How to Fix FileZilla Connection Timeout Errors
Connection timeouts are the most common problem FileZilla users encounter. If you see errors like "Connection timed out", "ECONNREFUSED", or "Could not connect to server", this guide will help you identify and fix the issue.
Error 1: "Connection timed out after X seconds of inactivity"
This usually means FileZilla cannot reach the server at all. Common causes:
- Wrong hostname or IP address — double-check the server address in your Site Manager
- Wrong port — FTP uses port 21, SFTP uses port 22, FTPS often uses port 990
- Firewall blocking the connection — your local firewall, router, or the server's firewall may be blocking the port
- Server is down — try pinging the server or contacting your hosting provider
Error 2: "ECONNREFUSED - Connection refused"
The server is reachable but is actively refusing the connection:
- The FTP/SSH service may not be running on the server
- You may be connecting to the wrong port
- Your IP may be blocked by the server (too many failed login attempts)
Fix: Contact your hosting provider to verify the FTP service is running and your IP is not blocked.
Error 3: "GnuTLS error" or "TLS handshake failed"
This occurs with FTPS (FTP over TLS) connections when encryption negotiation fails:
- Go to File → Site Manager
- Select your site and change Encryption to "Only use plain FTP (insecure)" to test if the connection works without encryption
- If it works, try "Use explicit FTP over TLS if available" instead of "Require explicit FTP over TLS"
- Update FileZilla to the latest version — older versions may have TLS compatibility issues
Error 4: "Failed to retrieve directory listing"
You can connect but cannot see any files. This is almost always a passive/active mode issue:
- Go to Edit → Settings → Connection → FTP
- Change Transfer Mode to "Passive" (recommended for most users behind NAT/routers)
- If Passive does not work, try "Active" mode
- Some servers require specific passive port ranges — check with your hosting provider
Error 5: "Connection closed by server" after login
You can log in but the connection drops immediately:
- Your hosting account may have reached its connection limit
- Another FTP session may still be open — close all FileZilla windows and reconnect
- Your hosting plan may restrict FTP access — check with your provider
General Troubleshooting Steps
- Update FileZilla — always use the latest version
- Check your firewall — temporarily disable Windows Firewall or your antivirus to test
- Try a different network — some corporate or public WiFi networks block FTP ports
- Check the FileZilla log — the message log at the top of the FileZilla window shows detailed error messages. Copy these when asking for help
- Try SFTP instead of FTP — if your server supports SSH, SFTP (port 22) often works when FTP (port 21) is blocked
Still stuck? Post your question on the FileZilla forums with the full log output from FileZilla's message window.