FileZilla successfully connects to my InfinityFree FTP server and logs in using explicit FTP over TLS, but it fails when retrieving the remote directory listing.
Connecting to [64:ff9b::b91b:860b]:21
TLS connection established.
Logged in
Command: EPSV
Response: 500 Unknown command
Command: EPRT |2|[IPv6 address]|…
Response: 522 Only IPv4 is supported (1)
Error: Failed to retrieve directory listing
Other Information
Hello InfinityFree Support,
I’m trying to migrate my local WordPress website to my InfinityFree hosting account.
FileZilla successfully connects, establishes TLS, and logs in, but it cannot retrieve the remote directory listing.
I have tried both FTP hostnames provided in the InfinityFree settings. I also tried connecting through a different Wi-Fi connection, but the same problem occurs.
The log suggests that FileZilla is connecting through an IPv6/NAT64 address, while the server reports that only IPv4 is supported.
Could you please advise how I can resolve this FTP connection issue?
Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
Your log shows FileZilla connecting through an IPv6 address, 64:ff9b::b91b:860b. That’s a NAT64 address, which wraps an IPv4 address inside IPv6, and it decodes to 185.27.134.11. So your network seems to be IPv6-only and translating to IPv4. The login works because the translator handles the control connection. The directory listing needs a second, separate connection, and FileZilla sets that up with EPRT |2|… using your IPv6 address. The server answers 522 Only IPv4 is supported, so the listing fails. I didn’t find a topic or article about this exact combination, so this comes from reading your log.
Our “Help, I cannot connect to FTP” article says a normal FileZilla log shows a line like Connecting to 185.27.134.11:21.... It also says you can enter that IP address as the FTP hostname. It suggests a VPN if your network restricts FTP connections.
Could you try one of these and tell me what the log shows?
Enter 185.27.134.11 as the host in FileZilla instead of the hostname. If the log then shows Connecting to 185.27.134.11:21, the listing should work. If it still shows a 64:ff9b:: address, your network is translating the connection regardless.
Connect through a VPN. That gives you an ordinary IPv4 route to the server.
Yes, that’s exactly it. Our FTP server only supports IPv4, but your network only supports IPv6. Your network provider is running a IPv6-to-4 gateway, but that’s causing the FTP connection to fail. We see that happen a lot on IPv6-only connections.
The proper way to fix it on our end would be to add IPv6 support, but that’s not on our roadmap.
So I think your best bet is to connect to the FTP server over a VPN. A VPN (generally) does give you an IPv4 connection, so you an bypass the NAT64 gateway on your network.