Syncplify.me Server! v5.0.15 released

We have released version 5.0.15 of our flagship product, Syncplify.me Server!

This update features the following improvements:

  • Fixed: a glitch in v5.0.14 that prevented the software from correctly decoding the license data (the bug only affected v5.0.14, no other v5.0.x was affected by it)

As usual, you can download this update from our web site.

Thank you.

Syncplify.me Server! v5.0.12 released

We have released version 5.0.12 of our flagship product, Syncplify.me Server!

This update features the following improvements:

  • Fixed: new virtual SFTP site didn’t always start automatically upon creation
  • Fixed: “back-end DB unreachable” error is now correctly handled, and connection to the DB is automatically re-established
  • Fixed: virtual SFTP sites that have the “AutoStart” flag set are now correctly automatically started after an OS reboot
  • Fixed: SMTP configuration is now saved correctly (only applies to the Ultimate edition of our software)

As usual, you can download this update from our web site.

Thank you.

Syncplify.me Server! v5.0.11 released

We have released version 5.0.11 of our flagship product, Syncplify.me Server!

This is a hot-fix minor release that fixes only one small bug in the process that allows the web interface to change the SSL/TLS certificate used by/for the HTTPS protocol only.

If you have experienced difficulties changing such certificate we suggest you download this update.

Thank you.

Syncplify.me Server! V5 Beta-2

We have released the second beta of Syncplify.me Server! V5.

This new beta fixes all the issues and bugs that have been reported by our users and customers, and is – in general – much more solid than the first beta.

In particular, this second beta can upgrade older v3.x and v4.x, but obviously only and exclusively in test environments. Being a beta version, deployment in production environments is strictly forbidden.

Furthermore, this new beta also allows for deployment of High Availability (HA) installations, so our users and customers can finally try out the brand new – and much improved – HA scheme that V5 incorporates.

Find Syncplify.me Server! V5 BETA-2 here.

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)