Gateway timed out - perhaps try again later?

Guys, see this case. I did a GET on the API using postman and it worked perfectly. In postman I copied the cURL of this request and imported it into the HTTP node, when performing the same GET on N8N the request does not work. always give error 504.
I’ve already tested it on my local N8N using vscode and I’ve also tested it on my production N8N on Linux. It’s as if the HTTP node didn’t have some configuration that postman has to be able to make requests.

Information on your n8n setup

  • **n8n version:1.52.2 & 1.45.1
  • **Database (default: SQLite):Postgres
  • **n8n EXECUTIONS_PROCESS setting (default: own, main):default
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):npm
  • **Operating system:Linux and Windows

Hey @leomangueira,

Looking at the error you are getting a 504 back which is fairly well defined here: 504 Gateway Timeout - HTTP | MDN

The request working in Postman is a but unusual though if n8n and Postman are running on the same machine so it could be that a parameter isn’t correct and the server on the other side is returning a 504 even though that isn’t the case.

I would recommend sending the request to either a test n8n webhook from both Postman and n8n or to something like webhook.site so you can compare the data being sent to make sure it is actually the same. It could be that maybe the service you are using blocks the user-agent we use I know this is an issue for IONOS hosted sites but I would be surprised if Mercado is using that.

I used the same postman parameter on the HTTP node, on the N8N it doesn’t work and on postman it works. To ensure that I wasn’t making something wrong, after the request was successfully made in postman, I generated the cURL code and imported it into N8N and it still doesn’t work in N8N. I did the 2 tests on my notebook.

Hey @leomangueira,

Did you try sending the same request to something like webhook.site to see if anything is different? That will show you what is actually being sent and will likely help solve the issue. A 504 is pretty generic and as it is an error from the server without seeing what is sent or having access to the service there is not a lot we can actually do.

I did this test by making a request through postman and another through N8N, there are some differences
Postman:


N8N:

image

these parameters solve the error
cache-control no-cache
accept /

1 Like

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