Quick fixes by cause
What you see or know | Likely cause | Fix |
|---|---|---|
You recently changed the password | FileZilla sends the old saved password | Site Manager: update the password, Logon Type "Normal" or "Ask for password" |
cPanel hosting, additional FTP account | Login without the domain part | Log in as |
Worked before, fails after many attempts | cPHulk blocked your IP | Admin removes the block in WHM, cPHulk History Reports |
"530 Non-anonymous sessions must use encryption" | The server requires TLS | Encryption: "Require explicit FTP over TLS" |
Right credentials, still fails for every user | Corrupted FTP user database |
|
The message comes from the server, not from the client, so WinSCP, Cyberduck and other FTP clients show the same "530 Login authentication failed". The fixes are the same, only the menu names differ.
What is the reason for the 530 Login authentication failed?
FileZilla 530 Login authentication failed usually means that the server didn't accept your username or password. This exact text comes from Pure-FTPd. ProFTPD answers with "530 Login incorrect." in the same situation. A wrong hostname can lead to it too: you may end up on another server where your account simply doesn't exist.
The first thing you need to do is make sure you are using the relevant and correct username and password when accessing the server. If one of those is incorrect - you'll definitely get 530 error, so double-check if you are using the correct credentials. If you are 100% sure that you are using valid credentials - check if the domain is pointed correctly to the server and reset the password.
FileZilla error?
On the other hand, the problem can be inside FileZilla. FileZilla remembers login details in the Site Manager, so it may keep sending an old password after you've changed it. Open "File > Site Manager", select your site and check "User" and "Password". Also make sure "Logon Type" is "Normal" or "Ask for password", not "Anonymous".
Encryption settings usually aren't the reason for this exact message. If the server requires TLS and you connect over plain FTP, Pure-FTPd replies "421 Sorry, cleartext sessions and weak ciphers are not accepted on this server", and vsftpd replies "530 Non-anonymous sessions must use encryption." Either way, the fix is the same: in the Site Manager, set "Encryption" to "Require explicit FTP over TLS" (or "Use explicit FTP over TLS if available"). On cPanel, use the server's hostname as the host for FTP over TLS, not your domain. Otherwise, the certificate won't match.
If you have SSH access, SFTP is an even better option: set "Protocol" to "SFTP" and use port 22 (or the SSH port your host gives you). Keep in mind that SFTP uses your SSH login, not the FTP account. On cPanel, that's your cPanel username and password - additional FTP accounts can't connect via SFTP.
Don't switch to "Only use plain FTP (insecure)". With plain FTP, your login, password and files travel over the network as clear text. If the server doesn't support TLS, ask your hosting provider to enable FTPS or SFTP. If you run the server yourself, our guide to setting up a secure FTP server on Ubuntu shows a TLS-only vsftpd setup and the SFTP alternative.
cPanel FTP
If you are using cPanel - there may be two types of FTP accounts: default and additional (pointed to a certain domain). For the default account, you can log in with your cPanel username and password if the account has a dedicated IP address. Otherwise, and for all additional FTP accounts, use the full login in the format «username@domain.com», so make sure you are using relevant login details in cPanel.
Also check cPHulk. It's cPanel's brute force protection, and it covers Pure-FTPd. After too many failed logins, it can block your IP address, and then even the right password won't get you in. The server admin can find and remove the block in WHM > Security Center > cPHulk Brute Force Protection > History Reports.
FTP database corruption
Pure-FTPd can keep virtual users and their passwords in a PureDB file (the passwords themselves are hashed). It may be corrupted due to incorrect cPanel updates or inaccurate FTP server changes. Database corruption may cause even bigger problems than 530 login authentication errors.
Before you touch the database, check the system log on the server. For every rejected login, Pure-FTPd writes "Authentication failed for user [name]". It shows which username actually reached the server, for example, without the @domain.com part.
On a server with plain Pure-FTPd and PureDB (without cPanel), rebuild the database from the text password file. By default, these are /etc/pureftpd.passwd and /etc/pureftpd.pdb. Debian and Ubuntu packages keep them in /etc/pure-ftpd/ instead:
shell
1pure-pw mkdbOr reset the user's password and commit the change to the database in one step:
shell
1pure-pw passwd username -mAnd if you are using cPanel / WHM - first reset the password in cPanel > Files > FTP Accounts > Change Password. If that doesn't help, the server admin can resync cPanel's FTP user data. Run it as root:
shell
1/scripts/ftpupdateDon't switch the FTP server back and forth in WHM > FTP Server Selection to fix passwords. Change it only if you really want to move to another FTP server.
In conclusion:
When you get "530 Login authentication failed" error - the first thing you should do is to check if you are using relevant credentials. Also check that you didn't copy any extra space or symbol with the password.
If you are using relevant credentials, and still get 530 error - try to reset the password. On cPanel, also make sure your IP isn't blocked by cPHulk.
If nothing above helps - then the problem is in the database and you already know what to do :)
Our support team helps server owners with errors like this every day. Together with cPHulk, mail and backups, it's part of the cloud infrastructure management we do, for example 24/7 managed server support for a hosting company in Iceland. Got 530 from a mail server instead, like 530 5.7.0 Authentication required? That's SMTP asking you to log in, and the fix is in our guide to the Relay Access Denied error.
