Troubleshoot common issues

Available in Classic and VPC

You might run into the following problems when using Object Storage. Find out causes and possible solutions.

Upload error

When I upload files to the bucket with encryption settings, an error occurs.

Cause

When you call the upload API for a bucket or object with encryption settings using the API key of the main account, an error related to permissions may occur.

Solution

View whether you call the upload API with the API key of the main account. Create a sub account and request using the API key of the sub account. For more information, see Encryption settings and Create and manage sub account.

Upload and download multiple files

• I cannot download or upload multiple files at once on the console.
• Only 1 file is uploaded at once on the console.
• Only 1 file is downloaded at once on the console.

Cause

You can upload and download only 1 file in the bucket at once on the console.

Solution

To upload or download multiple files at once, you must use the S3 browser. To integrate with and set the S3 browser:

1. See Create API authentication key and integrate with Amazon S3 to integrate with the S3 browser.
2. Run the S3 browser.
3. Navigate to Menu > Account > Add New Account.
4. Set as follows:
   • Account Type: S3 Compatible Storage
   • REST Endpoint: kr.object.ncloudstorage.com
   • Access Key ID: Enter the access key ID of the NAVER Cloud Platform account.
   • Secret Access Key: Enter the secret access key of the NAVER Cloud Platform account.
   • Use secure transfer (SSL/TLS): Select.
5. View whether the connection is normal in the [Task] tab.
6. Upload or download the file.

404 NoSuchKey error

A 404 NoSuchKey error occurs.

Cause

When the key value actually saved includes special characters or when "/" is included before blank and path, an error may occur.

Solution

You must view the exact object name. To view the object name:

• To view through API, call ListObjectsV2 API.
• To view through CLI, enter the following commands:

  aws s3api --endpoint-url=https://kr.object.ncloudstorage.com list-objects-v2 --bucket <bucket_name> --query 'Contents[].Key'
  

  Note

  For more information, see the Object Storage CLI guide.

• When there are many objects returned, filter the results using the --prefix option.

File access permission

Even though the top level folder is "open," I encounter a message saying you don't have access permission when I upload files.

Cause

When you upload a file, the file is uploaded in a "private" status regardless of the permissions of the folder where the object is uploaded. When the disclosure permission of the file is "private," the error may occur.

Solution

Upload the object through S3 or API and change the object's access restriction settings to "public-read."

• To set ACL you want to apply to objects, see PutObjectACL.
• For the access restriction list, see Access control list (ACL) on the Object Storage API guide.

When you upload the object on the console, click the [Set permissions and metadata] button in the upload window to select whether to be public.

Troubleshoot CORS errors

A Cross-origin resource sharing (CORS) error occurs.

Cause

Occurs when there is an issue in the CORS settings.

Solution

To view and test the bucket's CORS settings with CLI:

1. View CORS rules
   Run the following commands to view whether CORS settings are configured correctly.

   aws --endpoint-url=https://kr.object.ncloudstorage.com s3api get-bucket-cors --bucket <bucket_name>
   

2. Test CORS settings
   Send an OPTION request through curl and set the Origin header and the Access-Control-Request-Method header to view the CORS settings.

   i https://kr.object.ncloudstorage.com/<bucket_name>/<object_name> -H "Access-Control-Request-Method: <method>" --request OPTIONS -H "Origin: <origin>"
   

3. View responses
   View whether there are the Access-Control-Allow-Origin header and the Access-Control-Allow-Methods header in the response header.
   For example, the following headers mean that the CORS request is allowed.
   Access-Control-Allow-Origin: <origin>
Access-Control-Allow-Methods: <method>

To view CORS settings with API, see OptionsObjectCORS API guide.

Access Denied error

When I upload files to Object Storage using Java SDK, an Access Denied error occurs.

Cause

This issue occurs because you upload files and create buckets with API without permission.

Solution

• When you upload files or create folders, you can set the access control list (ACL). For more information, see PutBucketACL.
• You can set whether the uploaded object is public per folder on the console. For more information, see AWS SDK for Java.

Residual multipart upload issue after deleting bucket

Deleted the bucket, but Multipart-upload is remaining.

Cause

When you don't complete multipart upload, the remaining files exist in the bucket. Because the remaining files are included in the bucket capacity and charged, you must delete incomplete multipart objects.

Solution

To view and delete incomplete multipart objects by calling APIs:

1. View the information on canceled or uncompleted multipart upload (see ListMultipartUploads).
2. Stop and delete uncompleted upload among multipart uploads (see AbortMultipartUpload).

For more information on how to view and delete incomplete multipart upload in CLI, see Delete incomplete multipart upload.

When you use Cloud Advisor, you can receive notifications for incomplete multipart upload objects.

Unable to delete data

The data of Object Storage is not deleted.

Cause

The data set with the object lock cannot be deleted.

Solution

The data set with the object lock cannot be deleted and the object lock cannot be canceled until the expiration date. You cannot delete the data, which also affects when you delete your account, so be careful before you set the object lock to the data.