ftp
FTP Reply Codes
Three-digit reply codes returned by FTP servers. The first digit indicates success, failure, or an intermediate state; the second indicates the category.
57 codes
references rfc-editor.org/rfc/rfc959
1xx Informational 4 codes
- 110 Restart Marker Reply Marks a restart point in a data transfer. The text contains the marker and timestamp for use with the REST command.
- 120 Service Ready Shortly The service is not ready at this moment but will be available within the stated number of minutes.
- 125 Data Connection Open The data connection is already open and the requested transfer is starting.
- 150 File Status OK The file status is acceptable and the server is about to open a data connection to begin the transfer.
2xx Success 21 codes
- 200 Command OK The requested command completed successfully. Used as a generic positive completion reply when no other 2xx code is more specific.
- 202 Command Not Implemented The command has been accepted but is superfluous at this site and has not been implemented.
- 211 System Status A system status or help reply, optionally listing supported features or extensions.
- 212 Directory Status Status information for the current or specified directory.
- 213 File Status Status information for the specified file, such as its size or modification time.
- 214 Help Message A help message describing commands or features supported by the server, intended for human users.
- 215 System Type The system type name, as used in the SYST command response, identifying the operating system of the server.
- 220 Service Ready The server is ready to accept a new user. Sent immediately after a client establishes a control connection.
- 221 Service Closing Control Connection The server is closing the control connection. Sent in response to a QUIT command after completing any outstanding transfer.
- 225 Data Connection Open The data connection is open and no transfer is in progress.
- 226 Closing Data Connection The transfer completed successfully and the data connection is being closed.
- 227 Entering Passive Mode The server has entered passive mode and provides the IP address and port for the client to connect to for the data transfer.
- 228 Entering Long Passive Mode The server is entering long passive mode, providing an extended address for IPv6 or large port numbers.
- 229 Entering Extended Passive Mode The server has entered extended passive mode (EPSV), providing a port number for the client to connect to for data transfer.
- 230 User Logged In The user has successfully authenticated and the session is now open. No further credentials are required.
- 231 User Logged Out The user has been logged out and the service is terminated.
- 232 Logout Command Noted The LOGOUT command has been noted and the user will be logged out when the transfer completes.
- 234 Auth Mechanism Accepted The server accepts the proposed security mechanism specified in the AUTH command and is ready to proceed with the TLS handshake.
- 235 Security Data Exchange Complete The security data exchange has completed successfully and a protected session is now established.
- 250 Requested File Action OK The requested file action has completed successfully. Returned after commands such as CWD, DELE, RNTO, and similar file operations.
- 257 Pathname Created The pathname was created, typically returned after a successful MKD command or as the current directory in response to a PWD command.
3xx Redirection 5 codes
- 331 Username OK, Need Password The username is recognised and acceptable; the client must now send the corresponding password.
- 332 Need Account for Login Further account information is required to complete the login. The client should send an ACCT command.
- 334 Security Mechanism OK The requested security mechanism is acceptable and the server is sending the initial security data.
- 335 Security Data Needed The server requires additional security data from the client before the authentication exchange can complete.
- 350 Pending Further Information The requested file action requires additional information before it can proceed, such as the destination name in a rename sequence (RNFR/RNTO).
4xx Client error 9 codes
- 421 Service Not Available The service is not available and the control connection is being closed. Typically sent when the server is shutting down or overloaded.
- 425 Cannot Open Data Connection The server cannot open the data connection. This may be due to a network issue, firewall, or the port being unavailable.
- 426 Connection Closed, Transfer Aborted The data connection was closed and the transfer has been aborted, typically due to a network error or server-side interruption.
- 430 Invalid Username or Password The login credentials supplied were incorrect. The user may retry authentication.
- 431 Need Unavailable Resource A required resource such as storage space or a lock is temporarily unavailable. The client may retry later.
- 434 Requested Host Unavailable The requested host is not available. Used in virtual hosting contexts where the target host cannot be reached.
- 450 File Action Not Taken The requested file action was not performed because the file was unavailable, for example due to a lock or access conflict. The client may retry.
- 451 Local Error in Processing The requested action was aborted due to a local error in the server, such as an I/O failure or internal fault.
- 452 Insufficient Storage Space The requested action was not taken because there is insufficient storage space on the server. The client may free space and retry.
5xx Server error 18 codes
- 500 Syntax Error The command was unrecognised or contained a syntax error. The command could not be interpreted by the server.
- 501 Syntax Error in Parameters The command syntax was valid but the parameters or arguments supplied were syntactically incorrect.
- 502 Command Not Implemented The command is known but has not been implemented by this server.
- 503 Bad Command Sequence The command was issued in an incorrect sequence. For example, RNTO was sent without a preceding RNFR.
- 504 Command Parameter Not Implemented The command is implemented but the specific parameter value supplied is not supported by this server.
- 521 Data Connection Already Open The data connection is already open; a PORT or PASV command cannot be accepted while a data connection is active.
- 522 Network Protocol Not Supported The server does not support the network protocol specified in an EPRT command. The reply lists the supported protocol numbers.
- 530 Not Logged In The client is not logged in and must authenticate before the requested command can be accepted.
- 532 Need Account for Storing Files Storing files requires account information that has not been provided. The client should send an ACCT command.
- 533 Command Protection Level Denied The data protection level requested is not supported by the server for this command.
- 534 Request Denied for Policy Reasons The request is denied due to server policy, such as when the client requests an insecure channel that the policy forbids.
- 535 Failed Security Check The security check on the transmitted data failed, indicating a possible integrity violation during the exchange.
- 536 Unsupported Data Channel Protection Level The requested data channel protection level is not supported by the server.
- 537 Command Protection Level Not Compliant The command protection level requested does not comply with the server's security policy.
- 550 File Unavailable The requested file action was not performed. The file does not exist, the user lacks permission, or the path is invalid.
- 551 Requested Page Type Unknown The requested page type is not known to the server. Used in the context of the TYPE command with structured page types.
- 552 Exceeded Storage Allocation The requested file action failed because the user's storage allocation has been exceeded.
- 553 File Name Not Allowed The requested file name is not permitted by the server, either due to naming restrictions or policy.