Couldn’t get a look at it?
Hey @a1ekseev,
I have just given your compose files a go and it oddly enough works for me from n8n.
1650470082.078 194 172.50.0.3 TCP_MISS/200 384 GET http://httpbin.org/ip - HIER_DIRECT/3.231.0.150 application/json
I had to change the network to use 172.50.x as I was already using 172.18.x, I am not sure if I have missed something here but Squid is showing a 200 response and in n8n I get the IP back in my workflow.
What OS and version of Docker do you have installed?
Not sure what OC is but docker is 20.10.12
docker@docker:~/containers/prox$ docker --version
Docker version 20.10.12, build e91ed57
Sorry, Operating system…
I have Docker version:
Docker version 20.10.14, build a224086
I tried the 172.50.x subnet, but that didn’t help.
The subnet shouldn’t make a difference to n8n or the proxy really it is just where it is running, I am using Ubuntu Server 20.04.3 for my host OS. It is running on an old intel nuc, Connected to my home network through a wired connection with no vlans or anything complicated in the way.
I will update docker in the morning and see if that makes any difference but I am not sure it will.
I checked now on the Hetzner Cloud server.
The problem remains…
I am not sure why it is working on my setup ![]()
When you try from n8n do you see anything in the proxy log?
Same as here - Http proxy problem - #21 by a1ekseev
Problem there is I can see that the 501 errors are from n8n when making telemetry calls which wouldn’t impact the HTTP node from running but what about the successful 200 response from httpbin from the .4 address was that from n8n or curl in the container?
Do the HTTP Request node calls show in the log?
I have found the reason.
It’s all about the setting in /etc/docker/daemon.json
{
"iptables": false,
}
For my example with network 172.18.0.0/24, the problem is solved with an iptables rule:
iptables -t nat -A POSTROUTING ! -o docker0 -s 172.18.0.0/16 -j MASQUERADE
Now that is a fantastic find.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.