What’s changed?

• Fixed a small bug in the SftpClient object that was causing the DeleteSourceAfterDownload to fail in some specific circumstances.

As usual, you can download the most recent release from our website.

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

What’s changed?

• Fixed a minor glitch (affecting only the Windows version) that sometimes prevented edits to the VFS permissions to be propagated back up to the upstream Syncplify Server! instance to which the VFS was connected.

As usual, you can download the most recent release from our website.

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

What’s changed?

• Fixed a two-tier bug that prevented offline license activation

As usual, you can download the most recent release from our website.

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

What’s changed?

• Fixed a bug that prevented the deletion of secrets by name both via UI and REST API

As usual, you can download the most recent release from our website.

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

What’s changed?

• Upgraded the embedded back-end database to SyngoDB v6.3.0 (which features better atomicity and faster document-locking mechanism)

As usual, you can download the most recent release from our website.

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

What’s changed?

• More accurate and faster reconciliation of VFS configurations when the remote Syncplify Server! node(s) configuration is edited

As usual, you can download the most recent release from our website.

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

What’s changed?

• Upgraded back-end SyngoDB server to version 6.2.3

• Fixed several accessibilty issues in the WebClient! UI

• Fixed a few minor bugs to all 4 UIs (Setup, SuperAdmin, Admin, and WebClient!)

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

Syncplify Server! v6.x has been retired and is under Limited Long-Term Support (LLTS). Under normal circumstances, no new v6 builds would be produced. This release is an exception, made exclusively because a critical defect affecting some but not all HA (high-availability) clusters warranted a backport.

What’s in this release

• Critical fix (backported from v7): Corrected an HA node communication defect that could (in some limited cases) cause cluster nodes to exchange excessive inter-node traffic, consuming significant network bandwidth while performing no useful work. In severe cases this could degrade the cluster performance.

That’s it. There are no new features, no other fixes, and no roadmap changes. This is a surgical release for one reason only.

A reminder about v6 support status

Version 6 is retired. LLTS means we address critical defects when the impact is severe enough to justify it. It does not mean v6 is back on the active development track, and it does not mean future issues will always receive backports.

If you are running v6, the right long-term answer remains the same: upgrade to v7. It is more secure, more capable, and actively maintained. Every day on v6 is a day without the improvements, protections, and fixes that ship continuously in v7.

If you are running an HA cluster on v6 and cannot upgrade immediately, apply this release. Then make upgrading to v7 your next scheduled priority.

You can download the most recent releases from our website.

Thank you for your continued trust in Syncplify.

What’s changed?

• Vastly improved the VFS Configuration section in the Admin UI, its user experience (UX) is now much cleaner and user-friendly

As usual, you can download the most recent release from our website.

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

What’s changed?

• Fixed one critical bug that could cause mis-mapping of the REST API port for inter-node communication and synchronization between HA (high-availability) nodes belonging to the same set

• Made setting permissions onto shared objects (files and folders) in WebClient! much clearer and easy to understand

• Several other “quality of life” improvements to WebClient!, including but not limited to, a convenient “refresh” button, a more consistent editing experience for “self” (own profile), the ability to set custom colors (light and dark) for WebClient!’s title and disclaimer, and a few other accessibility improvements

• Block-list items are now included in backup/restore operations (NEW!)

• OTP inputs on all 3 UIs are now auto-focused if/when they appear

• Vastly improved SMTP configuration and testing

• Several more small bug-fixes to all 3 UIs (SuperAdmin, Admin, and WebClient!)

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

Here is what changed, and why it matters.

The SyncJS library is now the common cross-product engine. Previous versions of AFT! had their own bespoke (and somewhat incompatible) SyncJS implementation. Starting with v4.0, every AFT! automation uses the new SyncJS engine shared library: the same engine that powers Syncplify Server! event handlers and R2FS! storage backend scripting tasks.

This is not a compatibility layer; it is a true unification. A script you write for AFT! will run on Syncplify Server! without modification (except for APIs that are product-specific by design), and vice versa. One scripting language. One API surface to learn. One VSCode extension to install.

