Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address
Ooops@feddit.org 1 day ago
the 192.168.65.1 address that manifested out of nowhere
Or it’s the internal virtual lan your docker config uses…
Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address
Ooops@feddit.org 1 day ago
the 192.168.65.1 address that manifested out of nowhere
Or it’s the internal virtual lan your docker config uses…
Yeah, that appears to be the case from a link someone else linked here, but I was unable to trace that from anywhere I could find in my containers before.
lemmyvore@feddit.nl 18 hours ago
I think I’ve figured it out. Apparently now Docker also adds an 192.168. range on top of 172. ranges for its bridge networks:
docs.docker.com/engine/network/#automatic-subnet-…
Copy that example to your
/etc/docker/daemon.jsonon the reverse proxy machine, without the 192.168 line, and restart docker, and the 192.168.65. addresses will go away.(Don’t forget to remove the trailing comma on the last address line.)
Well… it’s the default iirc (192.168.65.0/24). So that’s what docker uses if there is no explicit configuration.
lemmyvore@feddit.nl 20 hours ago
Is it?! I always thought that Docker uses 172.16.0.0/16 by default for its networks. Did that get changed at some point?
That’s what the documentation says. I don’t know if/when that changed as I barely use docker.
It appears to be, but I didn’t know that until today. And beyond that, I’ve been trying every permutation of both that IP and the IP of the server on my network in my Jellyfin proxy settings, and it still hasn’t helped to surface the origin IP address.