Changes to your FTP access

We’re making updates to our FTP services on 19 October 2026 to enhance the security and privacy of your file transfers.

If you use FTP to manage your website or host files with us, these changes will affect how you log in and connect to your server.

Here is a summary of what is changing, why it matters, and the actions you need to take if you make use of FTP or SSH:

1. Set a new FTP password from 19 October 2026

Your current FTP password will stop working when we reset it on 19 October 2026 at 08:00 SAST. You’ll need to update your FTP password(s) before you can connect using your FTP software.

Note: If you’re making use of domain-level access in konsoleH, you will need to use your new password to log in.

2. Update your FTP software

Update your FTP software (such as FileZilla) to connect using SFTP on port 22 instead of FTP on port 21. 

3. Update automated deployments, if applicable

If you use an automated deployment workflow, update it to use SSH keys on port 2222.

4. Using port 21

If you continue to use FTP on port 21, you will have to accept an ‘unknown’ certificate.

This is due to the fact that the server wildcard certificate is used to provide the TLS encryption for the FTP service on port 21 and your FTP client isn’t yet able to recognise or trust it. 

Port 22 allows you to securely transfer your files over an encrypted connection using SFTP (Secure File Transfer Protocol).

It is good practice to change your passwords regularly to prevent unauthorised access to your information.