Comment

Comment on Help with Getting My Reverse Proxy to Forward the Correct IP Address

I really don’t know shit about the GUI tools, but presumably they overlay on the same configuration.

The config I posted would be part of the nginx configuration. You’re instructing it to append the client IP to the X-Forwarded-For header.

There is a “Custom Nginx Configuration” screen for my Proxy Host; does it go there? In a nested location block?

I doubt it, but I’m not sure. The location block would normally be where your reverse proxy configuration would already be, and you’d need to just add that one line. But again, I don’t know how that translates to these GUI tools. Maybe if you search for proxy_add_x_forwarded_for and “Nginx Proxy Manager” you might find what you need.

source

Sort:hotnew top

ampersandrew@lemmy.world ⁨3⁩ ⁨weeks⁩ 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.

source
- badlotus@discuss.online ⁨2⁩ ⁨weeks⁩ ago
  Try setting this in advanced settings:
  
  proxy\_set\_header Host $host; proxy\_set\_header X-Real-IP $remote\_addr; proxy\_set\_header X-Forwarded-For $proxy\_add\_x\_forwarded\_for; proxy\_set\_header X-Forwarded-Proto $scheme;
  
  Image
  
  source
  - ampersandrew@lemmy.world ⁨2⁩ ⁨weeks⁩ ago
    Still the same problem, I’m afraid. I also experimented with putting some of this stuff in the Custom Locations section of NPM’s proxy host settings, since that’s how it looks in Jellyfin’s nginx guide. The only feedback that I got at any point that my changes in NPM were doing anything at all was when my mobile app failed to connect to my server because of how I’d mucked around in there; I did delete those changes before adding your suggestions, of course.
    
    source
    anamethatisnt@sopuli.xyz ⁨2⁩ ⁨weeks⁩ ago
    Long 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
    
    source
    -> View More Comments