This document describes the error codes and corresponding error messages returned when a request fails.
Content-Type: application/xml
Corresponding HTTP status code: 3XX, 4XX, or 5XX. Please note that for the PUT Object - Copy API, even if the HTTP status code is 200, the response body may still include an error.
<?xml version='1.0' encoding='utf-8' ?>
<Error>
<Code>string</Code>
<Message>string</Message>
<Resource>string</Resource>
<RequestId>string</RequestId>
<TraceId>string</TraceId>
</Error>
The nodes are described as follows:
Node Name (Keyword) | Parent Node | Description | Type |
---|---|---|---|
Error | None | Contains all error messages | Container |
Content of the Container node Error
:
Node Name (Keyword) | Parent Node | Description | Type |
---|---|---|---|
Code | Error | Error code, a unique identifier to locate the error conditions and scenario. The error codes are described in detail below | string |
Message | Error | Specific error message | string |
Resource | Error | Requested resource, which can be a bucket or object URL | string |
RequestId | Error | An ID automatically generated by the server when a request is sent. COS can use it to quickly locate faults | string |
TraceId | Error | An ID automatically generated by the server when a request error occurs. COS can use it to quickly locate faults | string |
4XX errors
HTTP Status Code | Error Code | Description |
---|---|---|
400 Bad Request | ActionAccelerateNotSupported | The acceleration endpoint does not support this operation |
400 Bad Request | AttachmentFull | The number of ACLs and policies has exceeded the upper threshold. For more information, please see Specifications and Limits |
400 Bad Request | BadDigest | Value of the provided Content-MD5 is not the same as the MD5 hash value the server received |
400 Bad Request | BadRquest | The parameter is invalid |
400 Bad Request | BucketAccelerateNotEnabled | The acceleration endpoint is not enabled for the bucket |
400 Bad Request | BucketNameTooLong | The bucket name is too long. For more information, please see “Naming Conventions” in Bucket Overview |
400 Bad Request | BucketVersionNotOpen | Versioning is not enabled for the bucket |
400 Bad Request | DNSRecordVerifyFailed | The DNS record fails to be verified. Please add a CNAME or TXT record. The DNS record takes effect within 10 minutes |
400 Bad Request | EntitySizeNotMatch | The size of the request body is not the same as that specified in the Content-Length request header |
400 Bad Request | EntityTooLarge | The size of the uploaded object exceeds the upper threshold. For more information, please see Specifications and Limits |
400 Bad Request | EntityTooSmall | The size of the uploaded object does not reach the lower threshold. This error is often seen in multipart uploads. For more information, please see Specifications and Limits |
400 Bad Request | ExpiredToken | The temporary token has expired |
400 Bad Request | ImageResolutionExceed | The image resolution exceeds the limit, or the animated image contains too many frames |
400 Bad Request | ImageTooLarge | The image is too large |
400 Bad Request | IncompleteBody | The size of the request body is smaller than that specified in the Content-Length request header |
400 Bad Request | IncorrectNumberOfFilesInPostRequest | Only one object can be uploaded in a POST Object request |
400 Bad Request | InvalidArgument | The argument is invalid. Please check whether the request can take this argument |
400 Bad Request | InvalidBucketName | The bucket name is invalid. For more information, please see Naming Conventions |
400 Bad Request | InvalidCopySource | The source for object replication is invalid |
400 Bad Request | InvalidDelimiter | The delimiter parameter is invalid. It should be one character |
400 Bad Request | InvalidDigest | The provided value of Content-MD5 is invalid |
400 Bad Request | InvalidImageFormat | The image format is invalid |
400 Bad Request | InvalidImageSource | The image source is invalid |
400 Bad Request | InvalidLocationConstraint | The specified location is invalid |
400 Bad Request | InvalidObjectName | The object name is invalid. For more information, please see ObjectKey |
400 Bad Request | InvalidPart | A part for multipart upload is missing |
400 Bad Request | InvalidPartOrder | The part numbers are not continuous |
400 Bad Request | InvalidPicOperations | The Pic-Operations request header is invalid |
400 Bad Request | InvalidPolicyDocument | The policy in the POST Object request is invalid |
400 Bad Request | InvalidRegionName | The endpoint is invalid. For more information, please see Regions and Access Endpoints |
400 Bad Request | InvalidRequest | The request is invalid |
400 Bad Request | InvalidSHA1Digest | The request fails the SHA-1 verification |
400 Bad Request | InvalidTag | The bucket tag is invalid. For more information, please see Bucket Tag Overview |
400 Bad Request | InvalidTargetBucketForLogging | The destination bucket for logging is invalid. The destination bucket must be in the same region as the current bucket |
400 Bad Request | InvalidUploadStatus | If versioning is enabled, you cannot call a JSON API to upload objects. Please use an XML API |
400 Bad Request | InvalidURI | The URI is invalid |
400 Bad Request | InventoryFull | The number of inventory jobs has exceeded the upper threshold |
400 Bad Request | JsonAPINotSupportOnMAZBucket | JSON APIs do not support operations on MAZ buckets. Please use XML APIs |
400 Bad Request | KeyTooLong | The object key is too long. For more information, please see “ObjectKey” in Object Overview |
400 Bad Request | KmsException | A Key Management Service (KMS) exception occurs |
400 Bad Request | KmsKeyDisabled | The provided key is disabled |
400 Bad Request | KmsKeyNotExist | The provided key does not exist |
400 Bad Request | ListPartUploadIdIsEmpty | UploadId is empty |
400 Bad Request | LoggingConfExists | The logging configuration already exists |
400 Bad Request | LoggingPrefixInvalid | The logging prefix is invalid |
400 Bad Request | MalformedPolicy | The policy format is invalid |
400 Bad Request | MalformedPOSTRequest | The request body content of the current POST request is invalid |
400 Bad Request | MalformedXML | The XML syntax of the request body is incorrect |
400 Bad Request | MAZOperationNotSupportOnOAZBucket | OAZ buckets do not support MAZ operations |
400 Bad Request | MissingRequestBodyError | The request body is missing |
400 Bad Request | MultiAZFeatureNotSupport | The current region does not support the MAZ feature |
400 Bad Request | MultiBucketNotSupport | Only one destination bucket can be set for cross-region replication |
400 Bad Request | NotifyRuleEventConflict | Notification rules (event) conflict |
400 Bad Request | NotifyRulePrefixConflict | Notification rule prefixes conflict |
400 Bad Request | NotifyRuleSuffixConflict | Notification rule suffixes conflict |
400 Bad Request | NotSupportedStorageClass | The specified Storage Class is not supported |
400 Bad Request | OAZOperationNotSupportOnMAZBucket | MAZ buckets do not support OAZ operations |
400 Bad Request | PolicyFull | The number of ACLs and policies exceeds the upper threshold. For more information, please see Specifications and Limits |
400 Bad Request | PolicyVersionFull | The number of policy versions exceeds the limit |
400 Bad Request | RequestTimeout | The request timed out |
400 Bad Request | SsecDecryptHeaderInvalid | The source object is encrypted with SSE-C. Therefore, the same key should be provided in the request header |
400 Bad Request | SSEContentNotSupported | The encryption method is not supported |
400 Bad Request | SSEHeaderNotAllowed | The operation does not support the specified SSE header |
400 Bad Request | TargetBucketNameInvalid | The destination bucket is invalid. For more information, please see Naming Conventions |
400 Bad Request | TooManyBuckets | The number of buckets exceeds the upper threshold (200) |
400 Bad Request | UnexpectedContent | The request does not support the related content |
400 Bad Request | UserCnameInvalid | The specified CNAME does not exist or is invalid |
400 Bad Request | UserNetworkTooSlow | The network speed is too slow |
400 Bad Request | VerifyAlgorithmNotSupported | The verification algorithm is not supported |
400 Bad Request | WebsiteURLInvalid | The custom URL is invalid |
400 Bad Request | XMLSizeLimit | The length of XML exceeds the limit |
402 Payment Required | PaymentRequired | The cost quota is used up |
403 Forbidden | AccessDenied | The access is denied due to an incorrect signature or permission. For more information, please see Request Signature and ACL Overview |
403 Forbidden | AccessForbidden | The cross-origin resource sharing (CORS) request is denied. Please check whether Origin , Access-Control-Request-Method , and Access-Control-Requet-Headers in the request method or request header are in the configured CORS allowlist |
403 Forbidden | InvalidAccessKeyId | The SecretID does not exist |
403 Forbidden | InvalidObjectState | The storage class and requested operation conflict |
403 Forbidden | NoProcessAuthority | You do not have permission to process images |
403 Forbidden | RequestTimeTooSkewed | The difference between the local time and server time is more than 15 minutes |
403 Forbidden | Request has expired | The signature has expired when you initiate the request, or your system time is out of sync with the time in your time zone. For more information, please see FAQs |
403 Forbidden | SignatureDoesNotMatch | The client-computed signature is inconsistent with that computed on the COS server. For more information, please see Request Signature |
403 Forbidden | UserNotSourceBucketOwner | The current user is not the owner of the source bucket |
403 Forbidden | UserNotTargetBucketOwner | The current user is not the owner of the destination bucket |
404 Not Found | InventoryConfigurationNotFoundError | The list of inventory configurations is not found |
404 Not Found | NoBucketQuotaPolicy | The bucket quota policy is not found |
404 Not Found | NoSuchBucket | The specified bucket is not found |
404 Not Found | NoSuchCopySource | The source object to replicate is not found |
404 Not Found | NoSuchCORSConfiguration | The specified CORS configuration is not found |
404 Not Found | NoSuchEncryptionConfiguration | The specified bucket encryption configuration is not found |
404 Not Found | NoSuchJob | The specified Batch Operation job is not found |
404 Not Found | NoSuchKey | The specified object key is not found. You can call HEAD Object to check whether the object exists |
404 Not Found | NoSuchLifecycleConfiguration | The specified lifecycle configuration is not found |
404 Not Found | NoSuchObjectLockConfiguration | The specified object lock configuration is not found |
404 Not Found | NoSuchPolicyVersion | The specified policy version is not found |
404 Not Found | NoSuchTagSet | The specified tag set is not found |
404 Not Found | NoSuchUpload | The UploadId specified in a multipart upload is not found |
404 Not Found | NoSuchVersion | The specified version is not found |
404 Not Found | NoSuchWebsiteConfiguration | The specified static website configuration is not found |
404 Not Found | OriginConfigurationNotFoundError | The origin-pull configuration is not found |
404 Not Found | ReplicationConfigurationNotFoundError | The configuration for cross-region replication is not found |
405 Method Not Allowed | MethodNotAllowed | The resource does not support this HTTP method |
405 Method Not Allowed | RestoreNonArchiveObject | Non-ARCHIVED objects cannot be restored |
405 Method Not Allowed | UploadIdNotSupported | The specified UploadId is generated by a JSON API. Therefore, you cannot operate with an XML API |
409 Conflict | AppendPositionErr | The object length does not match position during the append operation |
409 Conflict | BucketAlreadyExists | The specified bucket already exists |
409 Conflict | BucketAlreadyOwnedByYou | The specified bucket already exists and is owned by the current account |
409 Conflict | BucketLocked | The bucket is locked. In this case, cross-region replication and lifecycle are not supported |
409 Conflict | BucketNotEmpty | The bucket is not empty |
409 Conflict | DomainConfigConflict | The endpoint configurations conflict. Please delete the conflicting records |
409 Conflict | InvalidBucketState | The bucket state conflicts with the request. For example, versioning configuration conflicts with cross-region replication |
409 Conflict | InvalidLockedTime | The object lock time is invalid |
409 Conflict | ObjectLocked | The object is locked. In this case, you cannot overwrite upload or delete the object, or modify the object metadata through copying |
409 Conflict | InvalidObjectState | The object state conflicts with the request |
409 Conflict | PathConflict | Millisecond-level concurrency conflict occurs for objects with the same name |
409 Conflict | QuotaConflict | The quota conflicts |
409 Conflict | QuotaOperationConfilct | The bucket state does not support this operation |
409 Conflict | RecordAlreadyExist | The DNS record conflicts. Please delete the conflicting record, or add a CNAME/TXT record |
409 Conflict | RestoreAlreadyInProgress | The object is being restored |
409 Conflict | UploadConflict | Uploading the same object key too many times causes a conflict |
409 ObjectNotAppendale | ObjectNotAppendable | The specified object is not appendable |
411 Length Required | MissingContentLength | The Content-Length request header is missing |
412 Precondition Failed | PreconditionFailed | The precondition matching failed |
416 Requested Range Not Satisfiable | InvalidRange | The requested object range is invalid |
451 Unavailable For Legal Reasons | DomainAuditFailed | The domain name does not have an ICP license |
451 Unavailable For Legal Reasons | UnavailableForLegalReasons | Unavailable due to legal reasons. You can submit a ticket for details |
5XX errors
HTTP Status Code | Error Code | Description |
---|---|---|
500 Internal Server Error | InternalError | Internal error of the server occurs |
500 Internal Server Error | KmsInternalException | KMS internal error occurs |
501 Not Implemented | NotImplemented | The request has not been implemented |
503 Service Unavailable | KmsFreqControl | The KMS access frequency is too high |
503 Service Unavailable | ServiceUnavailable | The service is unavailable. Please retry |
503 Service Unavailable | SlowDown | The access frequency should be slowed down |
Was this page helpful?