How to: use Syncplify.me Server! to keep your Android devices in sync

Some of our users are asking how to use Syncplify.me Server! as a shared repository to keep files/folders on their Android devices always in sync.

There are various Android FTP(S)/SFTP clients that work smoothly with Syncplify.me Server! but, in this case, we need more: we need one that doesn’t just transfer files between Android and FTP(S)/SFTP, but can also keep them in sync.

Continue reading

Syncplify.me Server!: why so many “ports” to configure?

Some of our users have been asking why there are so many “ports” to configure in Syncplify.me Server! and if configuring them is really necessary.

First of all, let’s say that Syncplify.me Server! is designed to work out-of-the-box, without the need for any special reconfiguration. In fact, by default, it uses the ports defined in each protocol standard (21 and 20 for FTP, 990 and 989 for FTPS, and 22 for SFTP) plus the widest possible port-range for passive FTP(S) connections.

Continue reading

New release: Syncplify.me Server! v2.0.1.21

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

The only significant change in this new minor version is itsĀ increased blacklist flexibility with regards to authenticated/authorized users. With this new version, in fact, a legitimate user who tries two or more authentication methods (SSH/SFTP) will not increase the error count after a successful authentication, if at least one of them is successful.

You can download this new version from our web site, as usual.

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.