Describe the problem/error/question
got error while setting up proxy with ip address instead of domain and non standard port.
if I set up wrong port or IP I got
ERROR: The service refused the connection - perhaps it is offline
if I set up login and password like
123: I got the same
ERROR: Bad request - please check your parameters
What is the error message (if any)?
Please share your workflow
Information on your n8n setup
n8n version: 0.227.1 / 0.236.0 / 1.1.1
Database (default: SQLite): SQLite / PostgreSQL
n8n EXECUTIONS_PROCESS setting (default: own, main): main
Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
Operating system: Ubuntu
@Nick_K_H Sorry you’re running into this!
Would you happen to also have logs from your proxy, too? Also, what proxy are you using? That’d be helpful in understanding a bit more of what’s going on.
This is commercial proxy so I don’t have access to logs.
I can request logs of n8n from our server if it wold help.
Also you can execute a process on your side - it has all the necessary credentials.
The issue not in the IP instead of domain:
I found something - If I request page through
http it works ok, if
https - got error.
http - ok:
https: - error:
1.1.1. GET/POST - doesn’t matter. Only
https scheme in target URL makes a difference.
n8n tries to connect to the proxy via HTTPS despite the scheme in
HTTP Node > Options > Proxy setting as I can see in the traffic logs.
If I’m not specifiyng a scheme in Proxy settings:
get/post + http - ok
get/post + https - error
Found several related topics:
I’ve seen this post about problems with the axios browser here
Http request proxy fails
It proposes rollback to a previous version of the library.
Any way to do this in the n8n Desktop version? I’m also having problems routing requests. In my case via TOR.
I have a TOR node at home with GitHub - dperson/torproxy - It’s making an http proxy.
I perfectly works from CURL in the command line.
Nevertheless SOME requests do not work whilst other do:
To repeat the failure
In the comand line those…
That is interesting to know thanks, I have been thinking about a workaround for this but it won’t be a quick or easy change to make. If your proxy is using squid though it will support https_proxy which will work and is supported by a few browsers like Firefox and Chrome but the browsers don’t really matter as your users would continue to use the existing http_proxy.
06:10PM - 06 Oct 22 UTC
So far, Axios did not support HTTPS requests over HTTP proxies.
This pull req
07:44PM - 15 Jul 23 UTC
This is similar to #5037 but has a simpler implementation adapted from [hpagent]
That looks right to me, So we are aware of some issues when using proxies with n8n which we will be looking to resolve soon. The issue itself comes from the Axios package we use not supporting https over http, If your proxy supports it you can set up https and that will work but depending on what your proxy is used for (content inspection) it may cause other issues.
Hope Axios will approve pull request some day. =)
P.S.: I have no control over the proxy I have to use in my project.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.