Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Google Cloud Translate API

Hello!

Could you please help with our critical issue with the work of Cloud Translation API with our server: from the 19th of August, Cloud Translation API has not been working with our server and we received an error: “That’s an error. Your client does not have permission to get URL <code>/language/translate/v2</code> from this server.“.

Please specify what is the source and reason for this error. Such our actions as creating of the new credential key, and updating of the library did not help. Locally and via the postman it works but not on our server.

Thank you in advance for your help.

0 2 751
2 REPLIES 2

Hello!

You mentioned that the Translation API works locally and via Postman but not on your server. This suggests that there might be a server-specific issue. Here are few thing you could do to troubleshoot the issue.

  • Ensure that the server environment is properly configured and that there are no environment-specific issues.
  • Google Cloud services, by default, require proper authentication and authorization. If the API requests from your server are coming from an IP address that wasn't previously whitelisted or authorized, it could result in this error. Make sure that the IP address of your server is allowed to access the Google Cloud Translation API.
  • Ensure that there are no firewall rules or network configurations that might be blocking outgoing requests from your server to Google Cloud services.
  • Make sure that the client libraries you are using to interact with the Translation API are up to date. Outdated libraries might not support the latest authentication methods or endpoints.
  • If you are using a service account for authentication, double-check that the service account has the necessary permissions to access the Translation API. You can grant permissions in the Google Cloud Console under "IAM & Admin" -> "IAM."

 

Thank you for your help. I solved the issue by changing the API key again and extending rights in the account.