ProFTPD server connection protocols

FTP (File Transfer Protocol)

FTP connections in “ active ” and “ passive ” mode are supported (alternate between the 2 to try to resolve a possible problem).

We opened the passive ports on our side [ PassivePorts 42000 44000] but only for connections to our FTP server. Passive FTP mode involves the use of remote ports defined by the remote server, as well as local ports which may vary depending on the FTP client used.

Passive mode is useful primarily when the client is behind a firewall or NAT router that blocks active FTP connections. However, in our infrastructure we allow active FTP connections, which means that relying on passive mode is generally not necessary. Regarding PHP, it is not possible, by default, to manage this configuration centrally. Therefore, it is not viable for us to open all ports to support all remote configurations, as this would not be practical or secure.

Overall, our infrastructure does not support 100% outgoing FTP connections in passive mode. For a smoother file transfer experience, we highly recommend using active FTP mode or exploring more modern technologies such as SFTP (read below).

SFTP (SSH File Transfer Protocol)

Creating SFTP connections ensures high security of file transfers. Make sure you have enabled SSH on your SFTP client and use port 22 for the connection: sftp://*****.

FTPES (Secure FTP with TLS/SSL)

Use FTPES for secure file transfers with port 21 and SSL/TLS encryption. With the Filezilla software for example, select "Explicit FTP connection over TLS" to configure your FTPES client: ftpes://*****.

FTP access

Access to FTPaccess configuration is available.

What is not supported

Public/Anonymous User

It is not allowed to log in as a public or anonymous user. You must have a valid user account to access your hosting space.

FTPs (secure FTP on a custom port)

The FTPs protocol is not supported, which means that port 2121 is not open for this type of connection.