search

n8n-io / n8n

Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
https://n8n.io
Other
45.51k stars 6.27k forks source link

504 Gateway Time-out #10421

Open Iamtheoldman opened 1 month ago

Iamtheoldman commented 1 month ago

Bug Description

working inside the docker env.

504 Gateway Time-out when connecting google sheets followed the guidlines and still getting the same error

To Reproduce

use https://n8n.io/workflows/2355-get-meta-ads-insights-and-save-them-into-google-sheets/

then connect files at the end google wont let us login instead of getting any other error we get "504 Gateway Time-out nginx/1.15.12"

Expected behavior

not to work will ask all the right things until you contuine and login

Operating System

mac m1

n8n Version

most recent version

Node.js Version

updated

Database

SQLite (default)

Execution mode

main (default)

Joffcom commented 1 month ago

Hey @Iamtheoldman,

We have created an internal ticket to look into this which we will be tracking as "GHC-163"

Joffcom commented 1 month ago

Hey @Iamtheoldman,

Just to double check are you self hosting n8n or using n8n Cloud? You have mentioned Docker in this post but the image you shared on Discord mentions n8n.cloud.

Depending on where you have n8n running this is either going to be an issue with our cloud environment or an issue with your local n8n configuration.

If you are using n8n cloud can you share your cloud username in an email to help@n8n.io if you are self hosting can you check that the url you are being redirected to is correct, it looks like n8n is redirecting to the wrong url possibly because WEBHOOK_URL is not correctly set.

Iamtheoldman commented 4 weeks ago

I am working inside of docker and using a local host, I am not sure what is going on @Joffcom

Joffcom commented 4 weeks ago

Can you share your n8n config and the url you were redirected to? That would be a good starting point, also make sure WEBHOOK_URL is correctly set to the value your reverse proxy is expecting.

At the moment this doesn't sound like a bug and is more of a config issue which is better suited to our support forum but before closing this I can take a quick look at your config.