The All-in-One WP Migration plugin uses Google Cloud Storage API to communicate with your Google Cloud drive and store your backups. If there is an error communicating with your account and the files that are on your drive, you might get one of these errors.
Google Cloud Storage sets a per-user quota for each user to share available resources fairly. If you have many other applications or systems connected to your Google Cloud account you may encounter issues.

What can you do about it?

If the All-in-One WP Migration plugin cannot connect to your Google Cloud account, please sign out from your account and sign in again in the Google Cloud Storage Settings page of the plugin on your WordPress Console.
Ensure that there are no other applications using your Google Cloud drive at the same time as the All-in-One WP Migration extension. Consider stopping or uninstalling any other third-party applications or services linked to your account. If you share large numbers of documents with other people or the public, consider an alternative solution to Google Cloud Storage.

Please see more specific detail about each error code below:

Invalid Credentials
The All-in-One WP migration plugin cannot connect to your Google Cloud account. Please sign out from your account and sign in again in the Google Cloud Storage Settings of the plugin on your WordPress Console.

The user does not have sufficient permissions for a file
The All-in-One WP migration plugin cannot access a file or folder on your Google Cloud drive. Please check that your 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 already on your drive, please sign out from your account and sign in again in the Google Cloud Storage Settings page of the plugin on your WordPress Console.

Cannot be used within the domain
The All-in-One WP migration plugin cannot access your Google Cloud Storage drive. If you are attempting to backup op or migrate your site whilst logged in on a corporate domain, please check that you can access your cloud storage or contact the domain administrator.

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

Backend Error
An unexpected error occurred with your Google Cloud drive while processing the request. Please try again. Please sign out from your account and sign in again in the Google Cloud Storage Settings page of the plugin on your WordPress Console.

Bad Request
The All-in-One WP migration plugin cannot connect to your Google Cloud account. Please sign out from your account and sign in again in the Google Cloud Storage Settings of the plugin on your WordPress Console.

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

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

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

The user has not granted access to the file
The All-in-One WP migration plugin cannot access a file or folder on your Google Cloud Storage drive. Please check that your cloud 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 on your drive, please sign out from your account and sign in again in the Google Cloud Storage Settings page of the plugin on your WordPress Console.

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

Here is a complete list of HTTP error codes including their meaning in Google Cloud Storage API:

*press control F to search this page

Code: 400 ‘Bad Request’
Message: The request is abnormal or incorrect and not processable.

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

Code: 402 ‘Payment Required’
Message: To proceed, the product requires payment.

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 HTTPP 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 produce a request within the time that the server was able to wait. 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 not 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 content type of the request is a format that the service does not support.

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: Cannot process the request because it is semantically incorrect.

Code: 429 ‘Too Many Requests’
Message: Client application has been throttled and should not attempt to repeat the request until an amount of time has elapsed.

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 ‘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 maximum storage quota has been reached.

Code: 509 ‘Bandwidth Limit Exceeded’
Message: Your app has been throttled for exceeding the maximum bandwidth cap. Your app can retry the request again after more time has elapsed.

Here is a complete list of Google Cloud Storage API errors:

*press control F to search this page

Error: customerEncryptionAlgorithmIsInvalid
Missing an encryption algorithm, or the provided algorithm is not “AE256.”

Error: customerEncryptionKeyFormatIsInvalid
Missing an encryption key, or it is not Base64 encoded, or it does not meet the required length of the encryption algorithm.

Error: customerEncryptionKeyIsIncorrect
The provided encryption key is incorrect.

Error: customerEncryptionKeySha256IsInvalid
Missing a SHA256 hash of the encryption key, or it is not Base64 encoded, or it does not match the encryption key.

Error: invalidAltValue
The value for the alt URL parameter is unrecognizable.

Error: invalidParameter
The value for one of the URL parameters was invalid. In addition to normal URL parameter validation, any URL parameters that have a corresponding value in provided JSON request bodies must match if they are both specified. If using JSONP, you will get this error if you provide an alt parameter that is not json.

