All Products
Search
Document Center

Object Storage Service:HTTP status code 404

Last Updated:Aug 24, 2023

This topic describes the types of error messages returned with HTTP status code 404, and the common causes of and solutions to these errors.

KeyNotFound

The specified parameter KMS keyId is not found

  • Cause: The specified customer master key (CMK) is not found.

  • Solution: Check whether Key Management Service (KMS) is activated and specify a valid CMK ID in the 9468da86-3509-4f8d-a61e-6eab1eac*** format. For more information, see Configure server-side encryption.

AliasNotFound

The specified Alias is not found

  • Cause: The specified CMK alias is not found.

  • Solution: Check whether KMS is activated and specify a valid CMK alias. The CMK alias must start with alias. Example: alias/example.

NoSuchServerSideEncryptionRule

The server side encryption configuration was not found

  • Cause: Server-side encryption is not enabled for the bucket.

  • Solution: Enable server-side encryption for the bucket. For more information, see Server-side encryption.

NoSuchWebsiteConfiguration

The specified bucket does not have a website configuration

  • Cause: Static website hosting is not configured for the bucket.

  • Solution: Configure static website hosting for the bucket. For more information, see Overview.

NoSuchBucketObjectTagging

The specified bucket does not have a object tagging

  • Cause: None of the objects in the bucket have tags.

  • Solution: Add tags to the objects in the bucket. A tag is a key-value pair used to identify an object. Object tags must comply with the following rules:

    • An object can have up to 10 tags. The tags added to an object must have unique tag keys.

    • A tag key can be up to 128 characters in length. A tag value can be up to 256 characters in length.

    • Tag keys and tag values are case-sensitive.

    • The tag key and tag value can contain letters, digits, spaces, and the following special characters:

      + - = . _ : /

      If the tags in the HTTP header contain characters, the tag keys and tag values must be URL-encoded.

NoSuchCORSConfiguration

The CORS Configuration does not exist

  • Cause: No cross-origin resource sharing (CORS) rules are configured for the bucket.

  • Solution: Configure a CORS rule for the bucket to allow or deny specific cross-origin requests. For more information, see CORS.

NoSuchWORMConfiguration

The WORM Configuration does not exist

  • Cause: No retention policies are configured for the bucket.

  • Solution: Configure a retention policy for the bucket to protect your data from being deleted or modified. For more information, see Configure retention policies.

The specified WORM ID does not exist

  • Cause: The specified retention policy ID does not exist.

  • Solution: Specify a valid policy ID when you lock a retention policy or extend the retention period of the retention policy. You can call the GetBucketWorm operation to obtain the ID of a retention policy.

SymlinkTargetNotExist

The symlink target object does not exist

  • Causes:

    • The name of the object does not comply with the naming rules.

    • The object to which the symbolic link points does not exist.

  • Solutions:

    • Make sure that the object name complies with naming rules.

      The object name must comply with the following naming rules:

      • The name cannot start with a forward slash (/) or a backslash (\).

      • The name must be encoded in UTF-8.

      • The name must be 1 to 1,023 characters in length.

    • If the object specified in the request is a symbolic link, make sure that the object to which the symbolic link points exists.

NoSuchUser

User not found

  • Cause: The specified user does not exist.

  • Solution: Check whether the Alibaba Cloud account that you use is canceled.

NoSuchRegion

NoSuchRegion

  • Cause: The specified region does not exist.

  • Solution: Check the information about the regions of Object Storage Service (OSS). For more information, see Regions and endpoints.

NoSuchLifecycle

No Row found in Lifecycle Table

  • Cause: No lifecycle rules are configured for the bucket.

  • Solution: Configure lifecycle rules for the bucket. This reduces storage costs by deleting expired objects and parts or converting the storage class of objects to Infrequent Access (IA), Archive, Cold Archive, or Deep Cold Archive to save reduce costs. For more information, see Configure lifecycle rules.

NoSuchInventory

No Row found in Inventory Table

  • Cause: No inventories are configured for the bucket.

  • Solution: Configure inventories for the bucket to obtain the information about specific objects in the bucket, such as the number, size, storage class, and encryption status of the objects. For more information, see PutBucketInventory.

NoSuchBucket

