FTP connection refused, login failed or listing timed out

For hosting customers · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Good to know
  5. Still not working?

FTP on this server uses port 21 with TLS ("explicit TLS") and passive mode. If FTP is troublesome on your network, SFTP (port 22) with the same username and password is usually easier and always encrypted.

Symptoms

  • FileZilla: "Connection refused", "Connection timed out" or "Could not connect to server".
  • 530 Login authentication failed.
  • The login works but "Failed to retrieve directory listing" or the listing hangs.
  • A warning about the server's certificate.

Causes

Most likely first:

  1. Wrong login name or password — extra FTP accounts sign in as name@yourdomain.
  2. Passive data connections are blocked by your network or a firewall on your computer.
  3. FTP is not included in your plan, or the account is suspended — FTP sign-in is then off.
  4. Your address was banned after several failed logins.
  5. Too many connections at once from your address.

Fix

Settings to use

Open FTP Accounts (section Files). Under Connection:

  • Server: the server name shown (your host's server name).
  • Port: 21, encryption "explicit TLS" (in FileZilla: "Require explicit FTP over TLS").
  • Main account: your control panel username and password, with your whole home folder.
  • SFTP: port 22, same username and password.

1. Login name and password

  • Main account: the control panel username (not an email address) and the control panel password. If you changed the password in Password & Language, use the new one.
  • Extra FTP accounts: the full login, for example [email protected], and the password set for it. Click Change next to the account to set a new password.

New FTP accounts and password changes work within a minute.

2. Passive mode

The server uses passive mode with data ports 30000–30049. If the login works but the listing fails:

  • Make sure your FTP program uses passive mode (FileZilla does by default).
  • Try another network, or turn off FTP filtering in your own router or antivirus.
  • Or use SFTP on port 22, which needs only one connection.

3. FTP not in the plan, or suspended

If the menu has no FTP Accounts, your plan does not include FTP; use SFTP or ask your host. A suspended account cannot sign in to FTP or SFTP.

4. Banned after failed logins

After 6 failed FTP logins within 10 minutes, the address is banned for an hour. Wait, correct the saved password in your FTP program, and try again. See My IP is blocked.

5. Too many connections

At most 8 connections per address are accepted. In FileZilla, lower Maximum simultaneous transfers (Settings → Transfers) to 2 or 3.

Good to know

  • The certificate is made for the server name shown under Server. Connect with that name to avoid a warning; with another name, check the details and accept it.
  • Plain FTP without TLS also works, but sends your password unencrypted.
  • Uploads fail when the account's disk is full: see Disk quota exceeded.

Still not working?

Try SFTP with the same details. If both fail from every network, contact your host through Support with the error from your FTP program's log.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.