How-to: configure Server! HA instances

Note: this article refers to Server! v3.x; As of Server! v4.0 support for high-availability (HA) has become even better; you can read more about v4.0 HA features here.

One of the main new features in Server! v3.0 is the ability to run in high availability (HA) configurations.

A highly available configuration is a deployment in which 2 or more servers share the same storage and configuration/user database. A network balancer is then used to decide whether to operate such servers in an active/active mode (where all nodes accept incoming client connections simultaneously) or in an active/passive mode (where some nodes accept client connections, and some other nodes kick in to substitute one of the active nodes that has stopped working).

This article explains how to configure Server! (with HA licenses) in order to operate in a highly available configuration. Please, read on… Continue reading

How-to: terminate a client session (or all of them)

As of version 3.0, Server! allows you to forcefully terminate an unwanted client session, or even terminate all active sessions if needed.

You can do so by running the Configuration Manager, switching to the real-time monitor panel, and right-click with your mouse on the session you wish to terminate. A popup menu will appear and let you choose whether you want to end the selected session, or all the currently active sessions.

terminating Server! v3.0: free upgrade for existing customers

All existing customers who paid for Server! v1.x or v2.x are entitled to a free upgrade to the “equivalent higher” edition of version 3.0.

What is the equivalent “higher edition”? For example, if you bought a v2.x “Professional” (used to be $179) you will now be upgraded to v3.0 “Pro One” ($219 MSRP) at no cost. And if you bought a v2.x “Professional Plus” (used to be $279) you will not be upgraded to the v3.0 “Pro Multi” ($349 MSRP) at no cost. And so on…

How to receive your free upgrade to v3.0? In the next 48 hours all customers will receive an email with the instructions. But, in case you don’t receive it (spam filters aren’t always friendly) you can simply contact us and request your free upgrade to v3.0.

If you contact us directly, please, remember to include your order number or license code, so we can identify you and provide you with the correct v3.0 upgrade license. Thank you!

How many concurrent file transfer from the same client?

Sometimes our users ask us how many concurrent file transfers can be initiated simultaneously by one client. The answer deserves a little bit of explanation.

First of all it is important to understand that this article is entirely focused on how to optimize the client side, in fact the server uses I/O completion ports and RTL critical sections to optimize concurrency under heavy load (hundreds or thousands of incoming client connections) and is therefore self-optimized.

The client side, instead, is very different. First of all the client has a GUI (graphical user interface) that needs to be synchronized with the “desktop” of the operating system. Furthermore, on the client side, the concept of “CPU core affinity” becomes very relevant. What is it? Let’s try to provide a simplified explanation… Continue reading

FTPS Server Certificate: best practices

Upon installation, 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 ( 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 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 ≠ FTPS (SSL/TLS) Server Certificate

From time to time our users ask how to use their X.509 (SSL/TLS) certificate for SFTP.

The one-line answer is: it’s not possible. But let’s dig into the topic and explain why, and above all how to implement server certificate and keys correctly.

First of all it is important to identify which protocol we intend to use, and what are its peculiarities: Continue reading

Issues connecting to Server! using FileZilla Client?

Seems like recent updates to the FileZilla Client have created some issues regarding secure (SSL and TLS) connections to Server!

First of all we would like to inform our users that the issue is not caused by Server!, in fact it is very well documented in two bug-reports of the FileZilla project (# 7873 and #9441) and it affects secure connections to several other servers, not just ours.

Anyhow… until a fixed version of the FileZilla Client is made available, we do recommend to download and use their version, which is the latest stable version before they broke compatibility. You can download it from SourceForge here.

Cisco UCM: backup to SFTP server

When you install Server!, the installer deploys a very secure (PCI compliant) configuration. Such strong configuration, though, is not compatible with Cisco UCM backups, as Cisco UCM has a very outdated support for the SFTP protocol.

Setting all the protocol options and tweaks by hand, to properly support Cisco UCM, may be painful, as there are so many! But Server! makes it easy by providing a handy drop-down list of ready-made configuration scenarios, including one that is ideal as a Cisco UCM backup target. Continue reading

Configuration Manager Default Password

If you are using Server! version 1.x or 2.x, the first time you run the Configuration Manager, after installing the software, it displays a little “hint” regarding the default username and password to use at your first access.

Username: admin
Password: [there is no password, just leave the field empty]

As soon as you perform your first access, you will be required (it’s mandatory) to set a password for the admin user. This requirement is necessary for obvious security reasons.

Instead, if you are using Server! version 3.x (or greater), the admin username and passwords are the ones you have chosen and set upon creation of your server instance. So there is no default value anymore, you will have to log in using username/password that you have set when you have created the particular instance you’re trying to access.