While SSL/TLS security configuration for the FTPS protocol is entirely self-contained, Syncplify.me Server!’s Web/REST service relies on Windows’ HTTP.SYS subsystem, which is the same subsystem IIS is based on, and therefore its security configuration has to be made at operating system level.
We have just released version 4.0.9 of our Syncplify.me Server! software. This version features the following improvements:
- Added brand new “zero configuration” option to the HTTP/REST Configuration Wizard
- Added auto-selection of an alternate port for the HTTP/REST service if 443 is busy (without overwriting your IIS certificate)
- Fixed a bug in Active Directory Group support (also read this article)
- Fixed a stability bug in the REST API service which was affecting only Windows 2012 R2
As usual you can download this new release from our website.
During the installation process of Syncplify.me Server! v4.x (or greater) you will be asked the IP address and port to which the new HTTP REST API service should bind. While in most cases 0.0.0.0 (all interfaces) is a safe choice for the IP address, it is important to carefully choose a port.
In order to help you choose, we have prepared a very easy diagram. Just answer the questions on the diagram, and you’ll know which port (not) to use.
This said, in order to limit automatic probes (bots), choosing a non-standard port is probably always the safest way to go.
Getting closer and closer to the early availability of Syncplify.me Server! v4, we think it’s time to share with our customers one of the biggest new features they can expect to find in the upcoming major version: a secure (authenticated) JSON REST web service that allows granular management and configuration of the server, user database, blacklist, and every other aspect.