Google Cloud Storage Extension Error Codes

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 stored in your drive, you might get one of these errors.
Google Cloud Storage 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 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. If you have other 3rd party applications or other services that are connected to your account, consider stopping or uninstalling them. 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 can not 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 file
The All-in-One WP migration plugin can not 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 stored 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 can not 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 are able to access your cloud storage or contact the domain administrator.

File not found
The All-in-One WP migration plugin can not 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 can not 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 can not 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 stored 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: 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: 402 ‘Payment Required’
Message: Payment for the product is required in order to proceed.

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 HTTP method in the request is not allowed on the resource.

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 prepared to wait. Repeat the request without modifications at any later time.

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

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

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

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 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 is not supported by the service.

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 interntal 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 was not recognized.

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 was sent to a /download/* path. Use the same path, but without the /download prefix.

Error: notUpload
Downloads or normal API request was sent 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
The resource is encrypted with a customer-supplied encryption key, but the request did not provide one.

Error: resourceNotEncryptedWithCustomerEncryptionKey
The resource is not encrypted with a customer-supplied encryption key, but the request provided one.

Error: turnedDown
A request was made to an API version that 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 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 access control policy, the current user does not have access to perform the requested action. This code applies even if the resource being acted on doesn’t exist.

Error: insufficientPermissions
According to access control policy, the current user does not have access to perform the requested action. This code applies even if the resource being acted on doesn’t exist.

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 require 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 is not enabled. 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 is not authorized to use the project specified in their request. The requester must have either the serviceusage.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 is 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 HTTP verb is not supported by the URL endpoint used in the request. 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.

Leave A Comment?