Syncplify.me Server! and Active Directory user authentication

Besides it own internal user database, Syncplify.me Server! can authenticate users against the Windows user database and/or the Active Directory.

This article explains how to authenticate users against the Active Directory. A different article explains how to use the Windows (local) user database.

Continue reading

Working on Syncplify.me Server! v2.0: any feature requests?

Here at Syncplify we’re now actively working on Syncplify.me Server! version 2.0. New major version number because it will bring too many new and cool features to simply call it v1.3. Among said new features you will find:

  • Even more powerful violation-identification algorithm, and automatic blacklist
  • 10+ new events that can be managed by the event handler
  • Redesigned Configuration Manager GUI (easier to use over RDP connections)
  • And much much more (that we cannot discolse yet…)

Your feature requests are welcome and will all be evaluated by out team for inclusion in v2.0 or in a later version (if they can’t fit in the project timeline for v2.0). You can leave your suggestion on our KB, or on any of the social networks we use (Facebook, Google+, or Twitter).

Thank you!

The Syncplify.me Server! Dev Team

RSA or DSA keys for public-key authentication with Syncplify.me Server!?

Some SFTP clients have the ability to generate key-pairs for SSH2 public-key authentication, and – in some cases – our users are presented with the question: do you want to generate RSA or DSA keys?

When you want to authenticate against a Syncplify.me Server!, please, always use RSA keys. If you use DSA keys you may not be able to successfully authenticate.

Syncplify.me Server! pre-install check list

The Syncplify.me Server! system service may fail to start, or otherwise fail to answer incoming connections, if the following requirements are not met. So it is very important to double-check every item in the list below before running the installer.

  1. No other FTP(S) or SFTP (therefore also SSH) server should be running on the same TCP ports used by Syncplify.me Server! By default FTP runs on ports 21 and 20, FTPS (implicit) runs on ports 990 and 989, and the SSH/SFTP service runs on port 22. Please make sure such ports are available.
  2. Make sure your server or VM has at least 256 MB of RAM (512 recommended).
  3. Make sure your server or VM has at least 100 MB free hard disk space.
  4. If you will be running Syncplify.me Server! behind a firewall, please, make sure all NAT rules on your firewall are in place and working correctly.

Performing the few simple checks here above can avoid 99.9% of all installation problems, and guarantee you’ll be up and running in a matter of minutes.

How does the new blacklist automatic trigger work?

In Syncplify.me Server! version 1.1.6.16 we have introduced an additional automatic triggering method for the blacklist, and several users asked us to explain how it works with more detail.

The previous versions, in fact, were already able to trigger the automatic blacklisting of a client IP address upon a certain number (configurable) of failed authentication attempts.

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