Guide FTP & File Management

How to fix FTP connection problems

The handful of things that actually stop an FTP connection working, checked in the order most likely to fix it fastest.

iFastHosting Support Team Updated 26 August 2026 8 min read Intermediate

An FTP connection can fail in a handful of ways — it might time out with no response at all, refuse the connection outright, reject your login, or connect but show an empty or endlessly loading file list. Each of those points at a slightly different cause, and working through them in order clears most problems without needing to contact support.

Before anything more technical, rule out the most common cause: a wrong host, username, password or port. Open the FTP section of your control panel in a browser tab and copy each value fresh, rather than trusting whatever is already saved in your client — a password changed weeks ago and never updated in a saved connection profile is a very common reason a client that "used to work" suddenly does not.

"530 Login incorrect" means exactly that

This response is the server telling you the username or password it received does not match an account. It is not a network or firewall issue, and retrying with the same details will not help. Reset the password in your control panel if you are not certain of it.

Match the port to the protocol

Plain FTP and FTPS both use port 21. SFTP uses port 22. Selecting SFTP as the protocol but leaving the port set to 21 — or the reverse — produces a connection that hangs or is refused, and the error message does not always make the mismatch obvious. Check your control panel for which port applies to the protocol you have chosen, and confirm the client's port field matches it exactly.

Active versus passive mode

This is the single most common cause of an FTP connection that times out while listing files, even though the initial login succeeds. It is worth understanding properly rather than just flipping a setting.

Plain FTP and FTPS use two separate connections: a command channel, which handles logging in and issuing instructions, and a data channel, which actually carries file listings and file contents. How that second connection gets opened is what "active" and "passive" mode control:

Active mode — the server opens a new connection back to your computer for the data channel. This requires your firewall or router to accept an incoming connection it did not initiate, which most home and office networks block by default.
Passive mode — your client opens the data channel to the server instead, the same direction as the original connection. Almost every firewall allows this without extra configuration, which is why passive mode is the default in modern clients and the one to use unless you have a specific reason not to.

Switch to passive mode first

In FileZilla, this is under Edit > Settings > Connection > FTP, where you can set the transfer mode explicitly to Passive. If your connection logs in but then hangs, freezes, or times out the moment it tries to list a folder, this is the setting to check before anything else.

SFTP does not have this active-versus-passive distinction at all, because it carries everything over the single encrypted connection used for login — one more reason it tends to be more reliable on networks with restrictive firewalls.

Your own firewall or antivirus

Security software running on your own computer can block outbound FTP traffic without showing an error that explains why — the connection simply times out. Temporarily disabling a firewall or antivirus to test (then re-enabling it immediately afterwards) will confirm whether it is the cause. If it is, add an exception for your FTP client rather than leaving protection off.

Try a different network

If the login details, port and passive mode are all correct and it still will not connect, try a different network entirely — a phone's mobile data connection is the quickest test. Corporate and public networks often block FTP ports outright as a matter of policy, in which case no client-side setting will fix it and you will need to use a different network, or a browser-based file manager instead, when working from that location.

Reading the error message properly

Message	What it usually means
Connection timed out	Nothing answered at all — check the host, and check whether a firewall is blocking the port.
Connection refused	Something answered and actively rejected the connection — usually a wrong port or the wrong protocol selected.
530 Login incorrect	The username or password is wrong for that account.
425 Cannot open data connection	An active-versus-passive mode problem — switch to passive mode.
550 Permission denied	The login worked, but the account cannot access that specific folder or file.

Still not connecting

If you have checked the login details, matched the port to the protocol, switched to passive mode, ruled out your own firewall, and tried a second network, the remaining possibility is a problem with the FTP account itself rather than your setup. Contact our support team with the exact error message and we can check the account's FTP settings from our side. It also helps to mention whether the account has ever connected successfully before, since that narrows down whether something changed recently.