Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address
anamethatisnt@sopuli.xyz 1 week agoLong shot but you might’ve solved the nginx x-forwarded header multiple times without seeing it if the nginx proxy is behind the same bridged docker desktop system setup on your minipc then the visitors IP will show as 192.168.65.1 to the nginx proxy too so you forward that same ip to jellyfin even when it works.
An easy check would be to spin up the nginx proxy manager as a vm instead of a docker image and see if it works.
No real solution, but a lot of chatter regarding that:
github.com/NginxProxyManager/…/674
Thanks, there’s a lot to read through in there, so I’ll see what, if anything, I can apply from it.
anamethatisnt@sopuli.xyz 1 week ago
The main point was that if your mini-pc running the proxy is also behind a windows docker desktop install it too will have incoming connections appear as 192.168.65.1.
A solution then is to switch to a linux docker host where you can get rid of that hidden NAT. There are many webuis for docker such as dockge and portainer on linux without having to use the terminal.
My preffered solution would be to switch to a router/firewall with reverse proxy support such as opnsense with haproxy and skip the nginx proxy manager completely.
Having the proxy configured in the same UI as vlan, port forwarding, nat rules and so on is nice. opnsenselab.com/…/opnsense-haproxy-reverse-proxy/
I have an OPNsense firewall, but I didn’t know it could do that. I was just following guides for the easy route for most of this stuff.
anamethatisnt@sopuli.xyz 1 week ago
Congrats! Then you have a guide for an easy reverse proxy right inside your router. :)
Try it out and see if that doesn’t fit you better than the nginx proxy manager.