34
Help with Getting My Reverse Proxy to Forward the Correct IP Address (lemmy.world)
submitted 1 day ago* (last edited 1 day ago) by to c/selfhosted@lemmy.world
39 comments fedilink hide all child comments
 

Hi, folks! I've learned a lot these past 8-9 months in self-hosting, but I'm not sure what's going on with my reverse proxy setup. At this point, I'm only running Nginx Proxy Manager, Jellyfin, and Komga, separated from my home network via VLANs and firewall rules. My home network is 192.168.1.X and hosted services are on 192.168.10.X. Yet when I look at access logs for Jellyfin or Komga, both are reporting access from 192.168.65.1 when accessed from outside my home network. I don't have a 65 subnet, so this is strange. The reverse proxy is run on a mini PC at .10.201, and Jellyfin and Komga are hosted on a NAS at .10.202; all of them run via Docker containers.

The instructions for Jellyfin for reverse proxy just say to list the address for the reverse proxy, which I did using IPv4 and the domain, and various configurations of only one or the other, as well as the 192.168.65.1 address that manifested out of nowhere. I haven't observed any kind of change in IP address reporting after making changes here. I haven't begun to try to configure Komga for the reverse proxy, because I figure until I get it working for Jellyfin and understand how to do it, it probably doesn't matter; I only listed it here as evidence that two different services were reporting the same phantom IP address. I did ask for help on this issue on a Discord server a little while ago, and some of those folks suggested looking at the Docker networks. I left network settings on basically default for all three of these applications, and they all seem to generate something like a 172.17.0.X address, not the 192.168.65.1 that I'm seeing in logs.

I know there are supposed to be extra headers on network packets that these services can be aware of if they know it's going through a reverse proxy first, and I figure this is important for proper monitoring of folks accessing my hosted services, so i want to get this figured out before I start running a few more apps. Any help anyone can offer would be appreciated. A lot of times, the documentation for this stuff is written up with an assumption of more understanding than the person reading it might have. Or maybe I just glanced right by something obvious and stupid.

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 1 point 4 hours ago (1 child)

The common-sense assumption is that you will adjust your Docker daemon settings so that you prevent overlap with your LAN. (Also, I expect lots of tutorials aren’t that high quality to begin with.)

I would say a high quality tutorial doesn't assume that I know anything about Docker, and most of them didn't (which is good, because I don't), but they also didn't seem to expect me to want better logging out of my hosted services. Thanks, the /16 subnetting makes sense. I'll try to edit that json file later today. But we seemingly don't expect this to fix the problem by itself, so other than telling Jellyfin to expect a proxy at the new reported IP address, what should I expect for next steps?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 4 hours ago

    Need to edit the proxy host for Jellyfin in NPM (advanced tab) and send the X-Forwaded-For header to it.

    proxy_set_header X-Forwarded-For $remote_addr;

    And also in Jellyfin settings you have to set the IP that it sees the reverse proxy coming from as a "known proxy", so it knows it can trust that header when it comes from that IP.

    https://jellyfin.org/docs/general/post-install/networking/reverse-proxy/#forwarded-for-headers

  • permalink
  • fedilink
  • source
  • parent