Android App - local server auto detect not wanting to connect

[ErikRedbeard 0]

If I open the android app and then try to connect directly to the auto detected server it fails with "Connection Failure - We're unable to connect to the selected server right now. Please ensure it is running and try again.".
But if I go via Add Server" and enter the IP of the emby server (192.168.1.4) and leave port default it just connects without issues.
And from that point the auto detected one works too (seems like the Add Server replaced the auto detected one though).

Here's a screenshot of the IP on the emby server

I'm confused on why the one auto detected (which has the correct display name) doesn't work until I Add the Server manually (which seems to replace the auto found one, and not actually add one).
Would be nice for the autofind to just work for the ones in the household that aren't that tech savvy.

Does the auto detected one not connect via IP on local or?
Or am I doing something wrong somewhere?

[Luke 37064]

Hi there, can you please provide the android app log from when this happens?

Thanks.

[ErikRedbeard 0]

Both logs are fresh made after clearing the emby app data so I could reproduce on a blank slate.
The bigger log is made while it gives the error.
a03c960c-3797-4996-851f-cf37a1796a8b.log
The smaller log is made after already closing the app again.
c57302f3-f69c-4e69-92e3-7322c98bad7f 1.log

 

I also forgot some extra information in the main post. So I'll add it here (was really late already). 
 

Emby is running in a bridged docker that gets a 172.17.0.8 address.
These are then linked to the host ip 192.168.1.4.

The logs are made with the below settings applied.


From what I can gather it seems the "Local IP address" option isn't completely overriding the local IP address that the Emby tells the clients.
As I've said if I manually add the 192 address as a server it works fine from that point.

I can work around this issue if it doesn't end up fixable by assigning the docker it's own IP or something along those lines.
But I'm confused on why the "Local IP address" option seems to not work properly for the Android App.

Now that I tried some of the other apps.
The Microsoft Store app version also has this same problem with the auto detect.
However the Windows Installer version works out of the box this way with the auto detect.

Edited January 21, 2021 by ErikRedbeard

[Luke 37064]

Hi @ErikRedbeard thanks for reporting. This will be resolved for the next release of the server.