pCloud Extension Error Codes

The All-in-One WP Migration plugin uses pCloud APIs to communicate with your pCloud and store your backups. If there is an error communicating with your pCloud and the files that are stored in your pCloud, you might get one of these errors
pCloud sets a per-user quota for each user to make sure that the resources available are shared fairly. If you have many other applications or systems connected to your pCloud you may encounter issues.

What can you do about it?

If the all-in-One WP Migration plugin cannot connect to your pCloud, please sign out from your pCloud and sign in again in the pCloud Settings of the plugin on your WordPress Console.
Ensure that there are no other applications using your pCloud at the same time as the All-in-One WP Migration extension. If you use a google drive sync, then pause or close the drive sync. If you have other 3rd party applications or other services that are connected to your pCloud, consider stopping or uninstalling them. If you share large numbers of documents with other people or the public, consider an alternative solution to pCloud.

Please see more specific detail about each error code below:

Invalid Credentials
The All-in-One WP migration plugin can not connect to your pCloud. Please sign out from your pCloud and sign in again in the pCloud Settings of the plugin on your WordPress Console.

The user does not have sufficient permissions for file
The All-in-One WP migration plugin can not access a file or folder on your pCloud. Please check that your pCloud account has permissions on the file or folder that you are trying to access with the plugin.
If this does not work, or if the file is stored on your pCloud, .please sign out from your pCloud and sign in again in the pCloud Settings of the plugin on your WordPress Console.

Cannot be used within the domain
The All-in-One WP migration plugin can not access your pCloud. If you are attempting to backup op or migrate your site whilst logged in on a corporate domain, please check that you are able to access your pCloud or contact the domain administrator.

File not found
The All-in-One WP migration plugin can not access a file or folder on your pCloud. Please check that the file exists and that you can access it through your pCloud.

Backend Error
An unexpected error occurred with your pCloud while processing the request. Please try again. Please sign out from your pCloud and sign in again in the pCloud Settings of the plugin on your WordPress Console.

Bad Request
The All-in-One WP migration plugin can not connect to your pCloud. Please sign out from your pCloud and sign in again in the pCloud Settings of the plugin on your WordPress Console.

User Rate Limit Exceeded
There have been too many API calls on your pCloud. Try again after stopping drive sync and any other applications that connect to your pCloud and waiting for 5 minutes

Rate Limit Exceeded
There have been too many API calls on your google drive. Try again after stopping drive sync and any other applications that connect to your google drive and waiting for 5 minutes.

Sharing Rate Limit Exceeded
You have exceeded the sharing rate limit on your pCloud account. This can be related to emails or documents that you are sharing publicly from your pCloud Don’t send large volumes of emails when you are doing backups/migrations. Remove permissions on publicly available files in your pCloud.

The user has not granted access to the file
The All-in-One WP migration plugin can not access a file or folder on your pCloud. Please check that your pCloud account has permissions on the file or folder that you are trying to access with the plugin. If this does not work, or if the file is stored on your pCloud, .please sign out from your pCloud and sign in again in the pCloud Settings of the plugin on your WordPress Console.

Too Many Requests
There have been too many requests on your pCloud account. This can be related to documents that you are sharing publicly from your google drive or other applications that are using your pCloud.

Here is a complete list of HTTP error codes:

*press control F to search this page

Code: 400 ‘Bad Request’
User error. This can mean that a required field or parameter has not been provided, the value supplied is invalid, or the combination of provided fields is invalid.

Code: 401 ‘Unauthorized’
Invalid authorization header. The access token you’re using is either expired or invalid. Suggested action: Refresh the access token using the long-lived refresh token.

Code: 402 ‘Payment Required’
Payment for the product is required in order to proceed.

Code: 403 ‘Forbidden’
Forbidden access. The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.

Code: 404 ‘Not Found’
The user does not have read access to a file, or the file does not exist. Suggested action: Report to users that they do not have read access to the file or that the file does not exist. Tell them that they should ask the owner for permission to the file.

Code: 405 ‘Method Not Allowed’
The HTTP method in the request is not allowed on the resource.

Code: 406 ‘Not Acceptable’
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’
Proxy authentication required. The client must first authenticate themselves with the proxy.

Code: 408 ‘Request Timeout’
Request timed out. The server timed out waiting for the request. The client did not produce a request within the time that the server was prepared to wait. Repeat the request without modifications at any later time.

Code: 409 ‘Conflict’
The current state conflicts with what the request expects. Request could not be processed because of the conflict.

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

Code: 411 ”Length Required’
A Content-Length based header is required on the request.

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

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

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

Code: 415 ‘Unsupported Media Type’
The content type of the request is a format that is not supported by the service.

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

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

Code: 429 ‘Too Many Requests’
The user has sent too many requests in a given amount of time.

Code: 500 ‘Internal Server Error’
An unexpected error occurred while processing the request.

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

