Troubleshooting FileZilla Error Logs

When you are experiencing issues using FileZilla to connect via FTP, you can review the error logs for common problems. In this guide we will discuss the cause and solution of FileZilla errors. Enabling error logging in FileZilla, allows you to save errors in a text file, and view them when needed.

In this article, we will cover the basics of troubleshooting FileZilla error logs.

Response: 530 Login authentication failed

Response: 530 Login authentication failed
 Error: Critical error
 Error:  Could not connect to server

This error is caused by an incorrect username, or password.

Response: 500 unrecognized command

Response: 500 unrecognized command
 Error:  Could not connect to server

In my tests, this error is caused by an incorrect port setting.

  • Check that you are using port 21.

Status: Connection attempt failed with “EAI_NONAME – Neither nodename nor servname provided, or not known”.

Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
 Error:  Could not connect to server

This error occurs when you enter a hostname that does not exist. There are several things you can do to fix this problem.

421 Too Many Connections

If you are getting this error, check out our full guide on 421 Too many connections.

Congratulations, now you know how to troubleshoot error logs in FileZilla!

JB
John-Paul Briones Content Writer II

John-Paul is an Electronics Engineer that spent most of his career in IT. He has been a Technical Writer for InMotion since 2013.

More Articles by John-Paul

Was this article helpful? Let us know!