Object Storage Service:HTTP status code 404

Cause: The specified customer master key (CMK) cannot be found.

Solution: Make sure that Key Management Service (KMS) is activated and that you specify a valid CMK ID. An example of a CMK ID is 9468da86-3509-4f8d-a61e-6eab1eac****. For more information, see Server-side encryption.

Cause: The specified CMK alias cannot be found.

Solution: Make sure that KMS is activated and that you specify a valid CMK alias. A CMK alias must start with `alias`, for example, alias/example.

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

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

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

Solution: Configure static website hosting for the destination bucket. For more information, see Static website hosting.

Cause: No tags are configured for any objects in the bucket.

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.

Cause: No cross-origin resource sharing (CORS) rules are configured.

Solution: If you want to allow or deny cross-origin requests, configure CORS rules for the destination bucket. For more information, see Cross-origin resource sharing.

Cause: No retention policy is configured.

Solution: If you want to store and use data in a way that prevents deletion and modification, set a retention policy. For more information, see Set a retention policy.

Cause: The specified policy ID does not exist.

Solution: When you lock a retention policy or extend its retention period, specify the correct policy ID. You can call the GetBucketWorm API operation to obtain the policy ID.

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 (\).

  • Use UTF-8 encoding.

  • 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.

Cause: The user does not exist.

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

Cause: The region does not exist.

Solution: For more information about the regions where OSS is available, see Regions and endpoints.

Cause: No lifecycle rules are configured for the bucket.

Solution: To periodically transition objects to the Infrequent Access (IA), Archive Storage, Cold Archive, or Deep Cold Archive storage class, or delete expired objects and fragments to save storage costs, configure lifecycle rules. For more information, see Set a lifecycle rule.

Cause: No inventory rule is configured for the bucket.

Solution: To obtain information about specified objects in a bucket, such as the quantity, size, storage class, and encryption status, configure an inventory rule. For more information, see PutBucketInventory.

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

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

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, 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 that are configured for the bucket to confirm that the requested object did not trigger a deletion rule. For more information, see Set a lifecycle rule.

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

• Check the CRR rules configured for the bucket to confirm that the requested object was not deleted. For more information, see Set up cross-region replication.

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.

• For a multipart upload or resumable upload, the upload is successful if the call to the CompleteMultipartUpload API operation returns an HTTP status code of 200 and a request ID. For more information, see InitiateMultipartUpload.

Cause: The specified object version does not exist.

Solution: When you list, download, or delete a specific version of an object, you must specify the version ID. You can call the ListObjectVersions (GetBucketVersions) API operation to obtain all version IDs of the object.

Cause: The specified LiveChannel does not exist.

Solution: When you use stream ingest to upload videos to OSS, you must create a LiveChannel and obtain its ingest URL. For more information, see RTMP stream ingest.

Cause: No authorization policy is configured for the requested bucket.

Solution: To grant other users access to your OSS resources, configure a bucket policy. For more information, see Grant users access to specified resources using a bucket policy.

Cause: No cross-region replication rules are configured for the bucket.

Solution: To automatically and asynchronously (near real-time) replicate object changes, such as creations, overwrites, and deletions, from a source bucket to a destination bucket for purposes such as disaster recovery or data replication, configure CRR rules. For more information, see Set up cross-region replication.

Cause: The specified cross-region replication rule does not exist.

Solution: When you obtain the CRR progress for a bucket or delete the replication configuration of a bucket, you must specify the replication rule ID. You can call the GetBucketReplication API operation to obtain the replication rule ID of the destination bucket.

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

Solution: Enable the transfer acceleration service for long-distance data transfers to accelerate uploads and downloads of large files in gigabytes or terabytes, or to accelerate downloads of non-static and non-hotspot data. For more information, see Access OSS through transfer acceleration.

Cause: The image channel does not exist.

Solution: Image channels are a concept from an older version of the image processing service, which is no longer updated. We recommend that you use the new image processing features instead. For more information, see Image processing.

Cause: The image style does not exist.

Solution: To quickly perform complex image processing operations, you can create a style that includes multiple image processing parameters. For more information, see Image styles.

Cause: No cache control policy is configured for the bucket.

Solution: To implement different cache control policies, use the cache-control general header in HTTP requests and responses. OSS supports specifying cache-control in API operations such as PutObject, AppendObject, and GetObject.