Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address
lemmyvore@feddit.nl 7 hours ago
Just to understand better:
- When you say “when accessed from outside my home network”, what kind of access is that? Port forward? VPN?
- Is 192.168.1.1 your router?
- What’s your LAN netmask?
- NPM listens on 192.168.10.201 ports and Jellyfin/Komga on 192.168.10.202 ports?
- A connection from the outside comes through the router, gets forwarded to 192.168.10.201:443, the proxy sends it to 192.168.10.202:8096, and it shows up in the Jellyfin logs as coming from 192.168.65.1?
If all of the above is correct I would look at the network interfaces that are up on the mini-PC and the NAS, as well as inside the containers of the proxy and of Jellyfin, and see if there isn’t a 192.168.65.1 up on there somewhere for whatever reason.
You can also try making a manual request (wget, curl, nc) from the proxy container to Jellyfin and see what it shows up as.
May also want to see what’s the DNS situation in your LAN and on those machines. You mentioned “names” being used, how are those defined and resolved?
Last but not least are the containers you mentioned using docker bridge networks or ipvlan?
ampersandrew@lemmy.world 6 hours ago
Accessing via 443 forwarding to my reverse proxy from the internet. My dad will hit my Jellyfin server from his house, and I can hit that server from mobile networks when I’m not on wi-fi.
Yes. It’s also .10.1 on the 10 VLAN.
255.255.255.0 on both VLANs
Correct.
Correct. Jellyfin is actually listening on a different, auto generated, arbitrary port that I just stuck with, but other than that, you got it.
I did check every IP address I could find anywhere on my network and couldn’t find the 192.168.65.X anywhere, but @anamethatisnt@sopuli.xyz here in this thread seems to have identified this as some NAT setting built in to Docker. Running on default settings for network, because I had no idea why I would want to modify any of those settings, they are running as bridge networks.