Amazon Glacier Extension Error Codes

The All-in-One WP Migration plugin communicates with your account and stores backups using the Amazon Glacier API. You may receive one of these errors if there is an error communicating with your Amazon Glacier drive and the files stored on it.
Amazon Glacier assigns a per-user quota to each user to distribute resources fairly. You may experience problems if you have a large number of other applications or systems linked to your Amazon Glacier account.

What can you do about it?

FIRST STEP: Please save the plugin’s settings on the Amazon Glacier page, especially if you have just installed it. This creates the bucket on your instance. If you don’t save the settings, the backup will fail.

If the All-in-One WP Migration plugin is unable to connect to your Amazon Glacier instance, please sign out of your account and sign back in to the plugin’s Amazon Glacier Settings page in your WordPress Console. Please save the settings page as well by clicking the update button.

Ensure that no other applications are using your Amazon Glacier instance concurrently with the All-in-One WP Migration extension. Consider stopping or uninstalling any third-party Glacier applications or services. Consider an alternative to Glacier 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 Amazon cloud. Please sign out of your account and sign back in to your WordPress Console’s Amazon Glacier Settings plugin.

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 Glacier. 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 drive, please sign out of your account and sign back in to the Amazon Glacier Settings page of the WordPress plugin.

Cannot be used within the domain
The All-in-One WP Migration Plugin is unable to connect to your Amazon S3 cloud. If you are attempting to backup or migrate your site while logged in on a corporate domain, please ensure you have access to your Amazon Glacier storage or contact the domain administrator.

File not found
The All-in-One WP Migration Plugin is unable to access a file or folder on Amazon Glacier. Please double-check that the file exists and that you can access it via your drive.

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

Bad Request
The All-in-One WP Migration Plugin cannot access your Amazon Glacier account. Please sign out of your account and sign back in to your WordPress Console’s Amazon Glacier Settings plugin.

User Rate Limit Exceeded
On your drive, there have been an excessive number of API calls. After stopping drive sync and any other applications that connect to your drive and waiting 5 minutes, try again.

Rate Limit Exceeded
On your drive, there have been an excessive number of API calls. After stopping drive sync and any other applications that connect to your drive and waiting 5 minutes, try again.

Sharing Rate Limit Exceeded
Your Amazon Glacier account’s sharing rate limit has been reached. This could be related to emails or documents that you are publicly sharing from your drive. When performing backups or migrations, avoid sending large volumes of emails. Remove permissions from publicly accessible files on your hard drive.

The user has not granted access to the file
The All-in-One WP Migration Plugin is unable to access a file or folder on Amazon Glacier. Please ensure that the file or folder you are attempting to access with the plugin is accessible via your cloud account. If this does not work, or if the file is already on your drive, please sign out of your account and sign back in to the Amazon Glacier Settings page of the WordPress plugin.

Too Many Requests
Your Amazon Glacier account has received an excessive number of requests. This could be related to documents that you’re publicly sharing from your drive or other applications that use 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 submit a request within the time that the server was willing 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’
The request requires a Content-Length based header.

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 the 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 service does not support the content type of the request format.

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’
There was an internal 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

Error: AmbiguousGrantByEmailAddess
The email address you provided is associated with more than one account.

Error: BadDigest
The Content-MD5 you specified did not match what we received.

Error: CredentialsNotSupported
This request does not support credentials.

Error: EntityTooSmall
Your proposed upload is smaller than the minimum allowed object size.

Error: EntityTooLarge
Your proposed upload exceeds the maximum allowed object size.

Error: ExpiredToken
The provided token has expired.

Error: IllegalVersioningConfigurationException
Indicates that the versioning configuration specified in the request is invalid.

Error: IncompleteBody
You did not provide the number of bytes specified by the Content-Length HTTP header

Error: IncorrectNumberOfFilesInPostRequest
POST requires exactly one file upload per request.

Error: InlineDataTooLarge
Inline data exceeds the maximum allowed size.

Error: InvalidArgument
Invalid Argument

Error: InvalidBucketName
The specified bucket is not valid.

Error: InvalidDigest
The Content-MD5 you specified is not valid.

Error: InvalidEncryptionAlgorithmError
The encryption request you specified is not valid. The valid value is AES256.

Error: InvalidLocationConstraint
The specified location constraint is not valid. For more information about regions, see How to Select a Region for Your Buckets.

Error: InvalidPart
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.

Error: InvalidPartOrder
The list of parts was not in ascending order. Parts list must be specified in the order by part number.

