Archives: February 24, 2023

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!


Syncplify Server! v6.0.19 released

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

Importance of this update: VERY IMPORTANT
Fixed
  • FTPES (explicit TLS) now no longer requires FTP permissions as well
  • FTP idle sessions that could not be terminated are now handled (timed-out and terminated) properly
  • Errors during WebClient! binding configuration are now handled correctly

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

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

Importance of this update: MINOR
Fixed
  • Minor Admin UI glitch that prevented the insertion of POSIX paths in VFSs (which only affected the Linux/ARM version of the software)

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

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

Importance of this update: MINOR
Improved
  • Improvements to Syncplify Customer Center portal’s Customer UI for usability purposes
  • Small SuperAdmin UI and Admin UI optimizations for usability purposes

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!


New support/ticketing system coming soon!

For several years we’ve been using Freshdesk to provide an online support/ticketing system to our customers. It’s a good and feature-rich solution, but it’s not deeply integrated with all of the other subsystems in our pipeline.

To improve on that, and to provide our customers with better, more tailor-made, more accurate support, we will soon switch to a more tightly integrated support/ticketing system.

When the new support/ticketing system is deployed, all support requests will need to be initiated from within your Syncplify Customer Center portal. Your information will be automatically injected into the ticket, so that you will have to write less, and we will have more information up front to help you better and more accurately.

Yet another step towards providing the best customer service we possibly can. 🙂


Syncplify Server! v6.0.16 released

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

Importance of this update: MINOR
Fixed
  • Glitch in the Admin UI that affected only the Linux version preventing it from using standard POSIX paths when creating new VFSs

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

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

Importance of this update: NORMAL
Improved
  • CLI installer added a –repair command line argument to repair existing installations
  • CLI installer now does not overwrite your .toml files during maintenance (update/upgrade)
  • More settings are now adopted in real-time without requiring a restart of the “worker” system service
  • Implemented the statvfs@openssh.org SFTP protocol extension

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!


So, what is this SyngoDB everyone is asking us about?

Previous versions of our flagship software, Syncplify Server!, did use MongoDB to store their configuration and metadata. Over the years, though, we had to accept that MongoDB is not always reliable, especially on Windows, when certain circumstances arise. This becomes painfully obvious when an unclean shutdown of the operating system occurs, and MongoDB fails to start when the machine reboots, until you manually clean up its lock file and/or repair its data files. It’s also not uncommon enough to find MongoDB suddenly unable to accept client connections for no apparent reason.

This was becoming more than just an annoyance. It was starting to affect our customers. So, mainly but not only for this reason, we embarked in the gigantic endeavor of developing our own backend DB.

First of all, the name. SyngoDB is not named after MongoDB, it’s actually the composition-abbreviation of three concepts: “Syn” for Syncplify, “go” because it’s written in Go, and “DB” because (drum-roll) it’s a DB.

So, what are the similarities and the differences between MongoDB and SyngoDB?

Let’s start with the similarities, because there are very few: both of them are schema-less, document-oriented, NoSQL databases. And that’s pretty much all they have in common.

The differences on the other hand, well, where do we even start? We’ll cover just a few of the most significant ones.

First and foremost, SyngoDB doesn’t have any of the powerful data manipulation and analytics functions that are a core value of MongoDB. Nor does it have MongoDB’s massive horizontal multi-node (replica-set) scalability. That wasn’t the goal in the first place.

SyngoDB, essentially and by design, had to achieve only three goals:

  • Highest reliability: it had to be always-available, never crash, and be consistent and reliable even across unclean reboot cycles; even if someone rips the power cable from the wall, SyngoDB must be able to run without issues and without data loss or corruption at the next OS restart.
  • Vertical scalability without compromising performance: your local data set may grow to petabytes without severely affecting operation time, especially insertion and querying time.
  • Built-in security out of the box: certificate-based authorization and optional built-in strong data encryption engine are part of SyngoDB’s core design.

We’re happy to report that SyngoDB has met, and even exceeded, our expectations. All of the design goals were achieved, and it’s now the backbone of our flagship product Syncplify Server!


Syncplify Server! v6.0.14 released

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

Importance of this update: IMPORTANT
Fixed
  • Import CRT issued based upon existing CSR didn’t always work
  • FTP sessions that would remain idle prior to attempting user authentication were not automatically closed, now they are
  • Backup function in the SuperAdmin UI would sometimes generate a 0-byte archive
  • a false-positive in FTP(E/S) session termination has now been gracefully absorbed
  • If Web/REST service started first, dashboard would only connect again after 60 seconds because of cached worker address
  • Some Allow-List checks were not performed correctly, now the Allow-List is always honored (when not empty)
  • In certain cases the CSR could not be downloaded after creation
  • FTP(E/S) TLSMode only showed the Disabled and Enabled statuses (Required was missing)
Improved
  • Various UI improvements, including clone function for Users and many more details

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!