Self hosting on raspberry pi - google cloud > sheets set up not working

Describe the problem/error/question

I have set up an n8n on my raspberry pi via docker, but I am having trouble configuring it to connect to my Google Sheets API. I’ve gone into the Google cloud > set up a project > while setting up credentials, it won’t accept the URL that comes out of n8n.

Seems that I need a public facing url so I used ngrok successfully to access the n8n user interface but the google sheet set up is still suggesting my 192… address.

I’ve exhausted all the AI chatbots trying to figure this out and they all tell me to do the same thing (use the 192… address) which doesn’t work.

What is the error message (if any)?

Gogle could doesn’t like 192….:pensive_face::pensive_face:

I also used ngrok to come up with a public facing URL for my pi. This worked in the sense that I was able to use this temp URL and log into the pi.

I then used this temp ngrok URL in google cloud which accepted it! Here is a ‘fake’ version of what Google accepted
https://[randomwordsthisisntreal]ngrok-free.dev/rest/oauth2-credential/callback

So it looks like the google cloud piece may have worked?

But now n8n isn’t accepting my google cloud details.

Please share your workflow

  1. Installed n8n on my raspberry pi via docker. Not using a SD card, using external hard drive to boot the pi.
  2. Set up google cloud project
  3. I have a client ID and client secret.
  4. Go to n8n google sheets node in a workflow
  5. enter in client ID and client secret
  6. then attempt “sign in with google’ which doesn’t work.

Share the output returned by the last node

none

Information on your n8n setup

Information Point Detail Found Source/Comment
n8n version n8nio/n8n:latest
Database (default: SQLite) SQLite (Default)
n8n EXECUTIONS_PROCESS setting main or own (Default) The environment: section does not contain EXECUTIONS_PROCESS. It will be using the default setting, which in single-instance deployments is effectively own or main.
Running n8n via Docker Confirmed by docker ps and the use of docker-compose.yml.
Operating system Raspberry Pi OS Confirmed by your command prompt.

This may be because you haven’t published your app yet, go to the audience section and change testing to publish

192… is in the private IP address range and can never be used for a public facing OAuth connection or any connection to the outside of your network. To have a public domain including https is the required minimum here. Ngrok or cloudflare tunnels is one possible way to go about it.

After setting this up, you need to change your environment variables of your locally hosted n8n instance accordingly to your domain:

N8N_EDITOR_BASE_URL=https://your-ngrok-url.ngrok.app

WEBHOOK_URL=https://your-ngrok-url.ngrok.app

After these changes, n8n should give you the right callback url looking like this:https://your-ngrok-url.ngrok.app/rest/oauth2-credential/callback

Generally speaking: there are a lot of great guides online that have a step by step explanation for setups like these. Much more detailed and correct than any LLM will provide to you. Here is one for example:https://medium.com/@fayoded/setting-up-n8n-with-docker-and-ngrok-a-beginners-guide-8b76e7d5e661

1 Like