Replies: 3 comments
-
Did you make any progress on the issue? Currently having the same problem, and the fix in this issue does nothing for me. |
Beta Was this translation helpful? Give feedback.
0 replies
-
In my case, the issue was caused by trying to get X-Forwarded-For when it was not HTTPS. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Anyone got a fix for this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So my setup is as follows.
I have a Proxmox server with a number of virtual machines.
All virtual macines are interconnected with private IP addresses (like 10.10.10.x, with x essentially being the VMID)
One virtual machine additionally has a public ip address. It runs nginx-proxy-manager in docker, and receives the traffic on the public IP address, and forwards the traffice to the other virtual machines through the private IP addresses.
This works perfectly except the virtual machines all see the traffic (the IP) as coming from the nginx-proxy-manager.
I've spent hours now trying to get the real client IP address to appear in the access log files on the proxy clients, but nothing works.
So I tried leaving the customer nginx configuration (in the gui) empty, and I have tried adding the lines
With IP being both the public IP address and the private IP address. I tried other combinations I found here and elsewhere, but the bottom line is, nothing ever changes.
On the clients I also tried adding
Again with IP being both the private and the public IP on the nginx-proxy-server, but nothing changes anything.
Surely there must be one correct way to set this up? Is this documented somewhere? I haven't been able to find any, other than man discussions here, and that isn't always clear and usually different situations.
Beta Was this translation helpful? Give feedback.
All reactions