The "Connection timed out after 20 seconds of inactivity" error in FileZilla is one of the most common FTP issues, and in most cases it has nothing to do with the server. FileZilla's default timeout is aggressively short, and a few quick setting changes will usually fix it permanently.
Increase the timeout from 20 to 60 seconds
Go to Edit > Settings > Connection in FileZilla. Change "Timeout in seconds" from 20 to 60. This single change resolves the issue for the majority of users. The default 20 seconds is simply too short for many connections, especially on shared hosting where the server may take a moment to respond during peak hours.
01. Why This Happens
FileZilla waits 20 seconds by default for the server to respond. If the server does not reply within that window, FileZilla gives up and shows the timeout error. Several things can cause the server to respond slowly or not at all:
- Too many simultaneous connections - FileZilla defaults to 10 concurrent connections, but most shared hosting servers limit FTP connections per account. When you exceed the limit, extra connections queue up and time out.
- Firewall or router blocking - Your local firewall, router, or ISP may be blocking or throttling FTP traffic, especially on non-standard ports.
- Passive mode issues - If FileZilla is set to active mode but your network does not support it (common behind NAT routers), the data connection will fail.
- DNS resolution delays - If you are connecting by hostname and DNS is slow, the initial connection can time out before it even starts.
- Server load - During high-traffic periods, the FTP server may take longer to authenticate your connection.
02. Fix 1: Increase the Timeout Value
- Open FileZilla and go to Edit > Settings (or FileZilla > Preferences on Mac)
- Click "Connection" in the left sidebar
- Change "Timeout in seconds" from 20 to 60
- Click OK and try connecting again
If 60 seconds is not enough (rare, but possible on very slow connections), try 120. If you need more than 120, there is likely a network issue rather than a timeout problem.
03. Fix 2: Reduce Concurrent Connections
FileZilla can open multiple connections at once to transfer several files simultaneously. This speeds things up in theory, but if the server limits you to 8 connections and FileZilla tries to open 10, two of them will time out.
- Go to Edit > Settings
- Click "Transfers" in the left sidebar
- Set "Maximum simultaneous transfers" to 2
- Uncheck "Limit number of simultaneous connections" or set it to 2
For Ultra Web Hosting accounts, we recommend no more than 3 concurrent FTP connections. This gives you reasonable transfer speed without hitting connection limits. If you are uploading many small files, a single connection is often faster because it avoids the overhead of establishing multiple sessions.
04. Fix 3: Switch to Passive Mode
FTP has two modes for data transfers: active and passive. If you are behind a router or firewall (which most people are), passive mode is almost always the correct choice.
- Go to Edit > Settings
- Click "FTP" under "Connection" in the left sidebar
- Under "Transfer Mode", select Passive
- Check "Allow fall back to other transfer mode on failure"
Passive mode lets the server choose the data port, which works better with NAT routers and firewalls since your client only makes outbound connections.
05. Fix 4: Use Explicit FTP over TLS
Plain FTP on port 21 is sometimes blocked or throttled by ISPs. Switching to encrypted FTP (FTPS) can bypass these restrictions and is more secure.
In the FileZilla Site Manager (File > Site Manager):
- Protocol: FTP - File Transfer Protocol
- Host: your domain name or server hostname
- Port: 21
- Encryption: Require explicit FTP over TLS
- Logon Type: Normal
- User: Your cPanel username
- Password: Your cPanel password
All Ultra Web Hosting servers support explicit FTP over TLS (FTPES). You may see a certificate warning the first time you connect. This is normal on shared hosting where the certificate is issued for the server hostname. Click "Always trust this certificate" and check the box to remember it.
06. Still Failing? Check These
Your IP might be blocked
If you entered your FTP password incorrectly several times, the server firewall may have temporarily blocked your IP address. Use our Firewall Unblock tool to check and unblock yourself.
Try connecting by IP instead of hostname
If DNS is being slow, connecting by your server's IP address eliminates DNS lookup delays. You can find your server IP in cPanel under "Server Information" on the right sidebar.
Try a different network
If you are on a corporate network or VPN, try connecting from your phone's hotspot. Some corporate firewalls block FTP entirely. If it works on a different network, your original network is the problem.
Check the FileZilla log
The message log at the top of FileZilla shows exactly what happened. Look for clues like "ECONNREFUSED" (connection refused, often a firewall block), "ETIMEDOUT" (network level timeout, different from FileZilla's timeout), or "530 Login incorrect" (wrong credentials).
Still Cannot Connect?
If you have tried all of the above and still cannot connect, open a ticket and include the full FileZilla log output. We will check the server side for you.
Open a Support TicketQuick Recap
- Increase timeout - Change from 20 to 60 seconds in Edit > Settings > Connection
- Reduce connections - Set maximum simultaneous transfers to 2-3
- Use passive mode - Almost always the right choice behind a router
- Try FTPS - Use "Require explicit FTP over TLS" to bypass ISP throttling
- Check firewall blocks - Use the unblock tool if you had failed logins
Thousands of users have fixed their FileZilla timeouts with these steps · Last updated March 2026 · Browse all FTP articles
