๐ŸŸข Network Status| First month from $2.00 โ€” fully managed | Contact Support
Skip to content
Need help? Real engineers available 24/7. Average response under 15 minutes. Open a support ticket โ†’

FTP Connects But the Directory Listing Is Empty or Times Out โ€‹

A confusing FTP problem: the connection succeeds, the login is accepted, and then nothing loads. In FileZilla the log looks like this:

Status:  Connecting to 203.0.113.10:21...
Status:  Connection established, waiting for welcome message...
Status:  Initializing TLS...
Status:  TLS connection established.
Status:  Logged in
Status:  Retrieving directory listing...
Command: PWD
Response: 257 "/" is the current directory
Command: PASV
...
Error:   Connection timed out
Error:   Failed to retrieve directory listing

Login works, but "Retrieving directory listing" stalls for about 20 seconds and then fails. This is almost always a passive mode problem, not a wrong password or a broken account.

Why this happens โ€‹

An FTP session actually uses two connections:

  • A control connection (port 21) that carries your login and commands. This is the part that succeeds.
  • A separate data connection that carries the actual file list and file transfers.

In passive mode (the default for most clients), the server picks a high-numbered port and tells the client to open the data connection to it. If anything between you and the server blocks that second connection, the control channel keeps working but the listing never arrives, which produces exactly the timeout above.

What to try first โ€‹

1. Switch the client between passive and active mode โ€‹

This is the quickest test and often an immediate workaround.

  1. In FileZilla, open Site Manager and select your site (or open Edit โ†’ Settings โ†’ Connection โ†’ FTP for the global default).
  2. Go to the Transfer Settings tab.
  3. Change Transfer mode from Passive to Active (or the other way around if you were already on Active).
  4. Reconnect and try to list the directory again.

If switching modes makes the listing load, you have confirmed it is a passive-data-connection issue rather than a credentials problem.

2. Rule out your own network โ€‹

A local firewall, antivirus "FTP protection", VPN, or office router can block the passive data ports. Quick checks:

  • Temporarily disable local antivirus/firewall FTP filtering and retry.
  • Try from a different network (for example a phone hotspot). If it works elsewhere, the block is on your side.
โœ“
Consider SFTP
SFTP (SSH File Transfer) uses a single connection on one port and avoids passive-mode issues entirely. If your plan includes SSH access, connecting over SFTP on port 22 is the most reliable option.

When it just started for no reason โ€‹

If FTP worked fine for a long time and then suddenly began timing out on the listing, with no change on your side (same client, same password, same network), the passive data ports may have been blocked on the server, sometimes after routine server maintenance or a security update.

You cannot fix that from your account. Open a support ticket and include:

  1. The exact FileZilla (or other client) log, like the one at the top of this page.
  2. The hostname you are connecting to and the FTP username.
  3. Whether Active mode works as a temporary workaround.

We will confirm the passive port range is open on the server and get normal listings working again.

Next steps โ€‹

Managed hosting that actually manages.