Syncplify.me Server!: 2 million file transfers in 24 hours

This article refers to Syncplify.me Server! v4.0, which – at the time the article is being written – is still in beta, and is not yet available for purchase by customers. The purpose of this article is to give our users an idea of the performance level of the upcoming version.

A considerable amount of Syncplify customers are large and very-large enterprises, and – as you can guess – some of them need a secure file transfer server that can sustain a tremendous amount of sessions for a very long period of time.

Syncplify.me Server! v3.x, with its HA (High Availability) deployment specific configuration was already ahead of the competition in many ways, but some of our customers needed something even more powerful. Therefore we have engineered our Syncplify.me Server! v4.0 to be our most reliable and heavy-load bearing version ever.

Continue reading

Maintenance release: Syncplify.me Server! v3.1.7.47

Today we have released Syncplify.me Server! v3.1.7.47 to fix a tiny bug that on some Windows Server 2012 systems (and only in certain conditions) prevented the user profiles from re-loading the user-specific white list after saving it to the configuration database.

Should you experience issues with saving/reloading some users’ white list, you may want to upgrade to this latest maintenance release.

Maintenance release: Syncplify.me Server! v3.1.6.46

We have just released Syncplify.me Server! v3.1.6.46 to work around the issues caused by CloudBerry Backup, as discussed in this post.

The SFTP protocol standard states “The server will respond to this request with a SSH_FXP_STATUS message. If a file or directory with the specified path already exists, an error will be returned.”; Yet, CloudBerry Backup tries to create the same directory twice and when Syncplify.me Server! correctly sends an error back the second time (because the directory already exists) CloudBerry Backup (3.9.6.42) considers the backup job failed.

This new version of Syncplify.me Server! tries to identify CloudBerry Backup, and sends a “success” reply upon double directory creation requests, but will practically ignore the second request if the first one was successful.

We have already contacted CloudBerry Lab, and we will remove this workaround from our software as soon as they release an update that fixes their protocol violation issue.

For now, if you need to use Syncplify.me Server! together with CloudBerry Backup, you are advised to download the latest version of our server from our web site.

New online and offline license activation method

Syncplify.me Server! v3.1.5.45 has introduced (per our customers’ request) a brand new online/offline license activation method that greatly simplifies the purchase process.

You don’t have to deal with the “System ID” anymore, in fact the Instance Controller now features a brand new “I have a License Code” button that you can push to activate the short and human-friendly license code you bought online. Note: the old “I have a License File” method is still supported for backward compatibility, but it is actually used only for offline activation of Enterprise licenses.

liccode

Continue reading

Maintenance release: Syncplify.me Server! v3.1.5.45

We have just released Syncplify.me Server! v3.1.5.45.

Nothing was changed in the server features or functions, this new version only adds a new online license activation system that allows our customers to buy without having to go through the whole “System ID” process. This should greatly simplify the purchase process.

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

Project codename: Foundation

More frequently than expected we receive questions from our users relative to the “codenames” of the various editions of our Syncplify.me Server! software. Since now our version 3 is solid enough to allow us to fully focus on version 4 development, we think this is a good time to answer that question, and give our readers few more details regarding what to expect in the upcoming new major version. Continue reading

Linux sftp client error 6: invalid packet (solution)

Some users of Syncplify.me Server! have reported that when trying to connect to Syncplify.me Server! using the command-line sftp client from certain (but not all) Linux versions they are suddenly disconnected with the error message shown in the picture here below:

linuxbefore

The error code 6 (invalid packet) signifies that the Linux sftp client was not able to negotiate a secure session with the server due to the (client) inability to verify the contents of the KEX packet coming from the server.

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.