The specified bucket does not exist

  • Cause: The name of the bucket does not comply with the naming rules.

  • Solution: Make sure that the bucket name complies with naming rules.

    The bucket name must comply with the following naming rules:

    • The name can contain only lowercase letters, digits, and hyphens (-).

    • The name must start and end with a lowercase letter or digit.

    • The name must be 3 to 63 characters in length.

NoSuchKey

The specified key does not exist

  • Causes:

    • The name of the object does not comply with the naming rules.

    • The object is deleted because a lifecycle rule is triggered.

    • The object is deleted by an authorized user in the OSS console, by using OSS clients, or by calling API operations.

    • Cross-region replication (CRR) is configured for the bucket in which the object is stored. A delete operation that is performed on an object that has the same name in the source or destination bucket is synchronized to the specified object.

  • Solutions

    • Make sure that the object name complies with the naming rules. The name must be 1 to 1,023 characters in length and encoded in UTF-8. The name cannot start with a forward slash (/) or a backslash (\).

    • Check the lifecycle rules of the bucket and make sure that the object is not deleted based on the rules. For more information, see Configure lifecycle rules.

    • Make sure that the object is not deleted by another authorized user.

    • Check the CRR rules that are configured for the bucket and make sure that the object is not deleted based on the CRR rules. For more information, see Configure CRR.

NoSuchUpload

The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed

  • Causes:

    • The request ID is not returned to the client, which indicates that the object failed to be uploaded.

    • Only some parts are uploaded in the multipart upload or resumable upload request.

  • Solutions

    • If this error message is returned when you access an object that you upload, check the returned results and make sure that the request ID is included in the response.

    • If this error message is returned during multipart upload or resumable upload, check the returned results and make sure that HTTP status code 200 and the request ID are returned for the CompleteMultipartUpload operation. For more information, see InitiateMultipartUpload.

NoSuchVersion

The specified version does not exist

  • Cause: The specified version of the object does not exist.

  • Solution: Specify a valid version ID when you list, download, or delete a specific version of an object. You can call the ListObjectVersions (GetBucketVersions) operation to obtain the IDs of all versions of an object.

NoSuchLiveChannel

The specified live channel does not exist

  • Cause: The specified LiveChannel does not exist.

  • Solution: Create a LiveChannel to ingest streams to OSS and obtain the ingest URL. For more information, see Stream ingest over RTMP.

NoSuchBucketPolicy

The specified bucket policy does not exist

NoSuchReplicationConfiguration

The bucket you specified does not have replication configuration

  • Cause: No CRR rules are configured for the bucket.

  • Solution: Configure CRR rules for the bucket to perform automatic and asynchronous (near real-time) replication of objects across buckets in different regions. After you configure CRR rules for a bucket, operations in the source bucket, such as the creation, overwriting, and deletion of objects are synchronized to the destination bucket. This meets your requirements for geo-disaster recovery and data replication. We recommend that you configure CRR rules. For more information, see Configure CRR.

NoSuchReplicationRule

The BucketReplicationRule you specified does not exist

  • Cause: The specified CRR rule does not exist.

  • Solution: Specify a valid CRR rule ID when you query the progress of a CRR task of a bucket or delete a CRR rule configured for a bucket. You can call the GetBucketReplication operation to obtain the IDs of the CRR rules configured for a bucket.

NoSuchTransferAccelerationConfiguration

The bucket you specified does not have transfer acceleration configuration

  • Cause: Transfer acceleration is not enabled for the bucket.

  • Solution: Enable transfer acceleration if you want to accelerate remote data transfer, accelerate the upload and download of objects of gigabytes or terabytes in size, and accelerate the download of non-static and non-hot data. For more information, see Enable transfer acceleration.

NoSuchChannel

No Such Image Channel

  • Cause: The specified image channel does not exist.

  • Solution: Use the latest version of Image Processing (IMG). Earlier versions of IMG are no longer supported. We recommend that you refer to the new IMG guide. For more information, see Overview.

NoSuchStyle

No Such Image Style

  • Cause: The specified image style does not exist.

  • Solution: Create an image style that includes multiple IMG parameters to perform complex operations on image objects in batches. For more information, see Image styles.

NoSuchCacheControlConfiguration

The bucket you specified does not have cache control configuration

  • Cause: No cache control policies are configured for the bucket.

  • Solution: Specify the cache-control header in HTTP requests and responses to configure different cache control policies. The cache-control header is supported by API operations such as PutObject, AppendObject, and GetObject.