I’m trying to setup a new credentials with Google OAuth2, each time I tryh to login I got a message “Google Sheets OAuth2 API credential “Something went wrong”
On some threads, people who got this error with n8n v2.x solved the issue by upgrading to 2.1.4
I upgraded to 2.1.4 on my self-hosted instance, but I still got the issue. No log entries on the specific error, so it’s hard to point out the root cause
I’m pretty sure my google oauth2 setup is correct : it works well when I was running n8n v1.x
The google sheets credendials that I previously setup when on n9n v1 is still running well, but I cannot setup additionnal google spreadsheets credential since I upgrade n8n to v2
I would try authenticating one more time, and if that still fails maybe switch to a service account. When it errors, there is also a screen in the n8n node called more details, can you paste that in your reply
I got it from another persons post so I removed it.
I tried with another google account, still the same error ; I’m pretty sure the issue is located somewhere in my n8n self-hosted instance, but without explicit error message or error log, it’s hard to troubleshoot
For the service account, I tried but unfortunately the usage of service account is not possible with “google sheets trigger”.
I can still use my pre-existing google sheet credentials which works well, legacy of the n8n v1 before upgrade. I created a workaround by looking every 30 min on a specific value in a specific cell to track an update, but it’s less conveninent than the “on row update” trigger
Any clues about where to find out logs, errors, etc. ?
I use cloud and self-host. When it errors, if you click on the node you can see a more details which will show more details. You can also find it somewhere in the files where your hosting it, but im not fully sure where. If you look in the folder where your hosted n8n is, perhaps it would be in one of those files, I’ll try to look where you can find it on the filesystem for you though.
After many tries I finally find out the root cause. The faulty element is “ClearURLs” add-on with firefox ( ClearURLs ) which basically clean the URL from trackings elements present in the URL