The All-in-One WP Migration plugin uses Amazon Glacier API to communicate with your account and store your backups. If there is an error communicating with your Amazon Glacier drive and the files that are stored in it, you might get one of these errors.
Amazon Glacier 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 Amazon Glacier account you may encounter issues.
What can you do about it?
FIRST STEP: Please save the settings on the Amazon Glacier page of the plugin, especially if you have just installed the plugin. This creates the bucket on your instance and without saving these settings, the backup will fail.
If the All-in-One WP Migration plugin cannot connect to your Amazon Glacier instance, please sign out from your account and sign in again in the Amazon Glacier Settings page of the plugin on your WordPress Console. Please also save the settings page by pressing the update button.
Ensure that there are no other applications using your Amazon Glacier instance 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 Glacier, consider stopping or uninstalling them. If you share large numbers of documents with other people or the public, consider an alternative solution to Glacier.
Please see more specific detail about each error code below:
The All-in-One WP migration plugin can not connect to your Amazon cloud. Please sign out from your account and sign in again in the Amazon Glacier 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 Glacier. 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 Amazon Glacier 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 Amazon S3 cloud. 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 Amazon Glacier storage or contact the domain administrator.
File not found
The All-in-One WP migration plugin cannot access a file or folder on your Amazon Glacier. Please check that the file exists and that you can access it through your drive.
An unexpected error occurred with your Amazon cloud while processing the request. Please try again. Please sign out from your account and sign in again in the Amazon Glacier Settings page of the plugin on your WordPress Console.
The All-in-One WP migration plugin can not connect to your Amazon Glacier account. Please sign out from your account and sign in again in the Amazon Glacier 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 Amazon Glacier 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 Amazon Glacier. 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 Amazon Glacier Settings page of the plugin on your WordPress Console.
Too Many Requests
There have been too many requests on your Amazon Glacier account. This can be related to documents that you are sharing publicly from your drive or other applications that are using your cloud.
Here is a complete list of HTTP error codes:
*press control F to search this page
Code: 400 ‘Bad Request’
Unable to perform AWS API request
Code: 401 ‘Unauthorized’
Required authentication information is either missing or not valid for the resource.
Code: 403 ‘Forbidden’
Access is denied to the requested resource. The user might not have enough permission.
Code: 404 ‘Not Found’
The requested resource doesn’t exist.
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’
Indicates that the request could not be processed because of conflict in it.
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: 500 ‘Internal Server Error’
There was an interntal error 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’
Message: The server does not support the HTTP protocol version used in the request.
Here is a complete list of Amazon S3 API errors:
*press control F to search this page
The email address you provided is associated with more than one account.
The Content-MD5 you specified did not match what we received.
This request does not support credentials.
Your proposed upload is smaller than the minimum allowed object size.
Your proposed upload exceeds the maximum allowed object size.
The provided token has expired.
Indicates that the versioning configuration specified in the request is invalid.
You did not provide the number of bytes specified by the Content-Length HTTP header
POST requires exactly one file upload per request.
Inline data exceeds the maximum allowed size.
The specified bucket is not valid.
The Content-MD5 you specified is not valid.
The encryption request you specified is not valid. The valid value is AES256.
The specified location constraint is not valid. For more information about regions, see How to Select a Region for Your Buckets.
One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part’s entity tag.
The list of parts was not in ascending order.Parts list must specified in order by part number.
The content of the form does not meet the conditions specified in the policy document.
SOAP requests must be made over an HTTPS connection.
The SOAP request body is invalid.
The storage class you specified is not valid.
The target bucket for logging does not exist, is not owned by you, or does not have the appropriate grants for the log-delivery group.
The provided token is malformed or otherwise invalid.
Couldn’t parse the specified URI.
Your key is too long.
The XML you provided was not well-formed or did not validate against our published schema.
The body of your POST request is not well-formed multipart/form-data.
This happens when the user sends malformed xml (xml that doesn’t conform to the published xsd) for the configuration. The error message is, “The XML you provided was not well-formed or did not validate against our published schema.”
Your request was too big.
Your POST request fields preceding the upload file were too large.
Your metadata headers exceed the maximum allowed metadata size.
This happens when the user sends an empty xml document as a request. The error message is, “Request body is empty.”
The SOAP 1.1 request is missing a security element.
Your request is missing a required header.
There is no such thing as a logging status subresource for a key.
Bucket POST must be of the enclosure-type multipart/form-data.
Your socket connection to the server was not read from or written to within the timeout period.
Requesting the torrent file of a bucket is not permitted.
The provided token must be refreshed.
You have attempted to create more buckets than allowed.
This request does not support content.
The email address you provided does not match any account on record.
The bucket POST must contain the specified field name. If it is specified, check the order of the fields.
There is a problem with your AWS account that prevents the operation from completing successfully. Please contact AWS Support for further assistance.
All access to this Amazon S3 resource has been disabled. Please contact AWS Support for further assistance.
Cross-location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location.
The AWS access key Id you provided does not exist in our records.
The operation is not valid for the current state of the object.
All access to this object has been disabled. Please contact AWS Support for further assistance.
The provided security credentials are not valid.
Your account is not signed up for the Amazon S3 service. You must sign up before you can use Amazon S3. You can sign up at the following URL: https://aws.amazon.com/s3
The difference between the request time and the server’s time is too large.
The request signature we calculated does not match the signature you provided. Check your AWS secret access key and signing method.
The specified bucket does not exist.
The specified key does not exist.
The lifecycle configuration does not exist.
The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
Indicates that the version ID specified in the request does not match an existing version.
The specified bucket does not have a bucket policy.
The specified method is not allowed against this resource.
The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.
Your previous request to create the named bucket succeeded and you already own it. You get this error in all AWS regions except US East (N. Virginia) region, us-east-1. In us-east-1 region, you will get 200 OK, but it is no-op (if bucket exists it Amazon S3 will not do anything).
The bucket you tried to delete is not empty.
The request is not valid with the current state of the bucket.
A conflicting conditional operation is currently in progress against this resource. Try again.
Object restore is already in progress.
You must provide the Content-Length HTTP header.
At least one of the preconditions you specified did not hold.
The requested range cannot be satisfied.
We encountered an internal error. Please try again.
A header you provided implies functionality that is not implemented.
Reduce your request rate.
Reduce your request rate.