How to upgrade Syncplify.me Server! from V4 to V5

The video here below shows the recommended procedure to upgrade your Syncplify.me Server! from version 4.x to the new version 5.x.

This article assumes you’ve already read and understood the following 2 knowledge base articles, before you attempt the upgrade process:

It is recommended, before upgrading to v5.x, to make sure that you’re running the latest version 4, which is v4.2.5.

Also, it should go without saying (but we say it anyway), that prior to any major upgrade like this you should always make sure to take a snapshot or a full backup of the machine/VM running your existing version. This way, should anything go wrong during the upgrade, you can always go back to your old v4.x in no time.

Last but not least, the “magic URL” mentioned in the video, the one to backup your old v4.x configuration is:

 

Syncplify.me Server! v5: how to add a node/server to a high-availability (HA) set

This article embeds a video that shows how to add an additional node/server to an existing Syncplify.me Server! v5, turning it into a high-availability (HA) deployment.

This video only deals with the addition of the second node, we strongly recommend you to also check out this other article to learn how to deploy the first node.

How to install Syncplify.me Server! v5

This article embeds a video that shows how to install Syncplify.me Server! version 5.x either as a single standalone server or as the first node of a high availability deployment.

Now that you’ve set up your Syncplify.me Server! v5 as a standalone server, we suggest you check out this other article to learn how to add a second node and turn your SFTP server into a high-availability set.

ObjectName and VirtualObjectName deprecated in V5

Syncplify.me Server! version: 5.0.0+

Starting from version 5.0 of Syncplify.me Server! the ObjectName and VirtualObjectName variables (scripting engine and event-handling subsystem) will be deprecated.

They are still available, but they will be removed in future versions, so we do recommend to update all scripts that may be using such variables and make sure you use the new ones:

Session.ObjectName: substitutes ObjectName
Session.VirtualObjectName: substitutes VirtualObjectName

There are also two new similar values that will normally be empty, but may contain a string value only when responding to client commands like COPY, MOVE or RENAME. Such variables are:

Session.ObjectName2: contains the destination file name, relative to the local file system, for the object to be copied to, moved to, or renamed to (example: C:\SFTPData\NewFileName.txt)
Session.VirtualObjectName2: contains the destination file name, in POSIX-compliant format, for the object to be copied to, moved to, or renamed to (example: /SomeFolder/NewFileName.txt)

Syncplify.me Server! v5.0 new pricing scheme

As previously mentioned, with the release of version 5.0 of Syncplify.me Server! our prices will change.

The price increase is justified by the vast range of new features developed for the new version, as well as by the fact that our prices have always been much lower than competing solutions with a comparable feature set.

The table below summarizes said changes:

Edition

Basic


Professional


Ultimate

V4.x

$199


$399


$749

V5.x

$299


$499


$849

All current customers who own a license for version 4.x of the software, and are current with their support subscription, will receive this major upgrade for free. Therefore, we urge all customers who are planning on upgrading to v5.0 upon release to make sure their support subscription is valid and active.

Thank you.

What’s new in Syncplify.me Server! v5

Syncplify.me Server! version: 5.0.0+

While the step from v3 to v4 was somewhat “epic” (as 80%+ of the code was rewritten from scratch) the upcoming Syncplify.me Server! v5 will, instead, build upon the rock-solid foundation of v4 and expand and improve its features significantly. Version 5 will also be our most cloud-enabled version to date.

Here’s a list of some of the most important upcoming new features our users will find in Syncplify.me Server! v5: Continue reading

No, we’re not vulnerable to the libssh attack CVE-2018-10933

Many of our customers these days have sent us emails asking our team if Syncplify software products are affected by the libssh vulnerability documented in CVE-2018-10933.

Good news: none of our software products is vulnerable.

As mentioned in previous articles in this knowledge base, our products are not based on 3rd party open source libraries and solutions (like OpenSSL, OpenSSH, libssh, …) therefore our software does not inherit their bugs.

Syncplify.me Server! v4.2.2 released

We have just released version 4.2.2 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: bug that prevented correct import of virtual folder permissions when converting from an old version 3.x
  • Fixed: incorrect log line human-readable comment upon file rename

Warning: upgrading to this version from any version prior to 4.0.34 will invalidate your license, so please if you are a customer – before you upgrade – contact us to request a license reset.

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

FAQ: How to receive support from Syncplify?

Occasionally our users ask us what their support options are. This article is intended to provide a clarification on that topic.If you are using the Free Edition of our products you can:

In addition to that, if you are still using the free edition for evaluation purposes and you intend to buy once your issue is resolved, you may also:

And, of course, if you are a registered customer with a valid and active support subscription, you are welcome to:

Haven't found the answers you were looking for?Ask us your question!