Need support: after change my gmail password - OAuth Redirect URL not working

Questions
,
1

After changing my password in Google, I experienced access issues with Google credentials. I did re-authenticate the Google OAuth2 credentials and I deleted the existing credentials and added new one. Still, I faced issue that QAuth Redirect us not working as depicted in below snapshot.

image
image1301×427 48 KB

I have also set N8N_PROXY_HOPS to 1 in the environment settings and re-enabled the Cloudflare proxy and the issue is insist.

BTY, the issue in gmail, google drive, google sheet, and also in google contact

Information on your n8n setup

  • n8n version: 1.89.2
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm, self-hosted in proxmox. Connectd with Cloudflare
  • Operating system:
2

have you tried to update redirect url in your google cloud ?

3

Thanks for fast response.
Yes, I did many times and also I created new credential.
Still, the same issue. I have also repeated again after your replay.

4

I created other project and tried to connect to it. It still the issue not resolved. I changed the host and URL redirect. Also I did not resolve the issue.
I used old version of n8n (1.86). The issue it still exist. :frowning:

5

Guys,
I need support please.
I am still facing issue with credentials:
“I’m still unable to access your emails due to an authorization issue”

When I tried to access calendar API, I got this error:
I’ll check your calendar, but I first need to confirm access. Based on prior issues with email permissions, there may be an authorization block.

image
image1302×412 27.2 KB

I checked the Cloudflare logs and I found this error:
2025-04-22T23:34:24Z ERR error=“context canceled” connIndex=2 event=1 ingressRule=1 originService=http://192.yyy.yyy.xx:5678
2025-04-22T23:34:24Z ERR Request failed error=“context canceled” connIndex=2 dest=https://n8n.digital-ai-home.de/mcp/my-functions/sse event=0 ip=yyy.xx.yyy.x type=http

I removed proxying for my n8n domain on Cloudflare. I also set N8N_PROXY_HOPS to 1 in the environment settings and re-enabled the Cloudflare proxy.
Still the issue is no resolved.

6

Hi, when you tested without a proxy did you reconfigure all of the Auth and callback items?

I would recommend testing with a basic workflow (like getting all calendar events) without proxy / MCP / AI (I guess there is a way to get a temp. Public IP for the instance and to lock access to your source IP)

From there you can start adding

Reg,
J.

7

Thanks for the response.
Yes, I ran the test without a proxy and called the tool directly. The issue is still not resolved.

The problem occurred suddenly, as the system was working without issues.
I updated my password for my Google account and I also reauthorize all credentials again.
Then, the system stacked and can not access URL redirect.

It looks like the courpted and invalid credentials still stacked in backend of n8n.
I tried many approaches and I am still stacking in this step. :frowning: