Reverse Proxy real and Forward for IP

[TeamB 2438]

2023-10-01 13:49:54.761 Info Server: http/1.1 POST http://‌‍‍192.168.0.17‌:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=67fdbe4e-e7de-4077-8deb-92e4a16debe6&X-Emby-Client-Version=4.7.14.0&X-Emby-Language=en-gb&reqformat=json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0
2023-10-01 13:49:54.780 Info Server: http/1.1 Response 204 to ‌‍‍192.168.0.17‌. Time: 19ms. http://‌‍‍192.168.0.17‌:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=67fdbe4e-e7de-4077-8deb-92e4a16debe6&X-Emby-Client-Version=4.7.14.0&X-Emby-Language=en-gb&reqformat=json
2023-10-01 13:49:57.162 Info Server: http/1.1 GET http://‌‍‍192.168.0.17‌:8096/emby/videos/89064/hls1/main/779.ts?PlaySessionId=0b540cab5aa94ca489d3f53ed960fff9. Accept=*/*, Connection=keep-alive, Host=192.168.0.17:8096, User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/117.0, Accept-Encoding=gzip, deflate, Accept-Language=en-US,en;q=0.5, Max-Forwards=10, Referer=http://mediahaven/emby/web/index.html, X-REAL-IP=192.168.0.110, X-Original-URL=/emby/videos/89064/hls1/main/779.ts?PlaySessionId=0b540cab5aa94ca489d3f53ed960fff9, X-Forwarded-For=192.168.0.110, X-ARR-LOG-ID=27a4ca9f-32ed-45bd-96b7-7d0eaa323c4a
2023-10-01 13:49:57.302 Info Server: http/1.1 Response 200 to ‌‍‍192.168.0.17‌. Time: 140ms. http://‌‍‍192.168.0.17‌:8096/emby/videos/89064/hls1/main/779.ts?PlaySessionId=0b540cab5aa94ca489d3f53ed960fff9

I am setting up a new server and when setting up the IIS reverse proxy I am not able to get the remote address working, in Emby it always looks to be reporting the servers address and not the client address.

I know this has been covered a lot on the forums but I though by setting the following you had it covered but mine is not working.

X-REAL-IP=192.168.0.110
X-Forwarded-For=192.168.0.110

Is it just these headers you need to set?

I am testing this all on the local network, from what I can see the above headers are ignored if all the traffic is from the local network.

If I force set them to something like 10.10.10.10 in the reverse proxysetup then that IP is used as the remote address but setting to anything on my local net like 192.168.0.X is ignored.

 

 

[Q-Droid 989]

What version of Emby? Current stable ignores them. There's a selection in beta to configure handling of headers.

[TeamB 2438]

36 minutes ago, Q-Droid said:

What version of Emby? Current stable ignores them. There's a selection in beta to configure handling of headers.

yeah it looks like it ignores them if they are not external IPs

looking at the beta now,  found the setting under network in the settings, it looks like you can force to always use them so hopefully that will solve my issue.

[TeamB 2438]

just confirmed this is working as expected in the Beta (4.8.0.49)

All internal local address are reported correctly as the connecting device

 

 

[anthonws 42]

On 10/2/2023 at 5:45 AM, TeamB said:

just confirmed this is working as expected in the Beta (4.8.0.49)

All internal local address are reported correctly as the connecting device

 

 

Are you by any chance using NGINX? If yes, could you share the relevant config to make this work?

I am using NGINX NPM and added this to the "Advanced" tab:

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

With the above config and the Emby option enabled to read proxy headers, it is still not working for me (only shows the NGINX NPM docker container IP).

Thanks!

[TeamB 2438]

8 hours ago, anthonws said:

Are you by any chance using NGINX? If yes, could you share the relevant config to make this work?

I am using NGINX NPM and added this to the "Advanced" tab:

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

With the above config and the Emby option enabled to read proxy headers, it is still not working for me (only shows the NGINX NPM docker container IP).

Thanks!

sorry, i was using iis on windows

this thread should have some info

 

[anthonws 42]

20 hours ago, TeamB said:

sorry, i was using iis on windows

this thread should have some info

 

All good! I sorted the issue. All configs where correct. I just had to take the NGINX NPM container out of its specific network and place it in host, SxS with Emby container (which was already using the host interface).