FTP

I was FTP'ing and now I can no longer access the server

Updated November 2026 10,179 views 3 min read
FTP | Updated November 2026

If you were connected via FTP and suddenly lost access, your IP was likely blocked by the server firewall due to too many connections, failed authentication attempts, or a timeout that triggered brute-force protection. This is a temporary block and is easy to resolve.

01. Unblocking Your IP

Follow the steps in our firewall unblock guide to remove your IP from the block list. You can also check if your IP is blocked using upordown.ultrawebhosting.com. If the server is up for everyone else but not for you, your IP is likely blocked.

Important

Before reconnecting after an unblock, make sure your FTP client has the correct password. If your client has cached an old password, every reconnection attempt counts as a failed login, and your IP will be blocked again within seconds.

02. Why This Happens

The server firewall (CSF) monitors all incoming connections and automatically blocks IPs that trigger brute-force detection rules. Common FTP triggers:

Too many simultaneous connections - FTP clients default to 5-10 concurrent connections. The firewall sees this burst of connections from a single IP and interprets it as a potential attack. FileZilla's default is 10, which is too high.

Failed login attempts - A wrong password, a typo in the username, or a cached expired password triggers failed auth logs. Five consecutive failures typically result in a block.

Rapid reconnection - If your connection drops and the client immediately tries to reconnect with multiple threads, each retry counts as a new connection attempt. The burst can trigger the block.

Session timeout - If your connection goes idle and times out, some FTP clients aggressively try to reconnect with multiple threads simultaneously.

03. Preventing Future Blocks

Configure your FTP client with these settings to avoid triggering the firewall:

FileZilla: Go to Edit > Settings > Transfers. Set "Maximum simultaneous transfers" to 2. Under Connection > set "Timeout" to 60 seconds. See our FileZilla connections guide.

SmartFTP: Go to Tools > Settings > Transfer > set concurrent connections to 2. See our SmartFTP connections guide.

Any FTP client: Keep concurrent connections at 2-3, set timeout to 60 seconds, and enable passive mode.

04. Using SFTP Instead

SFTP (SSH File Transfer Protocol) is more reliable than FTP for ongoing file management. It uses a single connection on port 22, which is less likely to trigger firewall rules. Most FTP clients (including FileZilla) support SFTP - just change the protocol to SFTP and the port to 22.

For detailed SFTP setup instructions, see our FTP client guide and SSH access guide.

Keep Getting Blocked?

If your IP keeps getting blocked during FTP sessions despite reducing connections, open a ticket and we can investigate or whitelist your IP.

Open a Support Ticket

Frequently Asked Questions

Why did I lose FTP access suddenly?

Your IP was most likely blocked by the server firewall after too many connections, failed logins, or a timeout that tripped brute-force protection. It is a temporary, automatic block and is easy to clear.

How do I unblock my IP after an FTP block?

Use the self-service IP unblock tool to clear your address immediately. If you cannot reach it, find your IP on an IP-lookup site and open a ticket from another connection, such as mobile data, to request an unblock.

How do I stop getting FTP-blocked repeatedly?

Lower your FTP client's simultaneous connections to 2 or 3, make sure the stored password is correct (a wrong saved password retrying causes repeat blocks), and use passive mode. These remove the triggers that set off the firewall.

Should I use SFTP instead of FTP?

SFTP over SSH on port 22, where shell access is enabled, is a secure single-connection alternative that is less likely to trip connection-based blocks. For standard FTP, explicit FTP over TLS with few connections works well too.

Quick Recap: FTP Access Blocked

  1. Use the Firewall Unblock tool to remove the block
  2. Reduce connections to 2-3 in your FTP client settings
  3. Increase timeout to 60 seconds
  4. Verify your password before reconnecting to avoid re-triggering
  5. Consider SFTP on port 22 for more reliable connections

Last updated November 2026 · Browse all FTP articles

Share: X in Reddit f Email
  • 308 Users Found This Useful

Was this answer helpful?

Related Articles

FileZilla GnuTLS Error and Could Not Connect to Server Over FTPS

FTP | Updated November 2026 A "GnuTLS error" or "Could not connect to server" message in...

425 Could not open data connection to port

FTP | Updated November 2026 The "425 Could not open data connection to port" error in FTP...

What are these default ftp accounts?

FTP | Updated November 2026 When you open the FTP Accounts section in cPanel, you will notice...

FTP Timeouts

FTP | Updated November 2026 FTP connections can time out for several reasons: idle connection...

Filezilla Connection timed out after 20 seconds of inactivity

FTP | Updated November 2026 The "Connection timed out after 20 seconds of inactivity" error...



Save 30% on web hosting - Use coupon code Hosting30