Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My n8n HTTP Request step fails with an error I do not understand

Short answer

An error from the HTTP Request node is usually the other service refusing the request. 400 means a bad parameter, 403 a login or permission problem, 404 a wrong address, 429 too many requests. Connection refused on a self-hosted n8n is often a Docker address problem. Check the service's own API documentation first.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The step turns red and shows Bad request, Forbidden or Not found.
  • It works in a test tool such as Postman but not in n8n.
  • It worked last week and fails now.
  • I see 'connection refused' when calling something on my own server.
  • A file upload arrives with the wrong name or is rejected.

Why does this happen?

  1. 400 or 404: the request or its address is wrong

    n8n lists the usual causes of a 400 as an invalid name or value in a query parameter, or an array that is not formatted the way the service expects. A 404 means the endpoint address is invalid, from a typo or a deprecated API. For both, n8n advises comparing with the other service's API documentation.

  2. 403: the login is not allowed to do this

    A 403 means authentication failed. n8n suggests checking that the credentials work and that the API key or account has the permissions or scopes for the operation. A new key with the right scopes may be needed.

  3. 429: you are sending too fast

    This is the service telling you that you hit its rate limit. n8n's node has Batching and Retry on Fail options, covered on the rate-limit page.

  4. Connection refused on a self-hosted n8n

    n8n says the most common cause is Docker networking: inside the n8n container, localhost points to the container itself, not to the machine it runs on. The target must be addressed by a name the container can reach. On n8n Cloud there is no path to a service on your own machine.

  5. Files: wrong name or wrong envelope

    With form-data, the file name sent comes from the binary data, not from the Name field, and defaults to 'file' if there is none. A 415 appears when the API wants a multipart upload but the file is sent as the whole body.

What can I do about it today?

  1. Copy the exact error textNote the status number and the message from the other service. Both matter.
  2. Open the other service's API pageCheck that the address, the method and the required fields in n8n match what that page says.
  3. Check the key has not expired or been changedIf it worked before, ask whether anyone rotated a key, changed a password or removed a user at the other service.
  4. Do not paste the key into a chat or emailShare only the error and the step name. Keys stay inside n8n's credentials.
  5. Note when it startedA date helps connect the failure to a change at either end.

When should I bring someone in?

  • The failing step affects orders, payments or customer messages.
  • The error changes between runs.
  • The service's own documentation does not explain the response.

How do I handle it?

  1. Reproduce the call outside n8nI send the same request with a plain tool, so I know whether the fault is in n8n's settings or at the other service.
  2. Read the exact responseThe body of the error usually names the field or permission.
  3. Fix the request, not the symptomCorrect parameters, address or credentials, rather than turning on retries to hide a real error.
  4. Add limits where neededBatching and sensible retry for services that limit requests.
  5. Make failures visibleAn alert that names the step, so the next failure is a message and not a surprise.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Why does it work in Postman but not in n8n?

Usually a difference in headers, body format or credentials. Comparing the two requests side by side finds it.

Should I just turn on Retry on Fail?

Only for temporary errors. A wrong address or permission will fail every time, and n8n limits retries to five tries with at most five seconds between them.

Is the 403 a problem in n8n?

n8n says it means authentication failed, so the fault is in the credentials or their permissions.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.