Syncplify Server! v6.2.32 released

Importance of this update: [HOT-FIX]
What’s changed?
  • Fixed the gzip log rotator, it now correctly gzips log files upon rotation to save space, and doesn’t leave zombie files on disk
  • Slightly improved the logging of users’ PKI authentication phases

IMPORTANT NOTE: those who are running the “worker” system service under a different account (not System or LocalSystem) will need to re-configure the service to run under such account after upgrading from any version number <= 6.1.12)

Upgrading from v6.x.y is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!


V6 VFSs include: Disk, S3, Azure, Google Cloud, SFTP (all with optional at-rest encryption)

Syncplify.me Server! versions 1 through 5 have always historically supported only 2 typed of Virtual File Systems (VFS):

  1. Disk (with optional at-rest encryption via DiskAES256)
  2. SFTP (encrypted over the network but not at-rest on the remote site)

When Syncplify Server! v6 is released, though, depending on the edition you use it will include the following Virtual File System (VFS) types:

  1. Disk (local drives and SSDs, and remote NAS, SAN, iSCSI, …)
  2. Amazon S3 (store data in your AWS S3 bucket)
  3. Microsoft Azure Blob Storage (store data in Azure Cloud)
  4. Google Cloud Storage (store data in Google Cloud Platform)
  5. SFTP (store data on another SFTP server, useful for SFTP-proxying)

And all of them will also feature encryption at-rest on whatever local or remote storage they point to.