Oauth2 generic credentials error - Unable to sign without access token

djjace · January 17, 2025, 6:03am

Having issue with an Oauth2 credential for Ringcentral, it worked fine until recently. it is shwing up as 302 (Found) in the developer admin for ringcentral, but I keep getting “Unable to sign without access token” in N8N

What is the error message (if any)?

Unable to sign without access token

Please share your workflow

Share the output returned by the last node

{
“errorMessage”: “Unable to sign without access token”,
“errorDetails”: {
“rawErrorMessage”: [
“Unable to sign without access token”
]
},
“n8nDetails”: {
“nodeName”: “HTTP Request”,
“nodeType”: “n8n-nodes-base.httpRequest”,
“nodeVersion”: 4.2,
“itemIndex”: 0,
“time”: “1/17/2025, 12:59:43 AM”,
“n8nVersion”: “1.74.1 (Self Hosted)”,
“binaryDataMode”: “default”,
“stackTrace”: [
“NodeApiError: Unable to sign without access token”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:525:33)“,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:632:19)”,
" 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"
]
}
}

Information on your n8n setup

n8nVersion: 1.74.1
platform: docker (self-hosted)
nodeJsVersion: 20.18.0
database: sqlite
executionMode: regular
concurrency: -1
license: enterprise (production)
consumerId: 1352b2dd-df55-4278-abc4-960f143e1068

n8n · January 17, 2025, 6:03am

It looks like your topic is missing some important information. Could you provide the following if applicable.

n8n version:
Database (default: SQLite):
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app):
Operating system:

djjace · January 19, 2025, 8:51pm

Still looking for a solution to this

AugmentERA · January 20, 2025, 7:24am

Hi, i’m new to n8n and i struggle with the same issue but for the Outlook Node.

I’ve tried everything, recreated the App Registration in Azure, checked dlegation and permission, read dozens of tutorials (all showing the same steps to be honest), but nothing seems to help on this behavior.

As for djjace’s case my credentials are as well accepted and the account is connected succesfully, still “unable to sign without access token”.

Running n8n 1.74.3 on Docker.

bNj · January 20, 2025, 10:27am

Same issue for me ! But on another API. Seems a global issue.

AugmentERA · January 20, 2025, 10:51am

I just stumbled about this:

github.com/n8n-io/n8n

OAuth Credential Renaming Error: "Unable to sign without access token"

opened 12:57AM - 15 Jan 25 UTC

closed 11:06AM - 17 Jan 25 UTC

lpadula

in linear

### Bug Description Hello, I've encountered an issue with OAuth credentials …in n8n when renaming the credential title for any Google App. The problem occurs as follows: ### To Reproduce 1. I create OAuth credentials for a Google App (ex. Google Analytics node). 2. I rename the credential (title). 3. After renaming, the following error is thrown: `error: Unable to sign without access token` If I delete and recreate the credential with the final name I want and then add the data, it works perfectly. However, if I rename it again, the error reappears. ### Expected behavior Renaming the credential title should not cause any errors and should function as expected. Thank you for your assistance in resolving this issue. ### Operating System Ubuntu Server 22.04 ### n8n Version 1.73.1 ### Node.js Version last ### Database PostgreSQL ### Execution mode main (default)

It seems the issue got fixed with version 1.75.x, just recreated my docker container with the n8nio/n8n:next image (v.1.75.2) and it works flawless!

Give it a try if this fixes it for you.

timautomation · January 20, 2025, 12:42pm

I have this problem as wel in n8n version 1.74.1

Jon · January 20, 2025, 3:55pm

@timautomation Can you upgrade to at least 1.75.0 which should solve this.

hybridhuman · January 20, 2025, 4:16pm

Experiencing the same issue, currently on `latest 1.74.3’ - self hosted.

liam · January 20, 2025, 4:17pm

please look at the reply directly above yours

timautomation · January 21, 2025, 9:25am

Thanks, but we cannot update yet as it is not the latest version, and we have the policy we do not install the pre-releases/betas.

Hopefully it will be the latest soon.

wrkshp · January 21, 2025, 3:47pm

We seem to be affected by this issue as well, specifically with our Google Drive nodes.

We are on a N8n cloud plan.
Reluctantly, we updated to the latest beta version (1.75.2), but this did not resolve the issue. We now reverted to the latest stable version (1.74.3).

I tried creating a new Google Drive credential with the same client ID and secret as the existing credential on N8n, which temporarily worked. However, after a few hours the issue reappeared but now also for the new credentials.

Jon · January 22, 2025, 3:38am

Hey @wrkshp

I have not seen a case where updating to 1.75 has not resolved the issue, the issue you are reporting should be fixed as it is a known issue in earlier versions so going back to 1.74 will only make it worse.

If you can go back to 1.75 and let me know once it happens again we can do some more digging.

wrkshp · January 22, 2025, 6:51am

Hi @Jon, Thanks for the reply. I will try updating again to 1.75 in the next hour.

I expect the following: The issue should be immediately solved for the existing credentials. There is no need to create new credentials or update existing credentials. Correct? Thanks.

wrkshp · January 22, 2025, 7:51am

Hi @Jon,

We updated to 1.75.2.

I had already created three Google Drive credentials which contain the same client ID and secret. I did this initially when troubleshooting the error. Prior to updating I tried all credentials on 1.74.3 and only one worked. The one which I created last. After updating I tried all credentials on 1.75.2 and again only the last one created worked.

But I want to get the oldest credential back working, because I don’t want to have to update all workflows.

This is the error I encounter when i execute with the oldest credential on 1.75.2

Just before sending this message I removed the two newer Drive credentials. Now only the oldest, the one I want to get working again, remains. I tried again executing with the oldest credential and I encountered the same error. I did this to make sure having multiple similar credentials wasn’t causing the issue.

Perhaps superfluous, but this: Google Cloud app becoming unauthorized | n8n Docs applies to our implementation. I first discovered the issue when reconnecting the account after it expired.

wrkshp · January 22, 2025, 11:25am

Hi @Jon,

It seems to be solved In a classic lightbulb moment I got the idea to reconnect to Google on the oldest credentials and I am happy to report that it solved the issue. Executing Drive nodes with these credentials now works again.

BTW I did reconnect the oldest credentials to Google yesterday, but that was on 1.74.3.

Olesya_A · January 25, 2025, 2:47pm

Hi! I struggle with the same issue but for the YouTube Node.

My n8n instance version is latest (1.75.2 now).
And I have already recreated the account in Google Console several times (before the update from 1.73.3 and after) and reconnected the credentials. When I connecting Oauth2, I see the consent screen, I accept all offers. It connecting successfully.

But the error has not gone away.

ria · January 30, 2025, 2:34pm

Hi @Olesya_A

Did you refresh that list after you’ve added the new credentials to the node?

Alex_Madg · February 19, 2025, 8:53am

I have the same issue but I’m on 1.78.1 could this have been reintroduced?

Paul_Bogemann · February 26, 2025, 9:01am

@Jon We are experiencing the Same Issue on both Google Mail triggers and Outlook Mail Triggers.
Running 1.77.3