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

FTPS Server Certificate: best practices

Upon installation, Syncplify.me Server! auto-generates a self-signed X.509 (SSL/TLS) Server Certificate to be used for implicit and explicit FTP (aka FTPS and FTPES). However, such certificate carries the name of “Syncplify” in the organization field, and the common name (CN) field is only suitable for localhost (127.0.0.1). Therefore you may want to generate your own certificate, or buy one from a trusted Certification Authority (CA).

If a self-signed certificate is enough for you (and for all clients that will connect to your server), then you can simply use Syncplify.me Server!’s internal certificate generator as follows. Simply click the “gear” button on the FTP(S) tab of the Configuration manager. Continue reading

SSH Server Key: best practices

Upon installation, Syncplify.me Server! auto-generates a 1024 bit SSH Server Key, and that is enough for most users and most scenarios.

But some of our users may have higher needs in terms of bit-length (2048 or even 4096) or may need to use a specific SSH Server Key provided by a third party. This article covers such scenarios.

If you only need a higher bit-length, the easiest way is to generate a new SSH Server Key from within the Configuration Manager. In order to do so, simply click the “gear” button next to the SSH Server Key field, as shown in the picture below: Continue reading

Running your SFTP server with high-availability and fault tolerance

Note: this article refers to Syncplify.me Server! v1.x and v2.x; As of Syncplify.me Server! v3.0 support for high-availability (HA) is built-in, and much easier to use; you can read more about v3.0 HA features here.

If you are running Syncplify.me Server! in a corporate environment, especially if you operate it in a mission critical environment, you may want to deploy it with high-availability (HA) and fault tolerance in mind.

The diagram here below, and the explanation that follows, are intended as a “first step” towards that goal. More complicated layouts are certainly possible, but this is a good starting point:

Continue reading

How-to: map Syncplify.me Server! as a drive (Swish version)

We have recently published an article in this Knowledge Base to explain how to mount a Syncplify.me Server! SFTP account as a virtual drive using SFTP Net Drive.

It is also possible to do the same using another very nice software called Swish. Different philosophy, but similar results. Here is how to do it.

Continue reading

How-to: map Syncplify.me Server! as a drive (SFTP)

There are several software programs on the market that can mount a SFTP (or also a FTP) server connection as a drive. Syncplify.me Server! strictly adheres to the standards, therefore it grants a very high degree of compatibility.

One option is to use SFTP Net Drive (by Eldos). Here’s a brief tutorial on how to map a SFTP connection as a drive using it together with Syncplify.me Server!

Continue reading

Receive a notification email when someone tries to log in

A very common request from our customers is to be able to receive an email notification whenever someone tries to log into their FTP(S)/SFTP server with the wrong credentials.

You can do that by taking advantage of the new “after a failed authentication” event handler that we’ve introduced in Syncplify.me Server! version 1.0.5.15. Here is how to do it:

Continue reading

Using the TSrvUser object in Syncplify.me Server!

Here’s a brief example that shows how to use the TSrvUser from within a script run by a Syncplify.me Server! event handler. This scripts simply creates a clone of the currently connected user profile.

FtpScripter acquired by syncplify.me

Dear friends and fellow FtpScripter users, it’s our pleasure to announce that today FtpScripter has joined the syncplify.me family.

We will keep developing FtpScripter in the new company and with the brand new name of Ftp Script! Today we have released version 2.0.2.22 which is the first re-branded version with the new logo and slightly revisited GUI.

Video-lesson #3: backup with versioning and email notification

In this article we present a very simple FTP script that, in just a few lines of code, performs the following operations:

  • zips the contents of a folder
  • uploads the zip archive to an FTP server, renaming the old one (if exists, for versioning)
  • notifies the operator via email after the upload has completed

Here below you can see both the video (see it in action) and the actual code that has been used during the recording of such video. Continue reading