History
Introduction
API Category
Making API Requests
Region APIs
Instance APIs
Cloud Hosting Cluster APIs
Image APIs
Instance Launch Template APIs
Placement Group APIs
Key APIs
Security Group APIs
Network APIs
Data Types
Error Codes
<?xml version='1.0' encoding='utf-8' ?><Error><Code>string</Code><Message>string</Message><Resource>string</Resource><RequestId>string</RequestId><TraceId>string</TraceId></Error>
Node Name (Keyword) | Parent Node | Description | Type |
Error | None | All error messages | Container |
Error has the following sub-nodes:Node Name (Keyword) | Parent Node | Description | Type |
Code | Error | Error code, which uniquely identifies an error condition and determines the error scenario. 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 |
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 | |
400 Bad Request | BadRequest | Parameter error. |
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 | |
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 key 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 | |
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 | |
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 | One or more parts are 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 (1,000) |
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. For the MAZ feature and its use limits, see MAZ Feature Overview |
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 | |
400 Bad Request | OAZOperationNotSupportOnMAZBucket | MAZ buckets do not support OAZ operations. For the MAZ feature and its use limits, see MAZ Feature Overview |
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 Server-side encrypted 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 limit (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-Request-Headers in the request method or request header are in the configured CORS allowlist |
403 Forbidden | DownloadForbidden | Not allowed to use default domain names (including default bucket domain name, static website domain, and global acceleration domain) to access apk and ipa type files. Please use custom domain name. |
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-calculated signature is inconsistent with that calculated on the COS server. You can refer to Request Signature and use COS's request signature tool to check the signature generation process |
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 | |
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 | Quota conflict |
409 Conflict | QuotaOperationConflict | 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 Conflict | FileAlreadyExists | When uploading an object, use the x-cos-forbid-overwrite:true header. If the object already exists, COS will reject the overwrite request and return an error. |
409 ObjectNotAppendable | ObjectNotAppendable | The specified object is not appendable |
411 Length Required | MissingContentLength | |
412 Precondition Failed | PreconditionFailed | The precondition matching failed |
416 Requested Range Not Satisfiable | InvalidRange | The requested object range is invalid |
424 Failed Dependency | MirrorFailed | Mirror origin server returns 403 |
451 Unavailable For Legal Reasons | DomainAuditFailed | The domain name does not have an ICP license |
451 Unavailable For Legal Reasons | UnavailableForLegalReasons | The service is unavailable. Please check whether your account has overdue payments. If not, check whether there are restricted files by referring to Content Compliance |
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 | Access bandwidth exceeds threshold, triggering flow control. Error information: Connection refused due to traffic overload. Access frequency exceeds threshold, triggering rate limiting. Error information: Message: Reduce your request rate. |
Error Code | Description | Solution |
-103 | Invalid request. The request packet cannot be recognized | Check the content of the request |
-104 | Invalid APPID. The APPID contained in the URL is invalid, or the domain name is not bound to the APPID | Check whether the APPID is correct |
-105 | Invalid style name. The style name or alias specified in the URL is not set | Check the style configuration or style name |
-106 | Invalid URL. The URL format is invalid | Check the URL format |
-107 | Invalid Host header field | Check whether Host is correct |
-108 | Invalid Referer | Check the Referer configuration |
-109 | Invalid style name ID. The image corresponding to the style name is not found. This style name may have been added after the image was uploaded, and therefore data corresponding to this style name could not be generated when the image was uploaded | - |
-110 | The image is on the blocklist | - |
-113 | The file type is not supported | For the input file types supported by file preview, see Rules and Restrictions |
-120 | Data returned by the origin server is exceptional during origin-pull, and consequently image data cannot be properly retrieved | Check the data on the origin server |
-124 | A download offset error has occurred. The setting of Range (checkpoint restart offset) for the HTTP request may be incorrect | Check the checkpoint restart offset setting |
-154 | Download is prohibited for this URL by the original image protection mechanism | Use style access |
-156 | Forcible execution of the 302 process | - |
-162 | Image downloading is not allowed due to overdue payment | Top up your account promptly |
-163 | The business configuration does not exist | Check related configuration items |
-164 | The request frequency is too high | |
-165 | Aggressive download requests are restricted | - |
-166 | The message format is invalid | - |
-167 | The image file is too large and cannot be downloaded | Reduce the size of the file |
-168 | The image file is too large and cannot be downloaded | Reduce the size of the file |
-441 | Unsupported image format. The image cannot be compressed | Use a CI supported image format for image processing. Valid formats: JPG, BMP, GIF, PNG, WEBP |
-442 | The image size exceeds the limit | Ensure that image dimensions are equal to or less than 9,999 pixels |
-443 | Unsupported image format | Use a supported image format. For details, see Rules and Restrictions |
-447 | Image resolution exceeds the limit or the GIF file contains too many frames | Limit image dimensions to 9999 pixels (limit the frame number of GIF files) |
-901 | Compression timeout | - |
-902 | Origin-pull times out. Specifically, when the image storage feature forwards a request to the developer's origin server, the timer expires before a response is received | Check the origin server data or origin-pull configuration |
-3006 | The file is encrypted and cannot be parsed | - |
-3008 | The file is empty and cannot be parsed | - |
-3011 | The file type is not supported | For the input file types supported by file preview, see Rules and Restrictions |
-3015 | The requested page number does not exist | - |
-3075 | This file exceeds 100 MB and cannot be parsed | Ensure that the file size is equal to or less than 100 MB |
-5062 | The image may be illegal | Check whether the content of the image is illegal |
-6101 | The image does not exist, is not uploaded, or has been deleted | Check the source data of the request |
-29033 | The download request does not contain a valid range | - |
-29034 | The download offset is greater than the file size | - |
-29214 | Frequency control is triggered | |
-40168 | The original image is null | Check the raw data of the request |
-46152 | The bucket name is invalid | Check whether the bucket name is valid |
-46154 | The APPID is invalid | Check whether the APPID is valid |
-46614 | Downloading is not allowed for a file that is being uploaded | Send the download request after the file upload is completed |
-46617 | An entry on the blocklist is hit | Check whether the content of the image is illegal |
-46618 | Signature authentication fails | Check whether the signature is correct |
-46619 | The signature has expired | Update the signature |
-46620 | The bucket is blocked | |
-46621 | The bucket is blocked | |
-46627 | The user is currently on the blocklist | |
-46628 | The file does not exist | Check whether the file to be downloaded exists |
-46642 | The APPID does not exist | Check whether the APPID is correct |
-46646 | The file is blocked | The file is blocked. Check whether the content of the file is illegal |
-46661 | No access permission | Contact the resource owner for permission |
Error Code | Description | Solution |
-60998 | An image processing parameter is invalid | Check whether image processing rules are correct |
-60997 | The number of image processing rules exceeds the limit | Persistence processing currently supports a maximum of five rules. Therefore, ensure that at most five rules are configured |
-60996 | The file is too large to process | Ensure that the file size is less than or equal to 32 MB |
-60987 | Failed to retrieve the image | Check the URL of the image |
-60983 | Invalid host | Check the host |
-60972 | Invalid region | Check if the region in the request supports CI. For more information on regions that support CI, see Regions and Domain Names |
-60967 | The image style does not exist | Check the image style |
-60957 | The number of used styles exceeds the limit | Currently, a maximum of 100 styles are supported. If you need more styles, submit a ticket to contact us |
-60955 | Invalid URL | Check whether the URL is correct |
-60950 | No file is specified | Specify the file to be processed in the request |
-60949 | The request frequency is too high | Reduce the request frequency. To increase the frequency limit, submit a ticket |
-60948 | The account is suspected of violation | |
-60938 | Incomplete signing information | Check the required items in the signing information |
-60936 | The request is rejected | Access denied |
-60932 | Signature error | The signature is invalid. Check whether the signing information matches |
-62999 | Invalid image format | Check whether the image format is valid |
Error Code | Description | Solution |
-3006 | The file is encrypted | Use a decrypted file |
-3008 | The file length is 0 | Check whether the file is normal |
-3011 | The file type is not supported | Check whether the file type is supported. For the supported file types, see Rules and Restrictions |
-3064 | File parsing failed | Document parsing failed. Check if the resource is damaged. |
-3070 | File processing timed out and failed. | Task processing timed out and failed. Recommendation for adjustment: single task generation scope. |
-3075 | The document size exceeds the limit. | Document resource limitation, document size can be adjusted. |
Error Code | Description | Solution |
-61011 | The file does not exist | Check whether the file exists |
-65007 | File content error. Decoding failed | Check whether the file format is correct |
-65010 | File download failed | Check whether the file link is correct. For a file with private read permission, the file link must be signed |
-65011 | The file is too large to process | Currently, an excessively large file cannot be moderated |
-65012 | The image resolution is too low to process | Currently, images with excessively low resolution are not supported |
-65013 | The file is not processed because it does not meet requirements (e.g., unsupported file suffix or excessively large size) | Check whether the file meets requirements |
-65014 | No CI role (CI_QCSRole) | Bind a CI role |
-65015 | No moderation scenario is used | Use at least one moderation scenario for moderation |
-65016 | BizType used does not exist | Enter a correct BizType |
Other | Internal error | None |
피드백