WebDAV Extension Error Codes

The All-in-One WP Migration plugin communicates with your server and stores backups using WebDAV Extension. If there is a problem communicating with the server and the files in your account, you may receive one of these errors.

What can you do about it?

If the All-in-one WP Migration plugin is unable to connect to your WebDAV storage, please sign out of your account and sign back in to the plugin’s WebDAV Settings page in your WordPress Console.
Check that no other applications are running on your server at the same time as the All-in-One WP Migration extension. Consider stopping or uninstalling any connected third-party apps or services. Consider an alternative solution if you share a large number of documents with others or the general public.

Please see the list of error codes below for more information:

Invalid Credentials
The All-in-One WordPress Migration Plugin is unable to connect to your server. Please sign out of your account and sign back in to your WordPress Console’s WebDAV Settings.

The user does not have sufficient permissions for the file
The All-in-One WP Migration Plugin is unable to access any files or folders on your WebDAV server. Please ensure that the file or folder you are attempting to access with the plugin is accessible to your account.
If this does not work, or if the file is already on your server, please sign out of your account and sign back in to your WordPress Console’s WebDAV Settings page.

Invalid Hostname
The All-in-One WP Migration Plugin is unable to connect to your WebDAV server. If you are attempting to backup or migrate your site while logged in on a corporate domain, make sure you can access your WebDAV server or contact the domain administrator.

File not found
The All-in-One WP Migration Plugin is unable to access any files or folders on storage. Please double-check that the file exists and that you can access it via WebDAV.

Backend Error
While processing the request, an unexpected error occurred with your WebDAV storage. Please try once more. Please sign out of your account and sign back in to your WordPress Console’s WebDAV Settings page.

Bad Request
The All-in-One WordPress Migration Plugin is unable to connect to your WebDAV storage. Please sign out of your account and sign back in to your WordPress Console’s WebDAV Settings.

Invalid Directory
It could not find the specified initial path.

Sharing Rate Limit Exceeded
You have exceeded your account’s sharing rate limit. This could be related to emails or documents that you have publicly shared from your storage. When performing backups or migrations, avoid sending large volumes of emails. Remove permissions from files that are publicly accessible in your WebDAV storage.

The user has not granted access to the file
The All-in-One WP Migration Plugin is unable to access any files or folders on your server. Please ensure that the file or folder you are attempting to access with the plugin is accessible to your account. If this does not work, or if the file is alreadyon your WebDAV storage, please sign out of your account and sign back in to the WebDAV Settings page of the plugin on your WordPress Console.

Here is a complete list of HTTP error codes:

*press control F to search this page

Code: 400 ‘Bad Request’
Message: Cannot process the request because it is malformed or incorrect.

Code: 401 ‘Unauthorized’
Message: Required authentication information is either missing or not valid for the resource.

Code: 403 ‘Forbidden’
Message: Access is denied to the requested resource. The user might not have enough permission.

Code: 404 ‘Not Found’
Message: The requested resource doesn’t exist.

Code: 405 ‘Method Not Allowed’
Message: The resource does not allow the HTTP method in the request.

Code: 406 ‘Not Acceptable’
Message: This service doesn’t support the format requested in the Accept header. The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

Code: 407 ‘Proxy Authentication Required’
Message: Proxy authentication required. The client must first authenticate themselves with the proxy.

Code: 408 ‘Request Timeout’
Message: Request timed out. The server timed out waiting for the request. The client did not submit a request in the time the server allows. Repeat the request without modifications at any later time.

Code: 409 ‘Conflict’
Message: The current state conflicts with what the request expects. The conflict does allow the request to process.

Code: 410 ‘Gone’
Message: The requested resource is no longer available at the server.

Code: 411 ‘Length Required’
Message: The request requires a Content-Length based header.

Code: 412 ‘Precondition Failed’
Message: The server does not meet one of the preconditions that the requester put on the request.

Code 413 ‘Request Entity Too Large’
Message: The request size exceeds the maximum limit.

Code 414 ‘Request-URI Too Long’
Message: Request-URI too long. The URI provided was too long for the server to process.

Code: 415 ‘Unsupported Media Type’
Message: The service does not support the content type of the request format.

Code: 416 ‘Requested Range Not Satisfiable’
Message: The specified byte range is invalid or unavailable.

Code: 417 ‘Expectation Failed’
Message: Expectation failed. The server cannot meet the requirements of the Expect request-header field.

Code: 422 ‘Unprocessable Entity’
Message: The request was well-formed but was unable to be followed due to semantic errors.

Code: 423 ‘Locked’
Message: The resource that is being accessed is locked.

Code: 424 ‘Failed Dependency’
Message: The request failed because it depended on another request and that request failed

Code: 429 ‘Too many Requests’
Message: There have been too many requests on your server account. This can be related to documents that you are sharing publicly from your WebDAV storage or other applications that are using your account.

Code: 500 ‘Internal Server Error’
Message: There was an internal error while processing the request.

Code: 501 ‘Not Implemented’
Message: The requested feature is not implemented.

Code: 502 ‘Bad Gateway’
Message: Bad gateway. The server was acting as a gateway or a proxy and received an invalid response from the upstream server.

Code: 503 ‘Service Unavailable’
Message: The service is temporarily unavailable. You may repeat the request after a delay. There may be a Retry-After header.

Code: 504 ‘504 Gateway Timeout’
Message: The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

Code: 505 ‘HTTP Version Not Supported’
Message: The server does not support the HTTP protocol version used in the request.

Code: 507 ‘ Insufficient Storage’
Message: The server is unable to store the representation needed to complete the request. Please ensure that you have enough disk space.

Code: 508 ‘Loop Detected’
Message: The server detected an infinite loop while processing the request.

Here is a complete list of cURL error codes:

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 you must obtain a rebuilt libcurl in order for it to function.

Couldn’t resolve proxy. Could not resolve the given proxy host.

Couldn’t resolve host. Could not resolve the given remote host.

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 (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 will pass 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.

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.

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 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 to start 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 an error. This mostly happens when you haven’t specified a good enough address for libcurl to use. See CURLOPT_FTPPORT.

he FTP REST command returned an 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 is 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. Could not find a required zlib function.

Aborted by callback. A callback returned “abort” to libcurl..

Internal error. A function was called with a bad parameter.

Interface error. Could not use a specified outgoing interface. Set which interface to use for outgoing connections’ source IP address with CURLOPT_INTERFACE.

Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.

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 to set 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 the 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.

The 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.

The socket is not ready for send/recv to wait till it’s ready and try again. This return code is only returned from curl_easy_recv and curl_easy_send (Added in 7.18.2)

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, 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 an 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.

The status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS
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 return. They were used in an old libcurl version and are currently unused.

Leave A Comment?