Syncplify.me Server! v4.1.7 released

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

  • Fixed: bug in the SSH “Shell” subsystem that prevented the user to be placed in the correct home directory upon opening a shell
  • Fixed: bug that prevented the TLS socket closure notification packet from being sent (only on Active FTPS data connections, no other protocol was affected)

Warning: upgrading to this version 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.

Syncplify.me Server! v4.0.10 released

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

  • Improved download speed by adding automatic self-adjustment of TCP window size
  • Improved analytics support
  • Improved support for AWS cloud platform

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

How to increase the speed of SFTP downloads

Syncplify.me Server! version: 3.0.0+

If you run Syncplify.me Server! hosted on a VM in the cloud or at some co-location provider, you are probably aware that your ISP uses traffic shapers to optimize the transfer speed and to prevent malicious users from abusing network resources.

In some cases, though, such strategy (packet/traffic shaping) clashes against the very nature of the SSH/SFTP protocol, in which both control and data packets are sent on the same connection. In particular, you may experience issues between the requested SSH socket buffer and the advertised buffer size on the network. If that happens, we got you covered! As of version 4.0, in fact, you can use a special Registry key to force Syncplify.me Server! to use a socket buffer size that matches the one advertised by your network. Continue reading