Code: 502 ‘Bad Gateway’
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’
The service is temporarily unavailable. You may repeat the request after a delay. There may be a Retry-After header.

Code: 504 ‘Gateway Timeout’
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’
The server does not support the HTTP protocol version used in the request.

Here is a complete list of pCloud API errors:

There are number of cases when you request can’t be processed as is and an error will be returned. Error codes are always 4 digit. They can be grouped into few categories depending on the type of error occurred.

*press control F to search this page

Error Code: 1xxx
These errors are reserved for cases when the API client misbehaved. Most of the time it means that required parameters were not provided, text was provided when a number was expected, or one of several valid values was expected, but the input was something else.
Also, trying to call a method that requires login without providing any login credentials is a 1xxx error, while providing bad credentials is not. Well behaved applications should never receive this type of error, regardless of user actions. It is advisable to find a way to send the error and the error message to the application developer.

Error Code: 19xx
This is sub-type of 1xxx errors.
It may be the case that the application is misbehaving or it could be a synchronization error – e.g. you are trying to monitor the progress of an upload that the server knows nothing about. It might be the case that the application has passed a wrong or not existing hash or it could be that the upload request is still in transit and the API server is yet to start processing it.
If you are sure that you have passed the correct parameters, it is safe to retry the request later.

Error Code: 2xxx
The user is trying to preform invalid operation or is providing bad data. Example errors are bad filename supplied, file not found or folder already exists.  While a part of these can be prevented in the application (notably can not delete root folder), given the multi-user and multi client environment, files that were here just a moment ago may disappear. Generally these types of errors can be displayed directly to the user. However, it is preferable for the applications to actually understand the error codes instead of blindly displaying them. Of course, in some cases this errors can be the application’s fault – e.g. the user wanted to open a file, but the application provided incorrect folderid. Keep in mind that user here is a quite abstract concept. If your applications is a filesystem, your users are not the end users, but end users’ applications.

Error Code: 3xxx
These are rare errors when something can not be done and is unlikely that retrying will give any better results. One example of error of this type is trying to create a thumbnail from text file renamed to mypicture.jpg. It can’t be classified as 1xxx error as the application did nothing wrong – it received thumb: true and decided to create thumbnail. The user probably didn’t do anything wrong either (apart from renaming text file to mypicture.jpg, but it was probably the application that decided to display the thumbnail). These errors should be ignored if the unsuccessful action is not explicitly requested by user (fall back for failing to display a thumbnail would be to simply display an icon instead) and if the action was indeed requested by user, it should be reported that the file is bad.

Error Code:  4xxx
Should generally be very rare. They are reserved for cases when server is not willing to process you request. This generally means that the API server is rate limiting you because of too many requests or login tries. It should be possible to retry the request at a later stage.

Error Code: 5xxx
Errors of this type are the ones that we work very hard to never happen. Nevertheless they are still possible. These type of errors generally mean that we can not satisfy the request at this time (e.g. a server is unavailable) but it is very likely that the API server will be able to satisfy the request at a later stage.

Error Code: 6xxx
These are not real errors, but legitimate non-error answers. They are used by conditional methods mostly to signal some action not required state.

Error Code: 7xxx
These errors generally represent error condition for which neither the implementation that accesses the API nor it’s user are responsible. These errors should be expected when a method is indicated to return one of those and should be presented to the user more like a normal condition, rather than you got an error, the sky is falling down. Typical 7xxx error is for example when somebody has deleted his public link and the user is trying to access it.

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

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

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 be returned. They were used in an old libcurl version and are currently unused.


  1. Chalermchon C

    I have problem after activate ectention, error on bellow.

    Notice: Constant AI1WMUE_PLUGIN_BASENAME already defined in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/all-in-one-wp-migration-unlimited-extension.php on line 42

    Notice: Constant AI1WMUE_PATH already defined in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/all-in-one-wp-migration-unlimited-extension.php on line 45

    Notice: Constant AI1WMUE_URL already defined in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/all-in-one-wp-migration-unlimited-extension.php on line 48

    Notice: Use of undefined constant AI1WM_PATH – assumed ‘AI1WM_PATH’ in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/constants.php on line 49

    Notice: Use of undefined constant AI1WM_PATH – assumed ‘AI1WM_PATH’ in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/constants.php on line 64

    Warning: require_once(AI1WM_PATH/lib/vendor/bandar/bandar/lib/Bandar.php): failed to open stream: No such file or directory in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/loader.php on line 35

    Fatal error: require_once(): Failed opening required ‘AI1WM_PATH/lib/vendor/bandar/bandar/lib/Bandar.php’ (include_path=’.:/usr/share/pear:/usr/share/php’) in /home/admin/web/scgceramics.com/public_html/wp-content/plugins/all-in-one-wp-migration/loader.php on line 35

Leave A Comment?