The All-in-One WP Migration plugin uses Amazon S3 Client API to communicate with your account and store your backups. One of these errors may occur if your Amazon S3 drive or the files stored on it do not properly communicate.
Amazon S3 assigns a per-user quota to share resources fairly. If you have many other applications or systems connected to your Amazon S3 Client provider’s account, you may encounter issues.
What can you do about it?
If the All-in-one WP Migration plugin cannot connect to your Amazon S3 drive, please sign out from your account and sign in again in the Amazon S3 Settings page of the plugin on your WordPress Console.
Ensure that there are no other applications using your Amazon S3 drive at the same time as the All-in-One WP Migration extension. If you have other 3rd party applications or other services connected to your Amazon S3 drive, consider stopping or uninstalling them. If you share large numbers of documents with other people or the public, consider an alternative solution to Amazon S3.
Please see more specific detail about each error code below:
Invalid Credentials
The All-in-One WP migration plugin cannot connect to your S3 cloud. Please sign out from your account and sign in again in the Amazon S3 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 Amazon S3. Please check that your account has permissions on the file or folder that you are trying to access with the plugin.
If this doesn’t work or the file is on your drive, sign out and back in on the WordPress Console’s Amazon S3 Settings page.
Cannot be used within the domain
The All-in-One WP migration plugin cannot 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 can access your Amazon S3 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 S3 drive. Please check that the file exists and that you can access it through your drive.
Backend Error
An unexpected error occurred with your S3 cloud while processing the request. Please try again. Please sign out from your account and sign in again in the Amazon S3 Settings page of the plugin on your WordPress Console.
Bad Request
The All-in-One WP migration plugin cannot connect to your Amazon S3 account. Please sign out from your account and sign in again in the Amazon S3 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 S3 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 Amazon S3. Please check that your cloud account has permissions on the file or folder that you are trying to access with the plugin. If this doesn’t work or the file is on your drive, sign out and back in on the WordPress Console’s Amazon S3 Settings page.
Too Many Requests
There have been too many requests on your Amazon S3 account. This can be related to documents that you are sharing publicly from your drive or other applications that are using your S3 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 resource does not allow the HTTP method.
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’
The request must include a Content-Length 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 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’
Message: The client application is making too many requests for the given user and it is being rated limited.
Code: 500 ‘Internal Server Error’
There was an internal error while processing the request.
Code: 501 ‘Not Implemented’
The requested feature has not been 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: expired token
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 may not be uploaded, or the specified entity tag may not have matched the entity tag of the part.
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
SOAP requests must be made 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: malformed XML
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 had not been read from or written to within the timeout period.
Error: RequestTorrentOfBucketError
It is not permitted to request a bucket’s torrent file.
Error: TokenRefreshRequired
The provided token must be refreshed.
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: not signed up
You did not register an account with Amazon S3 and must sign up before you can use it. You can sign up at the following URL: https://aws.amazon.com/s3
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: no such version
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
This resource does not allow the specified method.
Error: BucketAlreadyExists
The requested bucket name is not available. All users of the system share the bucket namespace. 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, 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: operation aborted
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
The requested range could not be satisfied.
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:
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 format of the URL was incorrect.
CURLE_NOT_BUILT_IN (4)
Due to a build-time decision, this libcurl did not have a requested feature, protocol, or option built-in. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and 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 error code is used 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)
When an active FTP session is in use, an error code will be sent over the control connection or something similar while waiting for the server to reconnect.
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 returned.
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 is flawed.
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 is passed back.
CURLE_FTP_CANT_GET_HOST (15)
An internal failure to lookup the host used for the new connection.
CURLE_HTTP2 (16)
There was a problem detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.
CURLE_FTP_COULDNT_SET_TYPE (17)
There was a problem detected in the HTTP2 framing layer. 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 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 things are severely screwed 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)
he 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 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?
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. A required zlib function could not be found.
CURLE_ABORTED_BY_CALLBACK (42)
Aborted by callback. A callback returned “abort” to libcurl.
CURLE_BAD_FUNCTION_ARGUMENT (43)
Internal error. A function was called with a bad parameter.
CURLE_INTERFACE_FAILED (45)
Interface error. A specified outgoing interface could not be used. 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)
The format of a telnet option string was illegal.
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 wasn’t 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 is not OK. 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.