Unable to sign without access token - OAuth Google

Getting Started with n8n
,
21

Worked for me with 1.74.3, AI Starter Kit

22

Same for me, worked because a restored all credentials. Thanks!

23

@Ken_Ssoon 1.74.2 self hosted with docker

1 Like
24

Hi everyone,

I’m new to n8n and currently in the process of evaluating and learning the platform. I’m running n8n on n8n.cloud, version 1.74.3, and facing an issue with my setup.

I believe I’ve configured everything correctly in my Google Console, as I’ve successfully used similar setups in other applications before. However, I’m encountering a problem and can’t seem to resolve it.

If anyone has experienced this issue and found a solution, I’d greatly appreciate it if you could share your insights or guide me in the right direction.

Thanks in advance for your help!

25

Here’s what worked for me:

  • Upgraded n8n to 1.74.3 (self-hosted in Kubernetes)
  • Set N8N_PROXY_HOPS to 1
  • DELETED the credential and recreated
    It did not work when I just tried to create a second credential without deleting the original.
2 Likes
26

Hi guys,

sorry this post was not flagged in the questions category, therefore the n8n team didn’t pick up on it in timely manner…

Can y’all please update to v 1.75 and see if our fix is working?

2 Likes
27

I updated to the n8nio/n8n:next Docker image, but it didn’t work right away. I had to remove the credential again, and then it worked. Thank you very much!

1 Like
28

Finally got it to work with 1.75.2…I looked in the developer console and noticed and error, the error wasn’t with gSheets but gDrive. I enabled gDrive and it worked!

I’m not sure gDrive needs to be enabled by default but it works!

1 Like
29

What version are you running? I did the same running Version: 1.74.0 on Render, with no success.

30

Yes gDrive requires other APIs to function properly. Seems to be on n8n side, and may require updating to fix. Thanks.

31

Just upgraded to 1.75.2, reconnected my account and everything worked like a charm. I am on a self-hosted version on my laptop.

1 Like
32

I also just upgraded to 1.75.2, reconnected my account and everything worked,

1 Like
33

Hi World!!

“I had the same issue, so what I did was exit my workflow and confirm my credentials by signing up using my Gmail account.”

I hope this is helpful for you!

34

What did you do to make it work?

35

I’m new to this too, and using docker running on my NAS, the version is ‘1.97.1

I can’t connect to GDrive - while I have credentials, n8n keeps telling me it’s ’Unable to sign without access token’ ??

36

It looking like my issue is that I’m self hosting via Docker, on a NAS and my host IP is all I have - so for the redirect - Google informs me if I try and put the IP in, it’s an “ Invalid redirect: Must end with a public top-level domain (such as .com or .org).”

37

just want to share a quick tip in case somebody in China and struggling to get n8n to work with Google Sheets or RSS (e.g. YouTube feeds), even with Clash running.

Problem:
Clash is on, but n8n can’t access Google APIs or fetch RSS from YouTube.

Solution:

  1. Use a .bat script (Windows):
@echo off
set HTTP_PROXY=http://127.0.0.1:7890
set HTTPS_PROXY=http://127.0.0.1:7890
n8n

Alternatively, you can run these set commands in CMD before launching n8n.

  1. Enable TUN Mode in Clash:

TUN mode lets all apps (even those that don’t support proxy settings) go through Clash, including n8n’s RSS node.

38

I ran into the same error:

NodeOperationError: Unable to sign without access token

The issue turned out to be with my Google Cloud OAuth setup. In the OAuth consent screen, I hadn’t properly set the User type / Audience.

:white_check_mark: To fix it:

  1. Go to Google Cloud Console → APIs & Services → OAuth consent screen.

  2. Set the Publishing status to In production or at least add your own email as a Test User / Developer email.

  3. Save and re-authorize the Gmail credential in n8n.

Once I did this, Google issued the refresh_token, and the Gmail node started working without the “Unable to sign without access token” error.

Hope this helps anyone stuck on the same problem!

1 Like
39

I am Having problem of access token to add and connect GMail account in n8n though I have followed all the required steps and Google API keys are also enabled.

40

I ran into this issue as well. There is one step I missed in the N8N google ID verification screen. After You get the message connected successfully, you MUST sign in with google, (look at bottom of verification screen. Once that is done you are all set.