Server! v4.0.20 released

We have just released version 4.0.20 of our Server! software. This version features the following improvements:

  • Fixed: quotas expressed in KB are now correctly evaluated in KB
  • Fixed: issue with detecting legacy MongoDB on Windows XP, Vista and Server 2003
  • Fixed: orphan socket handle upon failed PORT (active) transfer (which only affected the FTP protocol)

As usual you can download this new release from our website.

Can I run Server!’s HTTP REST API on port 443? Server! version: 4.0.0+

During the installation process of 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 (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.

HTTPS Port Choice

This said, in order to limit automatic probes (bots), choosing a non-standard port is probably always the safest way to go. Server!: why so many “ports” to configure?

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

First of all, let’s say that 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 Server! pre-install check list

The 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 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 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.