As of March 2025, we require encryption on all FTP connections. Before this requirement, it was possible to connect to FTP without encryption, which resulted in usernames and passwords being transmitted across the internet in clear text.

You may see an error returned like this:

Response: 421-Sorry, cleartext sessions and weak ciphers are not accepted on this server.
Response: 421 Please reconnect using TLS security mechanisms.
Error: Could not connect to server

The solution to this issue is to enable FTPS, which is FTP with TLS Encryption. Most FTP programs will allow you to choose FTP over SSL/TLS or FTPS. Choose explicit FTP over TLS on port 21.  We do not support implicit FTP on port 990.

Minimum FTP Client Supported Versions

• FileZilla: Version 3.10 or newer
• Dreamweaver: CS5.5 or newer
• WinSCP: Version 5.0 or newer
• Cyberduck: Version 4.3 or newer
• Transmit (macOS): Version 4 or newer
• CuteFTP: Version 8 or newer

Older versions of these clients may not support TLS 1.2 (or higher), causing connection failures or insecure fallback methods. If you use a very old client or version, please update to ensure proper encryption.

FileZilla

1. Open FileZilla and click Site Manager (under File > Site Manager).
2. In the Protocol drop-down, select FTP - File Transfer Protocol.
3. In the Encryption drop-down, choose Use explicit FTP over TLS.
4. Enter your host (ftp.example.com), username, and password as usual.
5. Ensure the Port is set to 21 (default for explicit FTPS).
6. Click Connect or OK.

Dreamweaver

1. Go to Site Setup or Manage Sites, select your site, and click Edit.
2. Under the Servers category, edit the server used for uploads.
3. For Connect Using, choose FTP over SSL/TLS (explicit encryption).
4. Enter your server address (ftp.example.com), username, and password. Leave Port as 21.
5. Click Save and then test your connection.

WinSCP

1. Open WinSCP and click New Session.
2. Under File protocol, select FTP.
3. In Encryption, choose TLS/SSL Explicit encryption.
4. Enter your hostname, username, and password.
5. Use port 21 (for explicit). Click Login.

Cyberduck

1. Open Cyberduck and click Open Connection.
2. In the top dropdown, choose FTP-SSL (Explicit AUTH TLS) (or FTP (TLS/SSL) in some versions).
3. Enter your server (ftp.example.com), username, and password.
4. Ensure the port is 21.
5. Click Connect, and accept the certificate if prompted.

Transmit (macOS)

1. Click the + button in the Transmit sidebar or go to File > New Connection.
2. Choose FTP with TLS/SSL (or “FTP (Explicit SSL)” in some versions) from the dropdown.
3. Enter your server, username, and password.
4. Make sure the port is 21.
5. Click Connect.

CuteFTP

1. Go to File > Site Manager (or press Ctrl+S).
2. Click New Site and name it.
3. Enter your host address and select FTP with TLS/SSL (Explicit) for Security.
4. Use port 21.
5. Enter your username and password, then click Connect.

Once you have enabled encryption, you will likely see a certificate window asking you to verify. You can accept the certificate to connect. If you continue to see connection errors, make sure your firewall or router is not blocking port 21 or the TLS connection.

Note: We do not support implicit FTP over TLS, which operates on port 990.  You will need to use explicit TLS on port 21.

Alternative Option: sFTP (FTP over SSH)

Most FTP clients also support sFTP.

sFTP is a completely different protocol than FTPS—it’s often called "FTP over SSH" because it uses an SSH-encrypted tunnel instead of the traditional FTP protocol. sFTP can be a great choice for security because it operates over a single port and uses robust SSH encryption and authentication methods.

• sFTP connects to port 2233 on our servers.
• It only works for the primary cPanel username.
• SSH is disabled by default; please contact us if you want SSH/sFTP enabled for your account.

Why Choose sFTP Over FTPS?

• Both encrypt data in transit, but SFTP uses SSH keys/credentials and a single port, which can simplify firewall settings, although this is rarely considered on the client side.
• FTPS remains widely supported and can be simpler to configure on some FTP clients, especially if were already using FTP.

Remote Path Differences:
When using sFTP, your root directory may differ from standard FTP. For example, instead of being placed directly in “public_html” or a similar folder, you will be placed in your home directory (e.g., /home/username). You can then navigate to the correct folder (e.g., /home/username/public_html) for uploading your site files.  How you adjust this varies from sFTP client to sFTP client.