libcurl-errors - error codes in libcurl
This man page includes most, if not all, available error codes in libcurl. Why they occur and possibly what you can do to fix the problem are also included.
Almost all "easy" interface functions return a CURLcode error code. No matter what, using the curl_easy_setopt(3) option CURLOPT_ERRORBUFFER(3) is a good idea as it will give you a human readable error string that may offer more details about the cause of the error than just the error code. curl_easy_strerror(3) can be called to get an error string from a given CURLcode number.
CURLcode is one
of the following:
All fine. Proceed as usual.
The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn’t use, it can be a misspelled protocol string or just a protocol libcurl has no code for.
Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn’t get done at init time.
The URL was not properly formatted.
A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. 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 libcurl.
Couldn’t resolve proxy. The given proxy host could not be resolved.
Couldn’t resolve host. The given remote host was not resolved.
Failed to connect() to host or proxy.
The server sent data libcurl couldn’t parse. This error code is used for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0.
We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.
While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.
After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned.
During an active FTP session while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS(3) (or the internal default) timeout expired.
libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed.
FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code is passed back.
An internal failure to lookup the host used for the new connection.
A problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.
Received an error when trying to set the transfer mode to binary or ASCII.
A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn’t match the previously given size.
This was either a weird reply to a ’RETR’ command or a zero byte transfer complete.
When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.
This is returned if CURLOPT_FAILONERROR(3) is set TRUE and the HTTP server returns an error code that is >= 400.
An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.
Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server’s explanation for this.
There was a problem reading a local file or an error returned by the read callback.
A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs.
Operation timeout. The specified time-out period was reached according to the conditions.
The FTP PORT command returned error. This mostly happens when you haven’t specified a good enough address for libcurl to use. See CURLOPT_FTPPORT(3).
The FTP REST command returned error. This should never happen if the server is sane.
The server does not support or accept range requests.
This is an odd error that mainly occurs due to internal confusion.
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
The download could not be resumed because the specified offset was out of the file boundary.
A file given with FILE:// couldn’t be opened. Most likely because the file path doesn’t identify an existing file. Did you check file permissions?
LDAP cannot bind. LDAP bind operation failed.
LDAP search failed.
Function not found. A required zlib function was not found.
Aborted by callback. A callback returned "abort" to libcurl.
Internal error. A function was called with a bad parameter.
Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections’ source IP address with CURLOPT_INTERFACE(3).
Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS(3).
An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem in the program that uses libcurl. The error buffer might contain more specific information about which exact option it concerns.
A telnet option string was Illegally formatted.
Nothing was returned from the server, and under the circumstances, getting nothing is considered an error.
The specified crypto engine wasn’t found.
Failed setting the selected SSL crypto engine as default!
Failed sending network data.
Failure with receiving network data.
problem with the local client certificate.
Couldn’t use specified cipher.
The remote server’s SSL certificate or SSH md5 fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.
Unrecognized transfer encoding.
Invalid LDAP URL.
Maximum file size exceeded.
Requested FTP SSL level failed.
When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed.
Initiating the SSL Engine failed.
The remote server denied curl to login (Added in 7.13.1)
File not found on TFTP server.
Permission problem on TFTP server.
Out of disk space on the server.
Illegal TFTP operation.
Unknown TFTP transfer ID.
File already exists and will not be overwritten.
This error should never be returned by a properly functioning TFTP server.
Character conversion failed.
Caller must register conversion callbacks.
Problem with reading the SSL CA cert (path? access rights?)
The resource referenced in the URL does not exist.
An unspecified error occurred during the SSH session.
Failed to shut down the SSL connection.
Failed to load CRL file (Added in 7.19.0)
Issuer check failed (Added in 7.19.0)
The FTP server does not understand the PRET command at all or does not support the given argument. Be careful when using CURLOPT_CUSTOMREQUEST(3), a custom LIST command will be sent with PRET CMD before PASV as well. (Added in 7.20.0)
Mismatch of RTSP CSeq numbers.
Mismatch of RTSP Session Identifiers.
Unable to parse FTP file list (during FTP wildcard downloading).
Chunk callback reported error.
(For internal use only, will never be returned by libcurl) No connection available, the session will be queued. (added in 7.30.0)
Failed to match the pinned key specified with CURLOPT_PINNEDPUBLICKEY(3).
Status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS(3).
Stream error in the HTTP/2 framing layer.
An API function was called from inside a callback.
An authentication function returned an error.
These error codes will never be returned. They were used in an old libcurl version and are currently unused.
This is the
generic return code used by functions in the libcurl multi
interface. Also consider curl_multi_strerror(3).
This is not really an error. It means you should call curl_multi_perform(3) again without doing select() or similar in between. Before version 7.20.0 this could be returned by curl_multi_perform(3), but in later versions this return code is never used.
Things are fine.
The passed-in handle is not a valid CURLM handle.
An easy handle was not good/valid. It could mean that it isn’t an easy handle at all, or possibly that the handle already is in used by this or another multi handle.
You are doomed.
This can only be returned if libcurl bugs. Please report it to us!
The passed-in socket is not a valid one that libcurl already knows about. (Added in 7.15.4)
curl_multi_setopt() with unsupported option (Added in 7.15.4)
An easy handle already added to a multi handle was attempted to get added a second time. (Added in 7.32.1)
An API function was called from inside a callback.
"share" interface will return a CURLSHcode to
indicate when an error has occurred. Also consider
All fine. Proceed as usual.
An invalid option was passed to the function.
The share object is currently in use.
An invalid share object was passed to the function.
Not enough memory was available. (Added in 7.12.0)
The requested sharing could not be done because the library you use don’t have that particular feature enabled. (Added in 7.23.0)
An argument that should be a CURLU pointer was passed in as a NULL.
A NULL pointer was passed to the ’part’ argument of curl_url_get(3).
A malformed input was passed to a URL API function.
The port number was not a decimal number between 0 and 65535.
This libcurl build doesn’t support the given URL scheme.
URL decode error, most likely because of rubbish in the input.
A memory function failed.
Credentials was passed in the URL when prohibited.
An unknown part ID was passed to a URL API function.
There is no scheme part in the URL.
There is no user part in the URL.
There is no password part in the URL.
There is no options part in the URL.
There is no host part in the URL.
There is no port part in the URL.
There is no query part in the URL.
There is no fragment part in the URL.