Syncplify Server! v6.2.9 released 🔥

Importance of this update: VERY IMPORTANT
What’s changed?
  • The ghost session bug that affected the FTP/FTPS/FTPES protocols (WebClient! and SFTP were not affected) has now been completely fixed
  • A weird and somewhat semi-random directory disappearance bug when using cloud (S3, Azure, GCP) VFSs has been identified and resolved

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!


Syncplify Server! v6.0.26 released

Importance of this update: MINOR
Fixed
  • Little cosmetic (Admin UI) bug introduced in v6.0.25 that prevented editing of LDAP users/group after importing them from an old V4/V5 backup
  • Cloud VFSs (S3, Azure, GCP) now correctly delete empty directories even when the client software sends the request without a trailing slash
Improved
  • Figured out a way to rename/move non-empty directories in cloud VFSs (S3, Azure, GCP) – it’s not fast (there’s no way to make this fast, as the only way is to iterate over all contained objects) but it works

Upgrading from v6.0.x 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!


Syncplify Server! v6.0.25 released

Importance of this update: NORMAL
Fixed
  • Fixed Admin UI glitches in the creation and editing of cloud VFSs (S3, Azure, GCP)
Improved
  • Importing (restoring) from an old V4/V5 backup now also sanitizes your block-list, safe-list, and allow-list: only correct items are imported, faulty ones are skipped
  • Cloud VFSs (S3, Azure, GCP) now return directory names in directory lists in a format that is more compatible with a broader variety of FTP/SFTP clients

Upgrading from v6.0.x 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!


Syncplify.me AFT! v3.1.4 released

We have released version 3.1.4 of our automated file transfer client, Syncplify.me AFT!
This update features the following improvements:

  • Workaround: uploads now can be completed even when the SFTP server doesn’t accept certain standard file-open flags, this allows to use AFT!, for example, to upload files to S3 via AWS’s quirky S3-SFTP protocol handler.

Thank you.


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.