Syncplify.me Server! v4.1.0 released

We have just released version 4.1.0 of our Syncplify.me Server! software. This version features the following improvements:

  • Added: support for MongoDB authentication and specific utility to configure it (read how to use it here)
  • Fixed: small memory leak in one of the password encryption functions

Warning: upgrading to 4.1.0 from any version prior to 4.0.34 will invalidate your license, so please if you are a customer – before you upgrade – contact us to request a license reset.

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Ensuring Syncplify’s MongoDB instance safety

Syncplify.me Server! version: 4.0.0+

In light of the recent news regarding ransomware targeting MongoDB, we would like to inform all of our users and customers that we are actively working to add support for MongoDB’s authentication directly inside our software.

In the meantime, though, it is very important to understand that:

  • set aside the hype, a good network security model already addresses 99% of all the issues of this type (DB-connectivity related)
  • Syncplify’s specific MongoDB instance uses port 28038 (instead of the standard 27017) and is therefore not targeted by the above mentioned ransomware
  • Syncplify’s specific MondoDB instance only accepts requests from localhost (127.0.0.1) unless you have explicitly created a Windows Firewall rule

Because of the above reasons we believe that all Syncplify.me Server! instances deployed in non-HA mode are safe unless the network and Windows Firewall configuration has been altered by the users/customers themselves.

For HA (high-availability) instances, we do strongly recommend our users/customers to make sure their network firewall and Windows Firewall rules only allow connections to the DB server(s) from the machines running the SFTP front-end nodes. No other machine should be allowed to connect to your DB server(s).

This said, we want to reassure everyone – once again – that we are also actively working (with high priority) to add MongoDB authentication directly into our software.

Syncplify.me Server! v4.0.30 released

We have just released version 4.0.30 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: bug in the initialization of MongoDB replica sets, which affected only High-Availability (HA) deployments

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.20 released

We have just released version 4.0.20 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: quotas expressed in KB are now correctly evaluated in KB
  • Fixed: issue with detecting legacy MongoDB on Windows XP, Vista and Server 2003
  • Fixed: orphan socket handle upon failed PORT (active) transfer (which only affected the FTP protocol)

As usual you can download this new release from our website.