Hey there! We've found the following might help you get unblocked faster:

• 🧵 N8N - Google API Oauth: Access blocked: authorisation error 400: invalid_request

• 🧵 YouTube Upload Node Works on n8n Cloud, But Fails with 400 Error on Railway

• 🧵 Google Drive API OAuth Redirect Issue on n8n

If you find the answer from one of these, please let us know by solving the thread!

Thank You.
I finally managed to save the link successfully that you offered. Also ChatGPT offered to try with http://localhost:5678/rest/oauth2-credential/callback, and i also managed to save these two links under "Authorized redirect URIs". But it is still error when i trying to login using google nodes (Error 400: redirect_uri_mismatch)

yes

I added a user to the test and gave him rights

I tried to click publish app

I gave all rights to the test user

I also tried through a service account, it worked with it but it has a limitation on creating files in the Google Drive folder, even in the shared folder

Thanks everyone. I bought a domain and now i probably need to wait while it "launching".

But a new problem arose.

I saw on YouTube that you can update n8n via deploy. I thought that maybe this would help somehow and clicked update. So I decided to update everything, redis, postgres, worker and the primary. Now everything except redis has a crash status and you can't log into n8n. In principle, it's not a problem, I created a new space. But in the old space there is a workflow that I worked on for two weeks. This is my first working large workflow. How can I restore access or make a database dump and get the workflow from it?

Errors:
Primary - Connection terminated due to connection timeout

Worker - Connection terminated due to connection timeout

Postgres - 1. database files are incompatible with server.
2. The data directory was initialized by PostgreSQL version 17, which is not compatible with this version 16.10 (Debian 16.10-1.pgdg13+1)
And under "data" section - Deployment Online. This service requires a deployment to be online

Thank you so much!!

Now it work properly. And after i bought and linked an domain name it ok with google accounts now. Of course ive done as much mistkes as it possible nad the last one that i bought domain name from godaddy and it is not that as simple as i touht but with i this manual (https://docs.railway.com/guides/public-networking#redirecting-a-root-domain-workarounds) finaly it began to work.