Speaking of which: the SyncJS VSCode extension is already AFT!-aware. Install it, set syncjs.product to aft (which is the default), and you get full IntelliSense for every SyncJS built-in, every AFT!-specific extension (FsWatcher, RemoteWatcher, WaitForHaltSignal, Params, JobID), and the full SyncJS API surface. The extension also bundles MCP servers, so AI coding assistants like GitHub Copilot (etc) have accurate, real-time awareness of the AFT! scripting API.

Scripts can run long-lived jobs or one-shot executions. This is the design choice that opens the most doors. An AFT! script can run as a persistent process. WaitForHaltSignal() blocks the script until an operator stops it via the web UI or the REST API, which means scripts can react to events in real time rather than polling on a schedule. FsWatcher monitors local directories for file-system events (create, write, remove, rename, chmod) and fires a callback the moment something changes. RemoteWatcher does the same for remote directories. Both support recursive subdirectory tracking. Newly created subdirectories are covered automatically, with no extra logic required. Scheduled execution via a cron-compatible built-in scheduler is still fully supported for batch workloads. The two models coexist.

The VFS Library replaces hardcoded credentials. Connection profiles (SFTP, FTP/S, S3, Azure Blob, GCS, local filesystem) are defined once in the VFS Library with a name and tested independently. Scripts reference them by name using VirtualFSByName(). Credentials never appear in script code, and the same script works across environments by simply changing which named profile it references. This is the AFT! equivalent of the VFS Library concept that Syncplify Server! users already know well.

CopyToVFS/MoveToVFS transfer without touching local disk. When copying or moving a file from an SFTP server to an S3 bucket, AFT! streams it directly between the two endpoints. Nothing is staged locally. And if it’s a “move” operation, the source file is removed automatically after a successful transfer.

Named Secrets keep credentials out of scripts. Passwords, API keys, and other sensitive values are stored encrypted in AFT!’s secrets store and retrieved at runtime with GetSecret("secret-name"). They never appear in plain-text anywhere in the script.

The full SyncJS function library is available. That means SFTP, FTP/S, S3, Azure, and GCS client objects with a uniform upload/download API; fluent HTTP client for REST API calls; SQL database access; AMQP messaging (RabbitMQ and Azure Service Bus); PGP encryption and signing; HMAC signing and verification; CSV and XML parsing; email, Slack, Teams, Telegram, and Twilio notifications; process execution with output capture; encoding and compression; image processing; and TcpConnect for lightweight health checks. The 21 new SyncJS core functions announced last week are all available in AFT! v4 as well.

The admin UI has been completely redesigned and vastly improved. New dashboard, new script editor with syntax checking, cron job management, op log, license management, and settings, all rebuilt. Login is now protected by bcrypt-hashed passwords and TOTP-based two-factor authentication.

Migration from AFT! v3 is a single command. Run aft import-from-aft3 and your existing v3 JavaScript scripts are imported. They will require review, and likely some adaptation to the SyncJS API, but the import step eliminates the manual copy-paste work.

It ships as a single binary with no external dependencies. One file. No runtime, no sidecar processes. Drop it on Linux or Windows, run it interactively, or install it as a system service with one of the supplied installers, and it is operational. The binary is CGO-free and statically linked.

Come check out the new AFT! at syncplify.com!

What’s changed?

• Fixed a minor issue in the installer (not the software itself) that wasn’t able to correctly identify updates/upgrades for fully-licensed instances.

As usual, you can download the most recent release from our website.

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

What’s changed in Server!?

• Bumped the scripting subsystem to SyncJS v4.1.2, which adds 21 brand new utility functions to the language

• Fixed a bug in the Admin UI that prevented clearing the SMTP configuration

• Improved UX of the WebClient! UI to more explicitly incorporate the new browser security restrictions with regards to OS interoperation with the file/directory selectors during uploads

What’s changed in R2FS!?

• Bumped the scripting subsystem to SyncJS v4.1.2, which adds 21 brand new utility functions to the language (same as in Server!)

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed in Server!?

• Extracted the SyncJS scripting language (Syncplify’s very own extended version of JavaScript built on top of the ECMA 5.1 standard with the addition of many dedicated functions, methods, and types) into an independent shared library so that it can be ported to R2FS! and AFT! as well with perfect consistency

