Syncplify.me Server! v4.0.2 Released!

We have just released version 4.0.2 of our Syncplify.me Server! software. This hot-fix release was necessary to address an issue with some of the upgrades from version 3.x to version 4.0 where – at times – a “path not found” error could appear during the upgrade process.

We apologize for any inconvenience, and recommend anyone that needs to upgrade from version 3.x to download this new hot-fix release.

Syncplify.me Server!: upgrading to version 4.x

Syncplify.me Server! version: 4.0.0+

Syncplify.me Server! v4 is more than just a major release. The software was totally redesigned and nearly entirely rewritten. The back-end database is new, both in structure (JSON) and with regards to the engine (MongoDB). The virtual file system (VFS) implements a true separation of the file transfer engine and the storage. Management is now entirely based on a rich set of REST API, to which we provide 2 front-ends: a modern Boorstrap/AngularJS secure web interface, and a completely redesigned CLI (command-line interface). For all these reasons, in order to upgrade to version 4 and keep your configuration and user database, you will have to carefully follow the procedures explained in this article, and especially in the VIDEO here below. Continue reading

Syncplify.me Server! v4: new license code format

Syncplify.me Server! version: 4.0.0+

This is a little, yet relevant, difference between Syncplify.me Server! v3 and v4. Version 3’s license codes were composed of 3 chunks of 4 digits each (ex: 1234-1234-1234) while the new v4 features license codes composed of 4 chunks of 4 digits each (ex: 1234-1234-1234-1234).

This means that v3 licenses are not compatible with v4. If you are an existing customer with an active support/maintenance and upgrade protection subscription, you will still need to contact us (before upgrading from v3 to v4) in order to request your new v4 license code. As usual, all v3 customers with an active subscription will be entitled to a FREE upgrade to v4.

Maintenance release: Syncplify.me Server! v3.1.15.55

We have just released version 3.1.15.55 of our Syncplify.me Server!

This new minor update (maintenance release) fixes a bug that affected only Windows Server 2012 and 2012R2 and prevented Syncplify.me Server! from correctly identifying overridden home folders for network user.

As usual you can download the latest version from our web site. Thank you!

New release: Syncplify.me FTP Script! v3.0.3.43

New major update for Syncplify.me FTP Script! Version 3.0 is finally here! And here’s a non comprehensive list of the main new features:

  • Multi-threaded parallel uploads and downloads
  • Configurable number of concurrent file transfer threads
  • Automatic keep-alive for lengthy operations
  • Automatic adjustment of file timestamps
  • Performance increase by up to 400%
  • Redesigned user interface for the script runner (execution environment)
  • More examples and ready-made templates

As usual you can download the new version from our web site. Thank you!

FTP Script! v3 is coming!

While working on the new version of our flagship product, Syncplify.me Server! v4, we have not forgotten our many FTP Script! users. Our team has been working hard on the brand new major version, and we’re now happy to announce that in few days Syncplify.me FTP Script v3.0 will be released.

The main limitation of version 1 and 2 was its single-threaded architecture. Although ideal for unattended file transfer operations, the single thread may become a significant performance hurdle when it comes to uploading or downloading a massive amount of small files.

Therefore all upload/download operations in FTP Script! v3 are now multi-threaded, and you can decide how many concurrent upload/download threads will be used in each transfer operation, and even change it multiple times within a single script. Continue reading

Syncplify.me Server! scripting: Session.Terminate and Blacklist

In a previous article we’ve been talking about the new properties and methods introduced by Syncplify.me Server! v3 to improve the session object. One of such methods is Session.Terminate that basically instructs the FTP(S) or SFTP server to forcefully terminate the session as soon as the script execution ends.

In such post we have mentioned the addition of another useful function, often used in conjunction with Session.Terminate: the Blacklist function (which name is pretty self-explanatory). In this article we will explain how to use it.

First of all, let’s see the functions definition:

There are 3 parameters:

  1. IPorNetwork: the first parameter clearly should be the specific IP address (e.g.: 192.168.172.25) or the network/subnet (e.g.: 192.168.172.0/255.255.255.0) that you want to blacklist
  2. AMinutes: this is pretty intuitive too, it is the number of minutes you want the above IP address or network to be blacklisted for (unless you are permanently blacklisting it, see point #3 here below)
  3. AType: this parameter can be either ttTemporary or ttPermanent. If you want to temporarily blacklist the IP/network you will use ttTemporary and the IP/network will stay in the blacklist only for AMinutes minutes. Instead if you use ttPermanent the IP/network will be blacklisted forever (unless manually removed) and the AMinutes parameter will be ignored.

Continue reading

Maintenance release: Syncplify.me Server! v3.1.4.44

We have just released Syncplify.me Server! v3.1.4.44 to fix an odd glitch that only happened with the 32 bit distribution of our software: basically the log file of the current day (the one “currently in use”) was locked and inaccessible. This strange behavior did not happen in the 64 bit version. Anyway, both 32 and 64 bit versions work correctly now.

As usual you can download the latest version of Syncplify.me Server! from our web site.