ampersandrew
@ampersandrew@lemmy.world
- Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address 2 hours ago:
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.
- Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address 2 hours ago:
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.
- Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address 3 hours ago:
I know you said you don’t know anything about the GUI equivalent, so I’m mostly responding to this comment to publicly post how far I’ve gotten off of your tips. There is a “Custom Locations” tab for my proxy host in NPM, but even after attempting to follow this guide I found, I can’t get my custom locations to persist after hitting the Save button.
- Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address 4 hours ago:
When you say “when accessed from outside my home network”, what kind of access is that? Port forward? VPN?
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.
Is 192.168.1.1 your router?
Yes. It’s also .10.1 on the 10 VLAN.
What’s your LAN netmask?
255.255.255.0 on both VLANs
NPM listens on 192.168.10.201 ports and Jellyfin/Komga on 192.168.10.202 ports?
Correct.
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?
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.
- Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address 4 hours ago:
I’m not quite sure where this goes. It’s Nginx Proxy Manager (in case that affects your answer compared to vanilla nginx), and I’m using Docker Desktop for much the same reason: I’m doing as much configuration via GUI as possible. Is this a Docker configuration or an Nginx Proxy Manager configuration? There is a “Custom Nginx Configuration” screen for my Proxy Host; does it go there? In a nested location block?
- Submitted 5 hours ago to selfhosted@lemmy.world | 13 comments