• Removed deprecated ioutil package (Go) and switched to the recommended alternatives (io, os, etc…)

• Fixed a bug with the multiplexed session counter for SSH-based subsystems which could, in certain conditions, “forget” to decrement the number of total active sessions in the dashboard

• Fixed several cosmetic (and one functional) bugs in the Admin UI

What’s changed in R2FS!?

• Added full SyncJS scripting and event-handling (uses the same SyncJS extended version of JavaScript also available in the Server! software) - now you can run your SyncJS scripts on the storage side as well!

• Added indexed/searchable VFS-level “op log” directly in R2FS!’s back-end database (does not substitute log files, which are still there for full auditing trail)

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed?

• Fixed a WebClient! UI bug that was recently introduced, which prevented multi-file/folder, nested, batched uploads, and improved the upload UX at the same time

• Fixed 3 more accessibility issues in the WebClient! UI

• Fixed a sanitization step in the Admin UI’s VFS page which, in some cases, would prevent saving the at-rest encryption passphrase for cloud-based VFS types (S3, Azure, GCP)

• Used more efficient “scroller” based approach for configuration backup and restores, which improves the speed of these two operations by about 15%, and provides for more granular and graceful error handling

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed?

• Vastly improved tombstone management for the HA synchronization database, making the sync operation between HA nodes up to 10x faster

• Fixed a glitch in the configuration of at-rest encryption that only affected Azure and GCP VFs types

• Added “Secret” management to the Admin UI and GetSecret method to the scripting engine, to safely store encrypted secrets in Syncplify Server!’s database and use them from your event-handling scripts

• Ported over all the “client objects” from AFT!, they are now all also available in Syncplify Server!’s scripting engine (reached 100% parity of features)

• Resolved a few minor accessibility issues in the SuperAdmin, Admin, and WebClient! UIs

• Updated OpenAPI definitions and software manual to reflect the new features and capabilities

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed?

• Added the ability to specify a custom HELO/EHLO string in the SMTP configuration settings

• Fixed a WebClient!-specific glitch that prevented users authenticated from LDAP groups from sharing files/folders, but only when the Home-VFS had dynamic parameters in its target configuration

• Resolved a few minor accessibility issues in the SuperAdmin, Admin, and WebClient! UIs

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed?

• Fixed the SSSync database collections for HA-nodes that were previously upgraded from an old Syncplify Server! version 6.x. If you have an instance of a high-availability set that was upgraded from v6.x, please, bear in mind:

  • Upgrading to v7.0.14+ is absolutely necessary to resolve inter-node synchronization issues, and prevent future ones

  • This upgrade may take a very long time (even > 10 minutes in some cases), let the installer run, it’s not stuck, please be patient

• Added (optional) cryptographically secure and auditable log file “rolling” digital signatures, forensically provable, ideal for customers working in highly regulated environments (dedicated blog post coming soon on this topic)

• Added the ability to optionally cycle (rotate) log files on a daily basis, in addition to the size-based rotation logic which is still present

• Fixed the behavior of the LIST command in the FTP(E/S) protocol handler to correctly handle wildcard restrictions

• Further refinement to the dereferencing of AD group users with regards to objects (directories and files) shared via WebClient! which now correctly honor parametric VFS configurations for this type of users

• Upgraded the back-end SyngoDB to the most recent version which comes with significant performance improvements

• Fixed a few minor glitches in the SuperAdmin and Admin UIs

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed?

• Vastly improved the dereferencing of AD user account data for “LDAP Group” accounts, for which the maximum number of concurrent connections per user will now take into account the actual UPN of the user in the group in which they have been authenticated

• Fixed three minor/cosmetic bugs in the WebClient! UI (these bugs did not affect its functionality, nevertheless we keep trying to improve all aspects of our UIs and we act upon our customers’ reports)

Please, also read this note which pertains to all updates/upgrades. And, as usual, you can download the most recent release from our website.

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

What’s changed?

• Improved support for directory-symlinks on the storage server side: dereferencing (and therefore STAT support) is now 100% automatic and handled by R2FS! internally and seamlessly.

As usual, you can download the most recent release from our website.

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