Issues with Emby server with two network cards since 4.5.2.x

[jacotec 7]

Hi,

I'm noticing that my ShieldTV has serious issues connecting to my Emby server. After starting the app it's "Loading" for more than a minute, mentioning "Volley timeouts" and then presenting the server lookup screen where choosing my discovered "mediaserver" does not work.

I'm manually entering my "official" access via my proxy server, https://media.mydomain.com and everything works.

Unfortunately the app does not recognize this server address (although I've set to login with the same user at each start) --> this is obviously a bug in the Android app. So, at the next start, the whole game starts from scratch.

I tracked the discovery issue down to this behavior:

My Emby server is connected to two networks: 10.0.6.3/12 and 10.32.6.3/16. The 10.32.x.x is a fully priorized VLAN for internal media clients, the 10.0.x.x is the standard network including the gateway and the proxy connection, mostly used for external access. Emby broadcasts the 10.0.6.3 internally, the Shield on 10.32.6.17 picks that up, sends the request via the router to 10.0.6.3 and the Emby server of course answers directly via the 10.32.x.x network. That's why this does not work.

I've changed the announcement to 10.32.6.3 in the server setting, now my Shield works perfectly but any other client in the 10.0.x.x network now has the discovery issue.

How can I solve this? It would be perfect if the discovery would announce my official proxy URL to the clients which works from everywhere. But the field only allows an IP, not an URL.

Second, it'll be good if a client would save the connection (URL) together with the user credentials it the "login always as this user" is selected. It tries to log in with that user at start, but unfortunately it does not use the URL it used for the connection, instead it seems to rely only on the discovery which does not work.

It's strange that this worked from all networks before 4.5.2.x, did something change?

Edited October 14, 2020 by jacotec

[Luke 42092]

Hi there, does your Emby Server dashboard display your correct local and remote addresses?

[Carlo 4561]

@jacotec 

Hi. You have overlapping network segments which need to be resolved.  That will surely cause you issues like this.

[jacotec 7]

23 hours ago, Luke said:

Hi there, does your Emby Server dashboard display your correct local and remote addresses?

Yes, it did display the 10.0.6.3 as internal address, after I forced this to 10.32.6.3 in the config it's displaying that. But both does not respect that the main connectivity should be done to my proxy with the URL "https://media.mydomain.de" ... so whatever LAN address is displayed, there will always be one of my two networks where this does not work.

22 hours ago, cayars said:

@jacotec 

Hi. You have overlapping network segments which need to be resolved.  That will surely cause you issues like this.

10.0.0.0/12 and 10.32.0.0/16 are absolutely not overlapping! These are two fully independent subnets.

Edited October 15, 2020 by jacotec

[Carlo 4561]

Wow, I looked at those numbers differently.  Sorry about that, yes completely different ranges.

Do you have routing setup between those LAN groups?  Can you ping the Emby Server from the other subnet?