Error: InvalidPolicyDocument
The content of the form does not meet the conditions specified in the policy document.

Error: InvalidRequest
You must make SOAP requests over an HTTPS connection.

Error: InvalidSOAPRequest
The SOAP request body is invalid.

Error: InvalidStorageClass
The storage class you specified is not valid.

Error: InvalidTargetBucketForLogging
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.

Error: InvalidToken
The provided token is malformed or otherwise invalid.

Error: InvalidURI
Couldn’t parse the specified URI.

Error: KeyTooLongError
Your key is too long.

Error: MalformedACLError
The XML you provided was not well-formed or did not validate against our published schema.

Error: MalformedPOSTRequest
The body of your POST request is not well-formed multipart/form-data.

Error: MalformedXML
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.”

Error: MaxMessageLengthExceeded
Your request was too big.

Error: MaxPostPreDataLengthExceededError
Your POST request fields preceding the upload file were too large.

Error: MetadataTooLarge
Your metadata headers exceed the maximum allowed metadata size.

Error: MissingRequestBodyError
This happens when the user sends an empty xml document as a request. The error message is, “Request body is empty.”

Error: MissingSecurityElement
The SOAP 1.1 request is missing a security element.

Error: MissingSecurityHeader
Your request is missing a required header.

Error: NoLoggingStatusForKey
There is no such thing as a logging status subresource for a key.

Error: RequestIsNotMultiPartContent
Bucket POST must be of the enclosure-type multipart/form-data.

Error: RequestTimeout
Your socket connection to the server was not read from or written to within the timeout period.

Error: RequestTorrentOfBucketError
Requesting the torrent file of a bucket is not permitted.

Error: TokenRefreshRequired
You must refresh the provided token.

Error: TooManyBuckets
You have attempted to create more buckets than allowed.

Error: UnexpectedContent
This request does not support content.

Error: UnresolvableGrantByEmailAddress
The email address you provided does not match any account on record.

Error: UserKeyMustBeSpecified
The bucket POST must contain the specified field name. If it is specified, check the order of the fields.

Error: AccessDenied
Access Denied

Error: AccountProblem
There is a problem with your AWS account that prevents the operation from completing successfully. Please contact AWS Support for further assistance.

Error: AllAccessDisabled
All access to this Amazon S3 resource has been disabled. Please contact AWS Support for further assistance.

Error: CrossLocationLoggingProhibited
Cross-location logging not allowed. Buckets in one geographic location cannot log information to a bucket in another location.

Error: InvalidAccessKeyId
The AWS access key Id you provided does not exist in our records.

Error: InvalidObjectState
The operation is not valid for the current state of the object.

Error: InvalidPayer
All access to this object has been disabled. Please contact AWS Support for further assistance.

Error: InvalidSecurity
The provided security credentials are not valid.

Error: NotSignedUp
You did not sign up your account for the Amazon S3 service. Before you can use Amazon S3, you must sign up. You can sign up at the following URL:

Error: RequestTimeTooSkewed
The difference between the request time and the server’s time is too large.

Error: SignatureDoesNotMatch
The request signature we calculated does not match the signature you provided. Check your AWS secret access key and signing method.

Error: NoSuchBucket
The specified bucket does not exist.

Error: NoSuchKey
The specified key does not exist.

Error: NoSuchLifecycleConfiguration
The lifecycle configuration does not exist.

Error: NoSuchUpload
The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.

Error: NoSuchVersion
Indicates that the version ID specified in the request does not match an existing version.

Error: NoSuchBucketPolicy
The specified bucket does not have a bucket policy.

Error: MethodNotAllowed
The specified method is not allowed against this resource.

Error: BucketAlreadyExists
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.

Error: BucketAlreadyOwnedByYou
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).

Error: BucketNotEmpty
The bucket you tried to delete is not empty.

Error: InvalidBucketState
The request is not valid with the current state of the bucket.

Error: OperationAborted
A conflicting conditional operation is currently in progress against this resource. Try again.

Error: RestoreAlreadyInProgress
Object restore is already in progress.

Error: MissingContentLength
You must provide the Content-Length HTTP header.

Error: PreconditionFailed
At least one of the preconditions you specified did not hold.

Error: InvalidRange
Cannot satisfy the requested range.

Error: InternalError
We encountered an internal error. Please try again.

Error: NotImplemented
A header you provided implies functionality that is not implemented.

Error: ServiceUnavailable
Reduce your request rate.

Error: SlowDown
Reduce your request rate.

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

Leave A Comment?