Troubleshooting guide
How to fix the problem
Check passive mode, server passive port range, firewall/NAT and correct public IP. If FTPS TLS is being terminated, check the server logs; don't switch to unencrypted FTP just because of a bug.
Possible solutions
Choose the method that matches your situation. Start with the simplest suitable option and check the result. If the problem is fixed, you do not need to continue with the other methods.
Passive data connection check
Check FileZilla's passive mode and, if you manage the server, its passive ports and NAT configuration.
Steps to follow
- Open FileZilla Edit > Settings and check Passive mode in the FTP connection settings; menu location depends on the version.
- Log in again and see if the file list loads.
- If you are unable to manage the server, please report the data channel error to the hosting support. Managing passive ports, NAT and public IP on the server is the job of the server administrator.
- Don't switch to unencrypted FTP just to get around the TLS bug.
Another network and server log
Compare from another network; provide the error time and personalized connection log to hosting support.
Steps to follow
- Compare the connection through your other network.
- Note the time and MLSD/ECONNABORTED error lines in the FileZilla log window.
- Remove login names, addresses or other non-public data before sending. Ask your hosting support to check the data channel and TLS log of the server.
If the problem persists
Compare a connection from another network and view the FileZilla log without publishing your login details. If you cannot control the server, please provide the error time and data channel error to the hosting support.
Request a repair