Google credentials error after sometime

Questions
1

Hey,

I have few workflows with Google nodes and there are working but after sometimes it stops and say this:

image
image1530×766 33.6 KB

I feel that I am doing something wrong, I was thinking that it’s because that this was testing mode. I read somewhere that if on Google console is testing mode then credentials work just 7 days so I changed it to production, but it still stopped working

image
image807×618 39.3 KB

Also, for each app I have different client idk if it can make this problem:

image
image1640×469 46.4 KB

Maybe someone knows why it happening? And how to resolve this?
Thank you in advance :3

2

That is weird. Probably it’s not refreshing the token. What version of n8n are you running?

3

I get a similar issue, i think this is a google setting if I remember correctly.

Using other automated workflow tools, i get the same issue.

4

Always the latest updated via watchtower for docker

image
image1401×85 24.2 KB

@RedPacketSec
Did you resolve that somehow? I was using for other python script other creds and them was working just fine

5

Just re authenticated manually then added error alerting for when it fails

6

Same problem for me since today. I updated to the latest version yesterday. Tested multiple things (add credentials new, reconnect, production & testing mode in Google Console) but nothings works.
Before the update I had no issues at all.
Last version was one of around 1 month ago (don’t have exact version number right now).

Edit:

Authorization failed - please check your credentials

Stacktrace:
NodeApiError: Authorization failed - please check your credentials
    at Object.googleApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GenericFunctions.js:26:15)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Object.googleApiRequestAllItems (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GenericFunctions.js:35:24)
    at async Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Calendar/GoogleCalendar.node.js:342:44)
    at async /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:442:47
7

Hey @maysi,

Welcome to the community :sparkling_heart:

Thank you for reporting the error. Do you experience it only with the Google OAuth or does it happen with other services as well?

I suggest you roll back to 0.138.0. However, if you really need to be on the latest version, you should refer this solution: Get Cookie After Login - #11 by jan

8

Thanks! Currently I only use Telegram API & services with Google OAuth.
I tried to downgrade to 0.138.0 which also didn’t work.
Same for 0.136.0.

When I try to reconnect, after accepting everything in the oauth screen, I get the error:
“Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method).”
Any idea what I’m doing wrong?

9

Hello!

I just tested locally with the latest version and it’s working fine.

It seems that there is a problem with the OAuth credentials you are using.

Maybe could you double check the Client ID, Client Secret and make sure that the callback URL is correctly registered?

I used the Get All Events operation here and it’s working fine after reauthenticating (my app lost connectivity it seems).

10

Probably the same issue to to this? Try out their solution

11

Sharing post from the above thread here:

Yesterday we released version 0.140.0 with a fix for the refresh tokens issue, so I would recommend you upgrade and try running without the N8N_USE_DEPRECATED_REQUEST_LIB flag.

Also there are other issues I am working on now to fix other possible errors. Please bear with us as replacing an inner library unfortunately can have side effects but we’re working hard on fixing all issues.

I believe later today we will be releasing another hotfix (possibly version 0.140.1) with more fixes, so stay tuned :upside_down_face:

2 Likes
12

I now reconnected creds and they’re working. Thanks! <3

3 Likes