long time to login, then have to select user after failure

[justinrh 267]

Running Android TV app on two Shields.  After re-configuring my network with a new IP address range and Wi-Fi SSIDs, I'm having a problem with only one of my Shields.  I've never seen this behavior, and the Emby home screen normally takes <1s to display.

I sent an app log @ 4:22 PM CT from the select user screen; attached is the server log right after that.

I launch ATV
the Emby logo screen shows with a spinner for maybe 30s
then I get the user select screen and a toast saying 'unable to connect to configured server', yet it is connected to the server
the only user is shown ready for me to select (it has a padlock on it)
I select the user and I am logged in at the home screen

What is the problem finding the server?  How can I fix it?

I've tried logout/login and manually defining the server again, but no change.

embyserver.txt

[seanbuff 1358]

55 minutes ago, justinrh said:

After re-configuring my network with a new IP address range

Have you tried adding this new range to the 'LAN Networks' section of the Emby 'Network' page?

[Luke 42255]

How have you configured server network settings?

[ebr 16346]

Hi.  Once logged in, try going to the app startup setting and changing it, then change it back.  I'm not sure what is goofing up but that process should re-save the server address.

[rbjtech 5345]

Looking at the the logs - I see a lot of http://168.1.162:8096 - which is obviously an illegal IP address ... should it maybe be 192.168.1.162 ?

App: Udp message sent to [::ffff:168.1.167]:48598

This is a broadcast to 'find' the server - but it's not going to respond with that IP ?

Edited May 28, 2024 by rbjtech

[ebr 16346]

12 minutes ago, rbjtech said:

but it's not going to respond with that IP

Unless someone actually typed that value into the network settings...

[justinrh 267]

19 hours ago, seanbuff said:

Have you tried adding this new range to the 'LAN Networks' section of the Emby 'Network' page?

Yes.

[justinrh 267]

18 hours ago, Luke said:

How have you configured server network settings?

Can you be more specific?

[justinrh 267]

7 hours ago, rbjtech said:

Looking at the the logs - I see a lot of http://168.1.162:8096 - which is obviously an illegal IP address ... should it maybe be 192.168.1.162 ?

App: Udp message sent to [::ffff:168.1.167]:48598

This is a broadcast to 'find' the server - but it's not going to respond with that IP ?

That was my mistake in editing the log file 

[justinrh 267]

Keep in mind that both Shields use the same SSID and user, but only one is having an issue.

[justinrh 267]

Today, Emby would open to the user select page in just a few seconds, but still not the correct experience.

I logged out, logged in, still no change.  Then, I checked the log in settings and it was set to 'user login screen' (or something like that).  I selected 'login as last user' and now it works correctly.  Thanks, ebr.

Right after I changed the network, I had to supply the user's PIN the first time and thought that was the end of it, but something go messed up somewhere.

Really, I guess the answer was staring me in the face, but I don't know if I've ever seen that user select screen before (or else I've totally forgotten about it).

Edited May 28, 2024 by justinrh

[Luke 42255]

5 hours ago, justinrh said:

Can you be more specific?

The entire Network screen. Have you customized any options?

[justinrh 267]

The only non-default value thing pertinent on that screen is "LAN networks", and I updated it.

[Luke 42255]

3 hours ago, justinrh said:

The only non-default value thing pertinent on that screen is "LAN networks", and I updated it.

Hi, what did you update it to, and what happened after that? Are you sure you actually need to customize this option? The vast majority of users do not.

[justinrh 267]

I updated to match the network, so that my clients could connect.  I may not need it now; I set it a long time ago and I don't remember why (because of remote access issues?).

Either way, that setting was not my trouble with the Shield.