SFTP Connection Issues

Your SFTP client (FileZilla, WinSCP, VS Code...) can't connect to your server, or refuses to upload files. Go through the checks below in order — most issues come from one of the first three.

What You See

Error: Authentication failed.
Error: Connection refused
Error: Connection timed out after 20 seconds of inactivity
Error: Critical error: Could not connect to server

Quick Diagnosis

1. Use SFTP, Not FTP

KataBump only supports SFTP, on port 2022. Plain FTP (port 21) will never work. In FileZilla's quick connect bar, the host must start with sftp://:

sftp://fr-node-xx.katabump.fr:2022

If your client has a separate Port field, either leave it empty (when the port is in the address) or set it to 2022.

2. Check the Server Address

The address depends on the node hosting your server. It follows the format fr-node-xx.katabump.fr, where xx is the node number — with no sftp. prefix in front. Copy it from the "Settings" section of your server on control.katabump.com rather than typing it from memory.

3. Check Your Credentials

Copy-paste both values and make sure no space was added at the beginning or end.

4. Network and DDoS Protection

• DDoS protection: if the node hosting your server is under attack, SFTP may be unavailable for a few moments. Wait and retry, and use the web file manager in the meantime.
• Restricted networks: school, work or public Wi-Fi networks often block uncommon ports like 2022. Try from another network (or your phone's connection) to confirm.
• Service status: check status.katabump.fr for an ongoing incident.

5. Upload to the Right Folder

Once connected, always upload into /home/container — that's your application's root. Uploading to / or elsewhere fails with Permission denied, or puts files where your bot won't find them.