Emby Connect and Reverse Proxies

[DePiglio 0]

Hey everyone, I have my server setup with nginx and Cloudflare proxying traffic. When connecting to my server through a browser and using my domain, everything seems to be in order with traffic going through Cloudflare.

 

When using Emby Connect however, traffic is being directed straight to my servers local address, and its ip is exposed. I'm using the external domain setting and changed the public ports to 80 and 443 but this seems to have no effect on how Emby Connect directs traffic.

 

How can I fix this so connecting through Emby Connect also sends you through Cloudflare?

[Luke 42086]

Hi, check the remote address that is displayed on your emby server dashboard. That is what is reported to emby connect, along with the lan ip address for when you are inside your local network.

[DePiglio 0]

The remote address displayed in my dashboard is my domain, however the lan ip is still being exposed when connecting through emby connect, and my server is not hosted on my local network.

 

[Luke 42086]

Well that's because if you do happen to be on the same local network as the server, this will allow the Emby apps to use that address rather than the remote address.

[DePiglio 0]

Emby goes on to connect through the in-home IP though, not the remote domain and It's leading to a worse streaming experience using Emby Connect because its not going through a CDN and nginx.

 

I also think its an issue Emby exposes the LAN IP to everyone who connects through Emby Connect as it defeats the point of a reverse proxy as a security measure to prevent things like a DDOS attack.

Edited April 9, 2020 by andyrsand

[Luke 42086]

We can always add an option to not report it.

[DePiglio 0]

I think that would be an excellent option for those who are using a reverse proxy.

 

Beyond that, do you have any idea why Emby is choosing to connect through the LAN IP rather then the remote IP? It seems like it might be an issue with Emby Connect itself.

[Luke 42086]

I think that would be an excellent option for those who are using a reverse proxy.

 

Beyond that, do you have any idea why Emby is choosing to connect through the LAN IP rather then the remote IP? It seems like it might be an issue with Emby Connect itself.

 

The apps always try the lan ip first as an optimization for when you are inside your local network.