FTP reply code 530 is the authentication failure response. It appears in two contexts: after a failed PASS command (wrong password, account disabled, or login denied by policy), or when the client attempts a command that requires authentication without having logged in first. In the first case, the login credentials are incorrect and the client should prompt for new credentials. In the second case, the client needs to complete the USER/PASS sequence before issuing file commands. Some servers also return 530 to enforce TLS — requiring AUTH TLS before USER/PASS to prevent credentials from being sent in plaintext.
The most common cause — the password provided in the PASS command does not match the user account. Passwords are case-sensitive. The username may need to be the full email address or include a domain prefix depending on the server configuration.
The client sent a file operation (RETR, STOR, LIST, CWD, etc.) before completing the USER/PASS authentication sequence. The server requires login before granting file access.
The server is configured to require encrypted connections (AUTH TLS) before accepting USER and PASS commands. This prevents credentials from being transmitted in plaintext. The 530 response text usually mentions TLS or encryption.
The user account exists but has been disabled by the administrator, or the client's IP address is not in the server's allowed list. The server returns 530 to deny access without revealing the specific reason.
Double-check the username and password. Try logging in through a web-based control panel or FTP client that you know works to confirm the credentials are correct.
curl -v -u username:password ftp://ftp.example.com/
If the 530 response mentions TLS or security, send AUTH TLS first, then attempt USER and PASS. Many servers require encryption before accepting credentials.
curl -v --ssl-reqd -u user:pass ftp://ftp.example.com/
Ensure you send USER and PASS (and receive 230) before sending any file commands. The full sequence is: connect -> USER -> PASS -> 230 -> (file operations).
Some FTP servers restrict access to specific IP addresses. If your IP has changed or you are connecting from a new location, contact the administrator to update the allowed IP list.
Check that the FTP service is running and the user's home directory exists and is accessible.
Scan PortsAuthentication successful. The user is now logged in and can access the server.
The username was accepted. The server is now waiting for the password.
The server requires an account name (ACCT command) in addition to the username and password.
The FTP server is unavailable and is closing the connection. The client should retry later.