libcurl-errors(3) libcurl errors libcurl-errors(3)NAMElibcurl-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 prob‐
Almost all "easy" interface functions return a CURLcode error code. No
matter what, using the curl_easy_setopt(3) option CURLOPT_ERRORBUFFER
is a good idea as it will give you a human readable error string that
may offer more details about the error cause than just the error code
does. 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.
The URL was not properly formatted.
Couldn't resolve proxy. The given proxy host could not be
Couldn't resolve host. The given remote host was not resolved.
Failed to connect() to host or proxy.
After connecting to an FTP server, libcurl expects to get a cer‐
tain reply back. This error code implies that it got a strange
or bad reply. The given remote server is probably not an OK FTP
We were denied access to the resource given in the URL. For
FTP, this occurs while trying to change to the remote directory.
After having sent the FTP password to the server, libcurl
expects a proper reply. This error code indicates that an unex‐
pected code was returned.
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
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
An internal failure to lookup the host used for the new connec‐
Received an error when trying to set the transfer mode to binary
A file transfer was shorter or larger than expected. This hap‐
pens when the server first reports an expected transfer size,
and then delivers data that doesn't match the previously given
This was either a weird reply to a 'RETR' command or a zero byte
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
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP
server returns an error code that is >= 400. (This error code
was formerly known as CURLE_HTTP_NOT_FOUND.)
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 to this. (This error code was formerly known as
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 occur.
Operation timeout. The specified time-out period was reached
according to the conditions.
The FTP PORT command returned error. This mostly happen when you
haven't specified a good enough address for libcurl to use. See
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 confu‐
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.
Attempting FTP resume beyond file size.
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. (This error code was
formerly known as CURLE_HTTP_PORT_FAILED.)
Too many redirects. When following redirects, libcurl hit the
maximum amount. Set your limit with CURLOPT_MAXREDIRS.
An option set with CURLOPT_TELNETOPTIONS was not recog‐
nized/known. Refer to the appropriate documentation.
A telnet option string was Illegally formatted.
The remote server's SSL certificate or SSH md5 fingerprint was
deemed not OK.
Nothing was returned from the server, and under the circum‐
stances, 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
Peer certificate cannot be authenticated with known CA certifi‐
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
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
Socket is not ready for send/recv wait till it's ready and try
again. This return code is only returned from curl_easy_recv(3)
and curl_easy_send(3) (Added in 7.18.2)
These error codes will never be returned. They used to be 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
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
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)
The "share" interface will return a CURLSHcode to indicate when an
error has occurred. Also consider curl_share_strerror(3).
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)
libcurl 7.17.0 30 Aug 2007 libcurl-errors(3)