Fix FTP "530 Login Authentication Failed"
530 Login authentication failedlogin incorrectcould not connectA 530 means the FTP server rejected your login. Usually it's the credentials or the connection mode/port. Here is how to get connected.
Cause 1: wrong username or password
The obvious one — double-check the FTP username (often it's the full user@domain.com on shared hosting) and reset the password in your panel if unsure.
Cause 2: wrong host or port
Use the FTP hostname/IP from your panel, with the right port — 21 for FTP/FTPS, 22 for SFTP (SFTP is SSH, a different protocol):
FTP/FTPS : port 21
SFTP : port 22 (uses your SSH login)Cause 3: passive mode / TLS
Many servers require passive (PASV) mode and explicit FTP over TLS. In your client (FileZilla etc.), set Encryption to "Require explicit FTP over TLS" and use passive mode.
They're different: FTP/FTPS uses port 21 and FTP accounts; SFTP uses port 22 and your SSH credentials. A 530 on one doesn't mean the other is broken — pick the right one.
530 = login rejected. Verify the user (often user@domain), the host/port, and use passive + explicit TLS.
Cause 4: the account is locked, suspended or over quota
Some panels suspend an FTP account after too many failed logins, or refuse new connections once the account is over its disk quota. Check your panel's FTP account status and disk quota before assuming it's a typo.
Cause 5: firewall blocking the passive port range
Even with correct credentials, a firewall on either end blocking the passive-mode data port range causes the login to hang or fail after authentication. If the control connection succeeds but the directory listing never loads, this is the likely cause — allow the FTP server's passive port range through your firewall.
How to prevent FTP login issues
- Use SFTP over FTP where possible — a single encrypted connection with none of the passive-port complexity.
- Store credentials in a password manager rather than memory, so typos don't creep in after a reset.
- Keep FTP accounts' quotas comfortably above what they need.
- Disable unused FTP accounts entirely to shrink the attack surface.
Related errors
If SFTP/SSH itself rejects your key rather than a password, see SSH permission denied (publickey). For general server access setup, see connecting with SSH. Login issues with the database GUI instead? See phpMyAdmin access denied.
Easy file management
Our web hosting gives you FTP, SFTP and a web file manager with a clean panel, on protected NVMe.
Frequently asked questions
What does FTP error 530 mean?
The FTP server rejected your login credentials. Usually the username or password is wrong, or you're connecting to the wrong host/port or protocol (FTP vs SFTP).
What's the difference between FTP and SFTP?
FTP/FTPS runs on port 21 and uses FTP accounts; SFTP runs on port 22 and uses your SSH login. They're separate protocols — make sure your client is set to the right one.
Why does FileZilla say 530 even with the right password?
Often the username needs to be the full user@domain.com on shared hosting, or the server requires passive mode and explicit FTP over TLS. Set those in the client and retry.
My FTP login worked yesterday - why is it 530 today?
Common causes are a password reset you forgot about, the account being auto-suspended after repeated failed logins from a bot, or the account going over its disk quota. Check the FTP account's status in your panel first.
Should I use FTP, FTPS or SFTP?
SFTP (port 22, your SSH login) is the most secure and simplest to firewall — one encrypted connection, no passive port range. Use FTPS (explicit TLS on port 21) only if your workflow specifically requires classic FTP.
Why does my FTP client connect but then hang loading the folder list?
That's a passive-mode symptom — the control connection (port 21) succeeded, but the data connection on the passive port range is being blocked by a firewall. Open that port range, or switch the client to active mode if appropriate.
Related articles
Fix "500 Internal Server Error" on Your Website
A 500 error on your site? The usual causes — .htaccess, file permissions, PHP — and how to fix them.
Read fix Web HostingHow to Point a Domain to Your Server (DNS A Record)
How to point a domain at your server with an A record — and why it doesn't work instantly.
Read fix Web HostingFix Email Going to Spam (SPF, DKIM & DMARC Explained)
Mail landing in spam? Set SPF, DKIM and DMARC correctly so your email reaches the inbox.
Read fix
