Google Credentials don't work anymore

[FabianMaquen]

##There is a bug that does not allow connecting the Google credentials (especially Google Sheets) and I don't know if other credentials

Error Message

Unable to sign without access token

Please share your workflow/screenshots/recording

## Share the output returned by the last node
Error details

 Other info
n8n version

1.74.3 (Self Hosted)

Time

1/19/2025, 1:37:36 PM

Error cause

{ "message": "Unable to sign without access token", "timestamp": 1737311856190, "name": "NodeApiError", "context": {}, "cause": {} }


## Debug info

### core

- n8nVersion: 1.74.3
- platform: docker (self-hosted)
- nodeJsVersion: 20.18.1
- database: sqlite
- executionMode: regular
- concurrency: -1
- license: enterprise (production)

### storage

- success: all
- error: all
- progress: false
- manual: true
- binaryMode: memory

### pruning

- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions

### client

- userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/130.0.0.0 safari/537.36 opr/115.0.0.0
- isTouchDevice: false

Generated at: 2025-01-19T18:45:32.743Z}

[Joffcom]

Hey @FabianMaquen,

We have created an internal ticket to look into this which we will be tracking as "N8N-8165"

[Joffcom]

Hey @FabianMaquen

Can you try 1.75 and let me know if you have the same issue? I believe this is also a duplicate of another issue so I may end up closing this tomorrow and linking it to the other one.

[LilDaniel0]

I have the same issue righ now, theyre all the google credentials

[Joffcom]

@LilDaniel0 same above if you can, Can you try 1.75 and see if that works? Is it also only failing when using the node as a tool or does it fail under normal use as well?

Have you also made sure your Google API application is set to production and not testing?

[dsebastien]

I face the same issue. My app is in testing. I don't intend on publishing it since it's for my personal use only. Is that mandatory? It seems that it worked that way before

[neverything]

Same issue here on a self-hosted version using an unpublished Google app because internal stuff:

{
  "errorMessage": "Unable to sign without access token",
  "errorDetails": {
    "rawErrorMessage": [
      "Unable to sign without access token"
    ]
  },
  "n8nDetails": {
    "nodeName": "Gmail Trigger",
    "nodeType": "n8n-nodes-base.gmailTrigger",
    "nodeVersion": 1.2,
    "time": "1/20/2025, 12:53:09 PM",
    "n8nVersion": "1.74.3 (Self Hosted)",
    "binaryDataMode": "default",
    "stackTrace": [
      "NodeApiError: Unable to sign without access token",
      "    at PollContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1297:19)",
      "    at PollContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1480:20)",
      "    at PollContext.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Gmail/GenericFunctions.js:54:26)",
      "    at PollContext.poll (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Gmail/GmailTrigger.node.js:231:28)",
      "    at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:651:32)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:872:51",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1206:20"
    ]
  }
}

[Joffcom]

@dsebastien if your app is not in production (doesn't need to be public / published) then the credential will expire after 7 days and we don't have a solution for that as it is something Google make clear for test apps.

@neverything can you try updating to 1.75.0 and let me know if you have the same issue.

[dsebastien]

Fixed it by enabling cloudflare proxying, adding N8N_PROXY_HOPS=1, deleting and recreating the GMail credentials

[Joffcom]

That seems like an unusual fix and one that seems unrelated to the issue, good to know though.

[rudmac]

I just delete it all Google credentials, restart the server and create the credentials again... all set!

[lapms]

In my case, rebooting the server seems to have solved the issue after upgrading to version 1.75.2.