Syncplify Server! v6.2.3 released

Importance of this update: MINOR
Fixed
  • A glitch in the Linux installer (for x86 architectures) prevented installation on Ubuntu when more than one locale was installed in the OS, now the installation works properly
  • Block-list pagination didn’t work if you had more than 100 block-list items, now it works
Improved
  • Improved logging on connection rejection reasons and block-list addition reasons
  • CORS configuration now guarantees that the minimum functional values are always present

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.2.2 released

Importance of this update: MINOR
Improved
  • The service shutdown routines have been reworked to make them more elegant and streamlined (and with better logging, too)

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.2.1 released

Importance of this update: MINOR
Fixed
  • All file transfer operations now correctly log the relative path of the file that was transferred

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.22 released 🔔

Today we released Syncplify Server! v6.0.22; here’s what’s new and improved in this version.

Importance of this update: IMPORTANT
Fixed
  • PUT/GET operations are now logged correctly, even when the client issues a STAT command on the open file handle before the file-transfer is finished
  • Fixed a memory leak in the session manager that only affected the ARM build of the software (x86-64 Windows and Linux versions were not affected)
  • Fixed a small memory leak in the scripting and event-handling subsystem that affected all builds on all platforms and could cause memory exhaustion over time if this subsystem was actively used
  • Fixed importing LDAP server profiles from old V5 backups
Improved
  • Optimized global server configuration loads/reloads for speed and reduced memory footprint
  • General code cleanup, removed unused/old libraries and all references to MongoDB (even in the comments)
  • Usernames are no longer treated as case-sensitive, as POSIX compliance does not require case-sensitivity for usernames (only for passwords)
Added

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.20 released

Today we released Syncplify Server! v6.0.20; here’s what’s new and improved in this version.

Importance of this update: NORMAL
Fixed
  • Fixed the return condition when no session ID is found in a session during its termination
  • Added safety checks during restore (from V6 backups, V4/V5 were not affected)
  • Consistent logging is now applied to all restore processes (from V4, V5, and V6)
Improved
  • Added “Trusted Proxies” setting to the SuperAdmin UI global configuration, which applies to all management UIs (SuperAdmin and Admin) to be able to run them behind non-fixed-IP load balancers like ALB and the like

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!


JSON structured logs

Log files are system administrators’ best friends. Well, they are if they are understandable and useful. The problem with most log files, including most of the so-called “human-readable” ones, are very badly structured, and ultimately only truly understandable by a machine.

For that reason, in the past few years JSON-structured log files have become all the rage. Because they are easily understandable by a human being, and extremely fast to parse for a computerized log analyzer.

So, yes, in Syncplify Server! v6 you will find JSON-structured logs that look pretty much like this:

{
    "time":"2021-06-18 13:31:46.781",
    "level":"info",
    "nodeId":"peaceful-booth",
    "sender":"ssh2_sftp-handler",
    "sessionId":"bCrx5QKuNao73CB9UQTURU",
    "clientIp":"127.0.0.1",
    "serverIp":"127.0.0.1",
    "serverPort":22,
    "protocol":"ssh2_sftp",
    "username":"test",
    "method":"SESSION-START",
    "uriStem":"",
    "uriQuery":"",
    "status":200,
    "cliToSrvBytes":0,
    "srvToCliBytes":0,
    "userAgent":"SSH-2.0-FileZilla_3.52.2"
 }{
    "time":"2021-06-18 13:31:46.786",
    "level":"info",
    "nodeId":"peaceful-booth",
    "sender":"ssh2_sftp-handler",
    "sessionId":"bCrx5QKuNao73CB9UQTURU",
    "clientIp":"127.0.0.1",
    "serverIp":"127.0.0.1",
    "serverPort":22,
    "protocol":"ssh2_sftp",
    "username":"test",
    "method":"LIST",
    "uriStem":"/",
    "uriQuery":"",
    "status":200,
    "cliToSrvBytes":0,
    "srvToCliBytes":0,
    "userAgent":"SSH-2.0-FileZilla_3.52.2"
 }{
    "time":"2021-06-18 13:31:48.257",
    "level":"info",
    "nodeId":"peaceful-booth",
    "sender":"ssh2_sftp-handler",
    "sessionId":"bCrx5QKuNao73CB9UQTURU",
    "clientIp":"127.0.0.1",
    "serverIp":"127.0.0.1",
    "serverPort":22,
    "protocol":"ssh2_sftp",
    "username":"test",
    "method":"SESSION-END",
    "uriStem":"",
    "uriQuery":"",
    "status":200,
    "cliToSrvBytes":0,
    "srvToCliBytes":0,
    "userAgent":"SSH-2.0-FileZilla_3.52.2"
 }

In addition to that, while older versions of our software only supported logging to file or syslog, the next major version will support 4 log targets: file, syslog, database, or stdout.