530 Login Authentication Failed: How to Fix the FTP Error in FileZilla and cPanel

Updated: 11 October 2026 · Applies to: Pure-FTPd 1.0.50, ProFTPD 1.3.8c and vsftpd 3.0.5 (tested on Debian 13), FileZilla 3.68, cPanel and WHM

530 Login authentication failed is the reply Pure-FTPd sends when it rejects a login. It means the server did not accept the username and password you sent. Usually the fix is one of these: use the full FTP username (on cPanel, extra FTP accounts log in as user@example.com, not just user), reset the FTP password and type it again, and make sure you are connecting to the server that really hosts the account.

Why the message does not tell you the cause

Pure-FTPd gives the same answer whatever the reason for the rejection. In our test with Pure-FTPd 1.0.50, each of these produced 530 Login authentication failed:

• the right user with a wrong password;
• a virtual account (deploy@example.com) with the correct password but only deploy as the username;
• a user that does not exist on that server;
• anonymous on a server with anonymous FTP switched off;
• a new account added to Pure-FTPd’s password file before its database was rebuilt.

The server only says why in its own log (see step 6). ProFTPD and vsftpd use different wording for the same situation: both answer 530 Login incorrect.

In FileZilla you see the server’s 530 reply in the message log, followed by a critical error saying it could not connect to the server.

How to fix 530 Login authentication failed

1. Use the full username. According to cPanel, an FTP account you create in cPanel > Files > FTP Accounts logs in with its full name, user@example.com. The cPanel username and password also work for FTP when the account has a dedicated IP address. Copy the exact login from the FTP Accounts list (see What are my FTP login details?).
2. Reset the password. In FTP Accounts, click Change Password next to the account, set a new password and save it. Then re-enter it in your client. FileZilla keeps saved passwords in the Site Manager, so an old saved password keeps failing until you replace it there. When you paste a password, check that no space came with it.
3. Check you reach the right server. After a hosting move, your domain may still point to the old server, where the account does not exist, so you get a 530. Compare the address your domain resolves to with the server IP in your hosting welcome email:

   dig +short example.com

   If they differ, connect with the server IP or hostname instead. According to cPanel, FTP over TLS does not support SNI, so for an encrypted connection use the server’s hostname, not your domain.
4. Match protocol and port. FTP and explicit FTP over TLS use port 21; SFTP is a different protocol on SSH port 22. According to cPanel, you cannot use an FTP account to connect over SFTP: SFTP needs the cPanel username (or root) with SSH access, and a failed SFTP login shows “Authentication failed” rather than 530. In FileZilla’s Site Manager, choose FTP (not SFTP) as the protocol, set Encryption to Use explicit FTP over TLS if available, with Logon Type Normal or Ask for password.
5. Wait out a brute-force block. According to cPanel, cPHulk watches Pure-FTPd logins and does not identify itself when it blocks an IP address or account, so after several wrong passwords even the right one is refused. Stop retrying, then ask your host to check cPHulk for your IP address. With root access, cPanel documents whmapi1 flush_cphulk_login_history_for_ips ip=203.0.113.10 to clear one address and /usr/local/cpanel/scripts/cphulkdwhitelist 203.0.113.10 to whitelist it.
6. Read the server log (root or server admin). Pure-FTPd writes the real reason to the system log. In our test the wrong username format left this line:

   pure-ftpd: (?@203.0.113.10) [WARNING] Authentication failed for user [deploy]

   Search for it with grep pure-ftpd /var/log/messages (AlmaLinux, Rocky, CloudLinux) or journalctl -t pure-ftpd. The user name in square brackets shows exactly what the client sent.

Should you switch FileZilla to plain FTP?

No. Older advice says to set Encryption to Only use plain FTP (insecure), but that does not fix a 530: the username and password are checked the same way, and plain FTP sends them unencrypted. When the server requires TLS, plain FTP fails with a different error. With Pure-FTPd set to accept only encrypted logins, our plain FTP test got:

421-Sorry, cleartext sessions and weak ciphers are not accepted on this server.
421 Please reconnect using TLS security mechanisms.

The same login over explicit TLS (234 AUTH TLS OK.) was accepted with 230 OK. Keep Use explicit FTP over TLS if available.

Server side: when correct logins still fail

• Stand-alone Pure-FTPd with virtual users: accounts in /etc/pure-ftpd/pureftpd.passwd only work after the database is rebuilt. In our test a new user got 530 until we ran:

  pure-pw mkdb

  Use pure-pw useradd ... -m or pure-pw passwd ... -m so the database is rebuilt in the same step.
• cPanel servers: FTP accounts are managed by cPanel, so do not edit Pure-FTPd files by hand. Reset the password in cPanel first. According to cPanel, /usr/local/cpanel/scripts/setupftpserver --current shows which FTP server is active (Pure-FTPd or ProFTPD), and WHM > Service Configuration > FTP Server Configuration holds the TLS and anonymous login settings. A ProFTPD server answers 530 Login incorrect., so the checks above apply in the same way.
• vsftpd: a refused login reads 530 Login incorrect.; also check whether the user is denied in the server’s user lists (see How to Allow or Deny Users on a vsftpd FTP Server).

Related guides: How to Change the Password for an FTP Account in cPanel (change an FTP password in cPanel), Configuring your website in FileZilla (set up a site in FileZilla), How to Use SFTP to Transfer Files Securely (sftp Commands, SSH Keys and FileZilla) (SFTP instead of FTP) and, for Centova Cast media uploads, On Uploading media MP3 via FTP found Authentication failed error. If you host with Ucartz, open a ticket with the FTP username and your public IP address: checking an FTP login is the kind of quick task covered by our Free Basic Managed Support.

Official documentation: cPanel FTP Accounts, WHM FTP Server Configuration, cPHulk Brute Force Protection.