Fixing FileZilla Connection Problems on Windows
Almost every FileZilla problem is announced in the message log at the top of the window, and almost every one falls into a handful of categories. Read the last three lines before the failure, then find the matching section below.
Read the log first
The log distinguishes stages that look identical from the outside: name lookup, TCP connection, TLS handshake, login, directory listing, transfer. Whichever line comes last is where the session died — that alone eliminates most guesswork.
Connection failed or refused
- Retype the host name; a stray space or a leftover
ftp://prefix on an SFTP host is common. - Confirm the port with the provider instead of assuming 21.
- Try the host from a phone hotspot — corporate and campus networks routinely block FTP outright.
- Check the provider's status page before changing your own settings.
Timeouts
A connection that hangs and then gives up is usually filtering, not a wrong password. Raise the timeout in the connection settings, drop the number of simultaneous transfers to one, and disable the keep-alive experiment if you enabled it. If the same host works over SFTP but not FTP, the passive data channel is being blocked.
Failed to retrieve directory listing
This is the single most-reported message and it always concerns the second, data connection:
- Use passive mode; active mode rarely survives a home router.
- Allow the client in Windows Defender Firewall for private and public networks.
- Turn off "FTP over TLS" inspection in third-party antivirus suites — several break the handshake.
- If you run the server yourself, forward the passive range and set the external IP (see the server setup guide).
Certificate and TLS warnings
A warning on first connect is normal: the client is showing you a certificate it cannot verify. Compare the fingerprint with what the provider published, then trust it. A warning that reappears on every login means the certificate changed, expired, or is self-signed — worth asking about rather than clicking past forever.
Login rejected
- 530 — credentials refused. Confirm the FTP account name; it is often not your panel login.
- 421 too many connections — lower the simultaneous-transfer limit and wait for old sessions to expire.
- Repeated password prompts on SFTP — key authentication is expected; load the private key in the settings.
Transfer errors
- 550 permission denied — the account cannot write there; fix rights, not the client.
- Disk quota exceeded — free space on the remote account.
- Files arrive corrupted — force binary transfer type for anything that is not plain text.
- Uploads restart from zero — the host disallows resume; keep the queue short and retry.
Still stuck?
The project's own channels are the right place for a specific host or defect: the support forum and the issue tracker. Post the log with credentials removed.
Frequently asked
Why does FileZilla say the connection failed?
A failed connection usually means the host name or port is wrong, the server is not listening, or a firewall dropped the attempt before the login stage. The message log shows which of the three happened.
How do I fix 'failed to retrieve directory listing'?
The login succeeded but the data connection did not. Switch the site to passive mode, let the client through Windows Defender Firewall, and ask the host which passive port range it uses.
What causes an FTP timeout after 20 seconds?
Either nothing is answering on that port or an intermediate device is silently discarding packets. Raise the timeout, confirm the port with the provider, and retry from another network to rule out local filtering.