GeoLocation troubleshooting

Available in Classic and VPC

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

401 - Unauthorized error

A 401 Unauthorized error occurs.
Error message "Request failed with status code 401" is displayed.
Error message "Permission Denied" is displayed.

Cause

When an incorrectly applied header causes an issue in authentication, the error occurs.

Solution

Check the following items:

• Check if the access key and secret key values used in API requests are correct.
• Check if the value of the timestamp used during signature creation is the same as the timestamp value passed to the header in the API call. The timestamp value must be in milliseconds.
• Check if the URI used in signature creation is the value excluding the host domain.
• Check if the method used in signature creation and the method value used when calling are the same.

Troubleshoot GeoLocation APIs access key issuance issues

I couldn't find where to issue a GeoLocation API access key.

Cause

You can issue it from My Account > Account and security management > Security management > Access management in the NAVER Cloud Platform console.

Solution

To issue an authentication key required when calling GeoLocation APIs:

1. In the NAVER Cloud Platform console, navigate to My Account > Account and security management.
2. Enter the account password and click [OK].
3. Click the Security management > Access management.
4. Click [Create a new API authentication key].
5. Check the access key ID and secret key of the API authentication key created, and apply them to request headers.
   • For more information, see Ncloud APIs.

Troubleshoot specific values display issues for foreign IPs

For domestic IP addresses, the response includes the r1 value, but for overseas IP addresses, the r1 value is not included in the response.

Cause

GeoLocation uses 2 IP DBs: "domestic IP DB," which is self-developed to provide domestic information (si, gun, gu, and dong), and "foreign IP DB," which is purchased separately to provide foreign IP information. In the process of providing domestic information, if IP's domestic information does not exist or regional information, such as si, gun, gu, and dong, is not specified, GeoLocation retrieves the foreign IP DB and responds. Therefore, some values (r1, r2, and 3) may be omitted in responses from the foreign IP DB and they may be provided in English.

Solution

As explained in the cause section, it is a normal operation and it does not need any action.

Learning resources

We offer various materials for you to explore. To learn more about GeoLocation, check out these helpful links:

• FAQs: Geolocation FAQs:
• NAVER Cloud Platform blog: GeoLocation API - Adding a Touch of Precision to Your Service!