Issue running n8n on GCP Cloud Run

[Lisandro_Scofano]

Hi! I’m having issues running a dockered image of n8n in GCP cloud run. I get 404s for any URL im trying to hit. I tried https://n8n-cloudrun-xxxxxxxx.us-central1.run.app/ - https://n8n-cloudrun-xxxxxxxx.us-central1.run.app/setup - https://n8n-cloudrun-xxxxxxxx.us-central1.run.app/signin , etc and none of them work. These are the env variables I configured. Logs look ok, I don’t see any error.

[King_Samuel_David]

Hey @Lisandro_Scofano

You will need to set your webhook url and gui url

N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
WEBHOOK_URL=https://${SUBDOMAIN}.${DOMAIN_NAME}/

Best regards,

Samuel

[Lisandro_Scofano]

Hi Samuel! thanks for you quick reply.

What do you mean by subdomain? Assuming my domain is https://n8n-cloudrun-12345678.us-central1.run.app

[King_Samuel_David]

Yeah, just replace the variable reference part and place the domain u want if no sub, just the fqdn.

But in ure case, the whole url

N8N_HOST=https://n8n-cloudrun-12345678.us-central1.run.app
WEBHOOK_URL=https://n8n-cloudrun-12345678.us-central1.run.app

Samuel

[King_Samuel_David]

oh @Lisandro_Scofano and you may need to change port 443,

makes life easier when doing callback urls for oauths,

Samuel

[Lisandro_Scofano]

I have it configured like the attach and still getting the 404s. is there any specific path I should try to hit after the domain when its loading for the first time?

[King_Samuel_David]

@Lisandro_Scofano 8080 is http, so if u browser it will probably go to https, so need to use 443.

Samuel

[King_Samuel_David]

@Lisandro_Scofano Hopefuly that resolves it

[Lisandro_Scofano]

Hi @King_Samuel_David ! thanks for your help. This is how I have my instance configured now.

When it initiates, when I try to open it, I keep getting the 404s, after some attempts using /signin, /setup , /workflows for some reason it starts to work and then it works fine. It is like it needs some time to start routing the requests which I don’t understand why it happens since I would expect it to work from the first time it’s deployed.

I have a workaround which is trying a few times but if you have any insights about why that happens and if it can be avoid it would be helpful.

Thanks!!

[King_Samuel_David]

Hey @Lisandro_Scofano

It normally just start up time, mine does the same, takes a few seconds for n8n to check incase of crahses, executions etc, you can check in the logs, but as soon as you see the domain name available url, it should be accessible by then.

Feel free to watch the log, even with debug on, but debug not really needed.

Great glad it’s accessible now
Samuel