Error: notDownload
Uploads or normal API request send to a /download/* path. Use the same path, but without the /download prefix.

Error: notUpload
Downloads or normal API request send to a /upload/* path. Use the same path, but without the /upload prefix.

Error: parseError
Could not parse the body of the request according to the provided Content-Type.

Error: push.channelIdInvalid
Channel id must match the following regular expression: [A-Za-z0-9\\-_\\+/=]+

Error: push.channelIdNotUnique
storage.objects.watchAll’s id property must be unique across channels.

Error: push.webhookUrlNoHostOrAddress
storage.objects.watchAll’s address property must contain a valid URL.

Error: push.webhookUrlNotHttps
storage.objects.watchAll’s address property must be an HTTPS URL.

Error: required
A required URL parameter or required request body JSON property is missing.

Error: resourceIsEncryptedWithCustomerEncryptionKey
A customer-supplied encryption key encrypts the resource, but the request does not provide one.

Error: resourceNotEncryptedWithCustomerEncryptionKey
A customer-supplied encryption key encrypts the resource, but the request provides one.

Error: turnedDown
A request made to an API version has been turned down. Clients will need to update to a supported version.

Error: userProjectInconsistent
The user project specified in the request does not match the user project specifed in an earlier, related request.

Error: userProjectInvalid
The user project specified in the request is invalid, either because it is a malformed project id or because it refers to a non-existent project.

Error: userProjectMissing
The requested bucket has Requester Pays enabled, the requester is not an owner of the bucket, and no user project was present in the request.

Error: wrongUrlForUpload
storage.objects.insert must be invoked as an upload rather than a metadata

Error: AuthenticationRequiredRequesterPays
Access to a Requester Pays bucket requires authentication.

Error: authError
This error indicates a problem with the authorization provided in the request to Cloud Storage. The following are some situations where that will occur:

• The OAuth access token has expired and needs to be refreshed. This can be avoided by refreshing the access token early, but the code can also catch this error, refresh the token and retry automatically.
• Multiple non-matching authorizations were provided; choose one mode only.
• The OAuth access token’s bound project does not match the project associated with the provided developer key.
• The Authorization header was of an unrecognized format or uses an unsupported credential type.

Error: lockedDomainExpired
When downloading content from a cookie-authenticated site, e.g., using the Storage Browser, the response will redirect to a temporary domain. This error will occur if access to said domain occurs after the domain expires. Issue the original request again, and receive a new redirect.

Error: push.webhookUrlUnauthorized
Requests to storage.objects.watchAll will fail unless you verify you own the domain.

Error: required
Access to a non-public method that requires authorization was made, but none was provided in the Authorization header or through other means.

Error: accountDisabled
The account associated with the project that owns the bucket or object has been disabled. Check the Google Cloud Platform Console to see if there is a problem with billing, and if not, contact account support.

Error: countryBlocked
The Cloud Storage JSON API is restricted by law from operating with certain countries.

Error: forbidden
According to the access control policy, the current user does not have access to perform the requested action. This code works even if the resource isn’t there.

Error: insufficientPermissions
According to access control policy, the current user does not have access to perform the requested action. This code works even if the resource isn’t there.

Error: rateLimitExceeded
The Cloud Storage rate limit was exceeded. Retry using exponential backoff.

Error: sslRequired
Requests to this API require SSL.

Error: stopChannelCallerNotOwner
Calls to storage.channels.stop requires that the caller own the channel.

Error: usageLimits.accessNotConfigured
This error implies that for the project associated with the OAuth token or the developer key provided, access to Cloud Storage JSON API has not been made available. This is most commonly because Cloud Storage JSON API is not enabled in the Google Cloud Platform Console, though there are other cases where the project is blocked or has been deleted when this can occur.

Error: UserProjectAccessDenied
The requester does not have authorization to use the project specified in their request. The requester must have either the service usage.services.use permission or the Editor role for the specified project.

Error: UserProjectAccountProblem
There is a problem with the project used in the request that prevents the operation from completing successfully. One issue could be billing. Check the billing page to see if you have a past due balance or if the credit card (or other payment mechanism) on your account has expired. For project creation, see the Projects page in the Google Cloud Platform Console. For other problems, see the Resources and Support page.

Error: userRateLimitExceeded
The developer-specified per-user rate quota was exceeded. If you are the developer, then you can view these quotas at Quotas pane in the Google Cloud Platform Console.

Error: notFound
Either there is no API method associated with the URL path of the request, or the request refers to one or more resources that were not found.

Error: methodNotAllowed
The URL endpoint used in the request does not support  the HTTP verb. This can happen, for example, when using the wrong verb with the /upload or /download URLs.

Error: conflict
A request to change a resource, usually a storage.*.update or storage.*.patch method, failed to commit the change due to a conflicting concurrent change to the same resource. The request can be retried, though care should be taken to consider the new state of the resource to avoid blind overwriting of other agent’s changes.

Error: gone
You have attempted to use a resumable upload session that is no longer available. If the reported status code was not successful, and you still wish to upload the file, you must start a new session.

Error: conditionNotMet
At least one of the pre-conditions you specified did not hold.

Error: uploadTooLarge
The Cloud Storage JSON API supports up to 5 TB objects.
This error may, alternatively, arise if copying objects between locations and/or storage classes can not complete within 30 seconds. In this case, use the Rewrite method instead.

Error: requestedRangeNotSatisfiable
The requested Range cannot be satisfied.

Error: usageLimits.rateLimitExceeded
A Cloud Storage JSON API usage limit was exceeded.
If your application tries to use more than its limit, additional requests will fail. Throttle your client’s requests, and/or use truncated exponential backoff.

Error: backendError
We encountered an internal error. Please try again using truncated exponential backoff.

Error: internalError
We encountered an internal error. Please try again using truncated exponential backoff.

Here is a complete list of cURL error codes:

CURLE_OK (0)
All fine. Proceed as usual.

CURLE_UNSUPPORTED_PROTOCOL (1)
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.

CURLE_FAILED_INIT (2)
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.

CURLE_URL_MALFORMAT (3)
The URL was not properly formatted.

CURLE_NOT_BUILT_IN (4)
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.

CURLE_COULDNT_RESOLVE_PROXY (5)
Couldn’t resolve proxy. The given proxy host could not be resolved.

CURLE_COULDNT_RESOLVE_HOST (6)
Couldn’t resolve host. The given remote host could not be resolved.

CURLE_COULDNT_CONNECT (7)
Failed to connect() to host or proxy.

CURLE_FTP_WEIRD_SERVER_REPLY (8)
The server sent data libcurl couldn’t parse. This use of this error code is for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0.

CURLE_REMOTE_ACCESS_DENIED (9)
We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.

CURLE_FTP_ACCEPT_FAILED (10)
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.

CURLE_FTP_WEIRD_PASS_REPLY (11)
After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code returns.

CURLE_FTP_ACCEPT_TIMEOUT (12)
During an active FTP session, while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.

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. The server has flaws.

CURLE_FTP_WEIRD_227_FORMAT (14)
FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line, this return code rebounds.

CURLE_FTP_CANT_GET_HOST (15)
An internal failure to lookup the host used for the new connection.

CURLE_HTTP2 (16)
The HTTP2 framing layer has a problem. This is somewhat generic and can be one out of several problems, see the error buffer for details.

CURLE_FTP_COULDNT_SET_TYPE (17)
The HTTP2 framing layer has a problem. This is somewhat generic and can be one out of several problems, see the error buffer for details.

CURLE_PARTIAL_FILE (18)
Received an error when trying to set the transfer mode to binary or ASCII.

CURLE_FTP_COULDNT_RETR_FILE (19)
This was either a weird reply to a ‘RETR’ command or a zero byte transfer complete.

CURLE_QUOTE_ERROR (21)
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.

CURLE_HTTP_RETURNED_ERROR (22)
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= 400.

CURLE_WRITE_ERROR (23)
An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback.

CURLE_UPLOAD_FAILED (25)
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.

CURLE_READ_ERROR (26)
There was a problem reading a local file or an error returned by the read callback.

CURLE_OUT_OF_MEMORY (27)
A memory allocation request failed. This is serious badness and can screw things up if this ever occurs.

CURLE_OPERATION_TIMEDOUT (28)
Operation timeout. The specified time-out period was reached according to the conditions.

CURLE_FTP_PORT_FAILED (30)
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.

CURLE_FTP_COULDNT_USE_REST (31)
The FTP REST command returned an error. This should never happen if the server is sane.

CURLE_RANGE_ERROR (33)
The server does not support or accept range requests.

CURLE_HTTP_POST_ERROR (34)
This is an odd error that mainly occurs due to internal confusion.

CURLE_SSL_CONNECT_ERROR (35)
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.

CURLE_BAD_DOWNLOAD_RESUME (36)
The download could not be resumed because the specified offset was out of the file boundary.

CURLE_FILE_COULDNT_READ_FILE (37)
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?

CURLE_LDAP_CANNOT_BIND (38)
LDAP cannot bind. LDAP bind operation failed.

CURLE_LDAP_SEARCH_FAILED (39)
LDAP search failed.

CURLE_FUNCTION_NOT_FOUND (41)
Function not found. Could not find a required zlib function.

CURLE_ABORTED_BY_CALLBACK (42)
Aborted by callback. A callback returned “abort” to libcurl.

CURLE_BAD_FUNCTION_ARGUMENT (43)
Internal error. A function has a bad parameter.

CURLE_INTERFACE_FAILED (45)
Interface error. A specified outgoing interface is not usable. Set which interface to use for outgoing connections’ source IP address with CURLOPT_INTERFACE.

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

CURLE_UNKNOWN_OPTION (48)
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.

CURLE_TELNET_OPTION_SYNTAX (49)
A telnet option string has an illegal format.

CURLE_GOT_NOTHING (52)
Nothing was returned from the server, and under the circumstances, getting nothing is considered an error.

CURLE_SSL_ENGINE_NOTFOUND (53)
The specified crypto engine could not be found.

CURLE_SSL_ENGINE_SETFAILED (54)
Failed to set the selected SSL crypto engine as default!

CURLE_SEND_ERROR (55)
Failed sending network data.

CURLE_RECV_ERROR (56)
Failure with receiving network data.

CURLE_SSL_CERTPROBLEM (58)
problem with the local client certificate.

CURLE_SSL_CIPHER (59)
Couldn’t use the specified cipher.

CURLE_PEER_FAILED_VERIFICATION (60)
The remote server’s SSL certificate or SSH md5 fingerprint was deemed unacceptable. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

CURLE_BAD_CONTENT_ENCODING (61)
Unrecognized transfer encoding.

CURLE_LDAP_INVALID_URL (62)
Invalid LDAP URL.

CURLE_FILESIZE_EXCEEDED (63)
Maximum file size exceeded.

CURLE_USE_SSL_FAILED (64)
Requested FTP SSL level failed.

CURLE_SEND_FAIL_REWIND (65)
When doing a send operation, curl had to rewind the data to retransmit, but the rewinding operation failed.

CURLE_SSL_ENGINE_INITFAILED (66)
Initiating the SSL Engine failed.

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.

CURLE_TFTP_PERM (69)
Permission problem on TFTP server.

CURLE_REMOTE_DISK_FULL (70)
Out of disk space on the server.

CURLE_TFTP_ILLEGAL (71)
Illegal TFTP operation.

CURLE_TFTP_UNKNOWNID (72)
Unknown TFTP transfer ID.

CURLE_REMOTE_FILE_EXISTS (73)
File already exists and will not be overwritten.

CURLE_TFTP_NOSUCHUSER (74)
This error should never be returned by a properly functioning TFTP server.

CURLE_CONV_FAILED (75)
Character conversion failed.

CURLE_CONV_REQD (76)
The caller must register conversion callbacks.

CURLE_SSL_CACERT_BADFILE (77)
Problem with reading the SSL CA cert (path? access rights?)

CURLE_REMOTE_FILE_NOT_FOUND (78)
The resource referenced in the URL does not exist.

CURLE_SSH (79)
An unspecified error occurred during the SSH session.

CURLE_SSL_SHUTDOWN_FAILED (80)
Failed to shut down the SSL connection.

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

CURLE_SSL_CRL_BADFILE (82)
Failed to load CRL file (Added in 7.19.0)

CURLE_SSL_ISSUER_ERROR (83)
Issuer check failed (Added in 7.19.0)

CURLE_FTP_PRET_FAILED (84)
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)

CURLE_RTSP_CSEQ_ERROR (85)
Mismatch of RTSP CSeq numbers.

CURLE_RTSP_SESSION_ERROR (86)
Mismatch of RTSP Session Identifiers.

CURLE_FTP_BAD_FILE_LIST (87)
Unable to parse FTP file list (during FTP wildcard downloading).

CURLE_CHUNK_FAILED (88)
Chunk callback reported an error.

CURLE_NO_CONNECTION_AVAILABLE (89)
(For internal use only, will never be returned by libcurl) No connection available, the session will be queued. (added in 7.30.0)

CURLE_SSL_PINNEDPUBKEYNOTMATCH (90)
Failed to match the pinned key specified with CURLOPT_PINNEDPUBLICKEY.

CURLE_SSL_INVALIDCERTSTATUS (91)
The status returned failure when asked with CURLOPT_SSL_VERIFYSTATUS

CURLE_HTTP2_STREAM (92)
Stream error in the HTTP/2 framing layer.

<

CURLE_RECURSIVE_API_CALL (93)
An API function was called from inside a callback.

CURLE_AUTH_ERROR (94)
An authentication function returned an error.

CURLE_OBSOLETE*
These error codes will never be returned. They were used in an old libcurl version and are currently unused.