Originally published on proxymint.
n8n proxy setup for the HTTP Request node and the whole instance: the Proxy option, HTTPS_PROXY and NO_PROXY, why SOCKS5 falls back, rotation per item, 407s.
TL;DR
- Put the full http:// URL in the Proxy field. Under Options > Proxy on the HTTP Request node, write http://USERNAME:PASSWORD@HOST:PORT. Paste a socks5:// URL or a bare HOST:PORT and n8n drops it and falls back to environment proxy settings. With no applicable environment proxy configured, the request leaves from your server and the node can still go green, which is the failure that eats an afternoon.
- For the whole self-hosted instance, set HTTP_PROXY and HTTPS_PROXY as a pair. Each one covers only targets of its own scheme, so with just HTTPS_PROXY your http:// calls go direct. NO_PROXY lists hosts that skip the proxy, and a lowercase https_proxy left in the container wins over yours.
- Forget SOCKS5 on n8n 2.44.6. As an env var it fails with "Proxy connection ended before receiving CONNECT response". Use your provider's HTTP endpoint instead; over CONNECT the hostname still resolves on the proxy side, so you lose nothing on DNS.
- Rotation comes from the gateway or from an expression. n8n opens one tunnel per request and fires every item at once, so a per-request gateway hands each item its own exit, and {{ $json.proxy }} walks a list item by item.
Key takeaways
- Check the exit before you trust it. Compare the workflow IP with a proxy-disabled request from the same n8n host/network namespace. An empty Proxy field uses environment settings; matching IPs mean investigate, not proof of bypass.
- Always write the scheme. Without http:// in front, the only trace of a skipped proxy is a warning in the server log, and a bare IP:PORT does not even get that.
- Keep the login in the URL, not in a header. A Proxy-Authorization header on the node got 407 on every https:// target, because n8n sends it inside the tunnel and the proxy wants it on the CONNECT.
- Set HTTP_PROXY and HTTPS_PROXY as a pair. Requests to the other scheme leave direct when no other applicable environment proxy is configured, and the execution can look perfectly normal.
- Match rotation to the flow. A new IP per request suits independent items; anything that logs in and then fetches needs sticky or a long timer, and Batching stops a big run from landing as one burst.
Read the full guide on proxymint, with the commands, tables and sources.
Top comments (0)