Troubleshoot common issues

Available in Classic and VPC

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

Troubleshoot CORS errors

A CORS error occurred.
"The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed." error message is displayed.

Cause

A Cross-Origin Resource Sharing (CORS) error is a security-related error that occurs when the web browser accesses resources of different sources. It occurs because the web browser limits access to the resources of different sources for security.
This header allows only 1 value according to the CORS policy. If it is set in Global Edge and the original, the error may occur due to value duplication.

Solution

Enable the feature of adding CORS headers in Global Edge.

Enable CORS feature
To enable the CORS feature for easily adding CORS HTTP headers:

1. From NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Click an edge from the edge list.
3. Click Rule builder > Managed rule on the left menu of the screen.
4. Enable the CORS feature.

Troubleshoot 401 error issues

During requesting of Global Edge Profile APIs, an Expired Time error occurs.
A 401 error occurs.

Cause

A 401 error occurs largely due to a client's invalid request.

Solution

• Check the Access Key and Secret Key values used when requesting API calls.
  • You can check Access Key and Secret Key under My Account > Manage account and security > Manage security > Manage access in the NAVER Cloud Platform console.
• Check the value of Timestamp used to create Signature is the same as the Timestamp value passing to header in the APIs call.
  • Timestamp value must be in milliseconds.
• Check whether URI used in creating Signature is the value excluding host domain.
  • Example: /api/v1/profiles
• Method used in creating Signature should be the same as the value of Method when calling. For more information, see Ncloud APIs.

404 NoSuchKey error

A 404 NoSuchKey error occurs.

Cause

A 404 NoSuchKey error occurs when the requested object doesn't exist in the bucket.

Solution

You must check whether the object name you request is correct.
To view the returned key value using CLI commands:

aws s3api --endpoint-url=https://kr.object.gov-ncloudstorage.com list-objects-v2 --bucket <bucket_name

The key value actually stored may have special characters or spaces or include "/" before the path.

Troubleshoot AccessDenied error issues

I connected the domain after creating the edge, but an AccessDenied error occurs.

Cause

When the origin is located in Object Storage, there may be an issue with file permissions.

Solution

Change Object Storage file permissions
Set the file permissions you uploaded on Object Storage to "Public." For more information on how to change permissions, see Manage permissions.

Troubleshoot wild certificate application errors

I want to apply the wild certificate to the service domain, but an error occurs.
I received the troubleshoot error message "This value is not available because it is applied by default."

Cause

You cannot enter a wildcard (/*) letter on the service domain depending on the Global Edge policy.

Solution

You cannot enter a wildcard letter on the service domain, so you must add all required directories.

1. From NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Click an edge from the edge list.
3. Click Rule builder on the left menu of the screen.
4. Click Detailed cache rules > [Add cache rules].
5. Add required directories one by one.

Troubleshoot certificate selection unavailable issues

I have the certificate normally issued, but the certificate is not selected in Global Edge.
When I created an edge, I selected the domain issued by NAVER Cloud Platform as the service domain and the domain is issued, but I have to use the service domain as my own domain.

Cause

When you create an edge, you must use the service domain as your own domain.

Solution

Check whether to register certificate
Check whether the certificate is normally registered in Certificate Manager.

Use your own domain as the service domain
To use your own domain as the service domain:

1. From NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Click [View settings] from the edge list.
3. Click [View settings].
4. Copy the address in the CNAME component.
5. Set the domain as CNAME in the DNS system you're operating or hosting company.
6. If you use NAVER Cloud Platform's Global DNS, register CNAME as follows:
7. From NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global DNS > Record.
8. Select the domain and click [Add record].
9. When the Add record window appears, enter the record name and select CNAME for the record type.
10. Select Do not use for Alias feature.
11. Enter the copied domain address in the record value.
12. Click [Add].

Troubleshoot file list hiding issues

When I access the root of the edge domain, I want to set the file list not to be displayed in the XML file.

Solution

Use URL Rewrite feature
You can change root requests into specific URLs using the URL Rewrite feature.

1. From NAVER Cloud Platform console, navigate to > Services > Content Delivery > Global Edge.
2. Click an edge from the edge list.
3. Click Rule builder on the left menu of the screen.
4. Click Detailed cache rules > [Add cache rules].
5. Enter "/" in IF Directory.
6. Click [Advanced settings], and enable URL Rewrite.
7. Enter "/index.html" in Rewrite to.

Set origin path
Create a new folder in the bucket of Object Storage, transfer CDN content to the folder, and enter the newly created directory name in Origin Settings > Origin Path on Global Edge.

To set Object Storage's meta information not to be displayed when you call only the edge domain ("/" root path requests):

1. Create a new folder in the bucket within Object Storage.
2. Click an edge in Global Edge.
3. Enter the folder name you created in the bucket in Origin Settings > Origin Path.
   Example: Enter "/path01."