Refer to the appropriate documentation. Below are brief explanations for the most common status and error codes. Also In This Category WebHelp not displaying properly in browser Does Globalscape have a replacement for CuteSITE Builder? CURLE_LOGIN_DENIED (67) The remote server denied curl to login (Added in 7.13.1) CURLE_TFTP_NOTFOUND (68) File not found on TFTP server. this contact form
CURLM_OK (0) Things are fine. Permissions? 38 LDAP cannot bind. This error code indicates that an unexpected code was returned. The error buffer might contain more specific information about which exact option it concerns. my response
Post navigation ← A Brief Explanation of Hexadecimal Numbers You Don't Know Me -- And I Have a Gun. → Comments Common FTP Error Codes -- No Comments Leave a Reply In the 289 days Since 1 Jan, 2016 there were 1,920,738 Defensive Uses of personal firearms. From The Galleries Categories Administrivia (7) Amusements (9) Archive (1) Business (3) Commentary (53) Communications The command is an extension to the original FTP spec RFC 959. 33 HTTP range error. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again.
WinSCP does not use byte range locking. 26 Range lock refused A request for a byte range lock was refused. CURLE_UNSUPPORTED_PROTOCOL (1) The URL you passed to libcurl used a protocol that this libcurl does not support. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size. https://kb.globalscape.com/KnowledgebaseArticle10300.aspx The given remote host was not resolved.
The command opens a data connection to perform an action, but that action is canceled, and the data connection is closed. This error code is used for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0. CURLE_FTP_WEIRD_227_FORMAT (14) FTP servers return a 227-line as a response to a PASV command. Logged out if appropriate. 231 User logged out; service terminated. 232 Logout command noted, will complete when transfer done. 234 Specifies that the server accepts the authentication mechanism specified by the
For FTP, the server typically denied the STOR command. https://support.google.com/urchin/answer/28456?hl=en See above. 5 Bad message A badly formatted packet or other SFTP protocol incompatibility was detected. 6 No connection There is no connection to the server. The specified time-out period was reached according to the conditions. 29 FTP couldn't set ASCII. It indicates that the user has successfully logged on. (Informational) 250 Requested file action okay, completed. (Informational) 257 "PATHNAME" created. (Informational) 300 Series The command has been accepted, but the requested
CURLMcode This is the generic return code used by functions in the libcurl multi interface. weblink A required zlib function was not found. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt The user should send another command specifying this information.
Proceed as usual. This should never happen if the server is sane. If you want to remove the directory, first archive or delete the files in it. 10068 Too many users, server is full. navigate here Will likely get them to reinput credentials/reinstall etc initially, but if there's any specific information available re: this error code that would be great.
This is likely to be an internal error or problem, or a resource problem where something fundamental couldn't get done at init time. It may be returned by the server if the server does not implement an operation. 9 Invalid handle The handle value was invalid. 10 No such path The file path does Why they occur and possibly what you can do to fix the problem are also included.
When determining a course of action, review the entire log; some codes are informational only, others indicate that you have entered the wrong information, and others indicate what the information is CURLE_FTP_WEIRD_PASV_REPLY (13) libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. x5x File system These replies indicate the status of the Server file system vis-a-vis the requested transfer or other file system action. Some codes represent errors, most others simply communicate the status of the connection.
The SSL handshaking failed. 36 FTP bad download resume. CURLE_HTTP2 (16) A problem was detected in the HTTP2 framing layer. When properly decoded, these replies fall into the above categories. his comment is here The SIZE command failed.
CURLE_AGAIN (81) Socket is not ready for send/recv wait till it's ready and try again.