Getting 504 Gateway Time-out nginx/1.15.12

Questions
1

Hi, everyone, I’m using npm version of n8n and when trying to use it with: npm n8n start --tunnel getting 504 Gateway Time-out
nginx/1.15.12. I found only answers related to docker version of n8n.
Please give me step by step guide to resolve it like (1.2.3), thank you

when i do
“export WEBHOOK_URL=http://localhost:5678/”

and trying to test what’s app - getting this error

Problem running workflow
Bad request - please check your
parameters

• Show Details
WhatsApp Trigger: (#2200) Callback
verification failed with the following
errors: curl_errno = 28; curl_error =
Operation timed out after 6000
milliseconds with 0 bytes received;
HTTP Status Code = 200; HTTP
Message = Connection established

2

It could be that the tunneling service on n8n’s servers is having trouble reaching the tunnel target host (i.e. your running instance).

If you can run n8n in docker, you could follow those answers you found just to see if it works that way first.

If the n8n tunnel feature doesn’t work, even in docker, there are many other options for establishing a tunnel that allows those public-internet services to reach your n8n instance, so you may want to try one of them and follow their steps to set it up.

Here is a list of tunneling options which includes links and a brief description of each one.

1 Like
3

with docker i got same error, unfortunatelly - is there any way to see why it happens on macos ?

4

There is no specific tool to analyze what might be happening on MacOS or any other OS. The best strategy is to narrow it down by isolating different parts of it, using tools like ping, traceroute, curl, pcap, etc., while also watching the n8n debug logs.

For instance…

  • Try a connection (curl command) from your own machine to localhost, vs 127.0.0.1, vs ::1 to find out if it might be related to ipv4 vs. ipv6 (See this for more about that.)
  • Grab the tunnel URL from one of the webhook trigger nodes and try calling an API endpoint, from your Mac, via the tunnel ( curl --trace curl_trace_data -X GET https://{tunnelid}.hooks.n8n.cloud/api/v1/tags -H 'accept: application/json' -H "X-N8N-API-KEY: {your-api-key} )
    • Note: I haven’t tried this (so I don’t know if it should work), but it’s what I would try to see if it’s reasonable to expect that Telegram could reach your n8n instance for a webhook/trigger call.
  • Try the curl → API request (assuming it worked from your Mac) from a host that is elsewhere on the public internet (e.g. container running on DigitalOcean).
  • Check connections from your Mac to n8n.cloud (be sure the tunnel itself is actually connecting).
  • etc.

Good luck!! Finding where network connections are failing is challenging even without a tunnel layered on top of it all.

BTW, if you want to poke around in source and see how the tunnel is working, see this, and this

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.