Not able to get the client ID after multiple failed attempt? Any one help out with this problem?
using n8n version: 2.23.2
Running n8n via Hostinger (n8n claud, Docker container 5678:5678) self-hosting
Operating System: Ubuntu 24.04
The error you are seeing is actually a generic glitch from Google’s side, not a problem with your n8n installation. Essentially, Google is refusing to save the “Redirect URI” (the link that tells Google where to send the user back to after they log in), but it isn’t giving you a specific reason why. This usually happens because of a security setting or a browser conflict.
The most common fix is to check your “OAuth Consent Screen” settings. Google won’t let you add a specific redirect link if you haven’t first told the system that your entire website domain is trusted. You need to go to the Consent Screen section and add your main domain (the hstgr.cloud part) to the “Authorized Domains” list and save it before trying to add the Client ID again.
Another frequent cause is having multiple Google accounts logged into the same browser. When you have a personal Gmail and a work account open at once, the Google Cloud Console often gets confused about which account has permission to make changes, leading to that “action failed” message. Opening an Incognito or Private window and logging into only one account usually solves this immediately.
You should also consider that some browser extensions, like ad-blockers or privacy shields, can accidentally block the “Save” command that the page sends to Google’s servers. If the button seems to do nothing or triggers an error, try disabling your extensions or using a different web browser entirely to see if the settings will finally save.
Lastly, double-check that the link you pasted is exactly correct, with no extra spaces at the beginning or end. Once you have authorized your domain in the consent screen, logged in via an Incognito window, and disabled any blocking extensions, the “Save” button should work, allowing you to finally get the Client ID and Secret needed for n8n
1 Like
When Google refuses to save the redirect URI with no clear reason, it is almost always one of a few specific things, and the reply above is right that it is on Google’s side, not your n8n install.
Check these in order. The redirect URI has to be exact: https not http, your real domain, and the n8n callback path (ends in /rest/oauth2-credential/callback), no trailing slash mismatch. Google rejects anything that does not match precisely. If you are on a fresh Google Cloud project, make sure you configured the OAuth consent screen first, Google will not let you finish creating credentials until the consent screen exists. And if your n8n is self-hosted on Hostinger, confirm N8N_EDITOR_BASE_URL is set to your full https URL, because the callback n8n shows you (the one you paste into Google) is built from it, and if it is wrong the URI you are entering is wrong too.
Post the exact text Google shows when it refuses and your callback URL (minus the domain if you want) and it is usually obvious which of these it is.
Thank you; this feedback really helps me. 
Thanks once again
Thank you @dima_automation, this really helped me
1 Like
I am having the same issue. This is frustrating. That is such a basic step, Google Apps and N8N connection.I could add credentials using the same callback ID. now also I am getting this unknown, useless error message. I really need help, solving these little problem. The solutions offered are not helpful. I am sure I am not using extra trailing slash or something the cause mismatch. I have also checked the ymal editor. But I am stuck. Please help me!