yaksplat 58 Posted July 17, 2020 Author Share Posted July 17, 2020 The only thing that i can think of is that the server name isn't resolving. But then after a timeout, it should go to the settings screen to allow for a change. But the app isn't programmed to do that, or it's failing. Link to comment Share on other sites More sharing options...
Carlo 4332 Posted July 17, 2020 Share Posted July 17, 2020 Have you tried removing the network to see what happens on that screen? Link to comment Share on other sites More sharing options...
yaksplat 58 Posted July 17, 2020 Author Share Posted July 17, 2020 When you remove the network, the screen goes black. Factory resetting now. Link to comment Share on other sites More sharing options...
yaksplat 58 Posted July 17, 2020 Author Share Posted July 17, 2020 Okay, more weirdness: Full factory reset on a FireTV. Installed the App from scratch and i start it up and i get..... The same exact screen on the first post. Never entered any address. Checked the logs and i see this, and only this to the IP of the FireTV Line 22669: 2020-07-17 16:11:18.544 Info App: Udp message sent to 192.168.1.189:39087 Line 22670: 2020-07-17 16:11:18.547 Info App: Udp message sent to 192.168.1.189:39087 Line 22672: 2020-07-17 16:11:19.686 Info HttpServer: HTTP Response 200 to 192.168.1.189. Time: 1ms. http://192.168.1.151:8096/emby/system/info/public?format=json So a 200, but still nothing. I reboot emby server and everything works again. All of the FireTvs/FireSticks are operational. I honestly don't know what was wrong there. But it all started with a second server. All other clients could jump back and forth between servers with no issues. Link to comment Share on other sites More sharing options...
ebr 14963 Posted July 17, 2020 Share Posted July 17, 2020 34 minutes ago, yaksplat said: I reboot emby server and everything works again. All of the FireTvs/FireSticks are operational. I honestly don't know what was wrong there. My guess is the same as it originally was - the IP address being reported to the app was incorrect and re-booting the server caused it to re-query and fix itself. I'll have to look into making the app handle this situation better. It should not have been trying to auto-connect to your server. 1 Link to comment Share on other sites More sharing options...
Carlo 4332 Posted July 17, 2020 Share Posted July 17, 2020 That's certainly what it sounds like and what the indications were. Link to comment Share on other sites More sharing options...
yaksplat 58 Posted July 17, 2020 Author Share Posted July 17, 2020 54 minutes ago, ebr said: My guess is the same as it originally was - the IP address being reported to the app was incorrect and re-booting the server caused it to re-query and fix itself. I'll have to look into making the app handle this situation better. It should not have been trying to auto-connect to your server. But how would that happen with a static IP? No changes since last year. Link to comment Share on other sites More sharing options...
ebr 14963 Posted July 18, 2020 Share Posted July 18, 2020 18 hours ago, yaksplat said: But how would that happen with a static IP? No changes since last year. We cannot be sure exactly what happened but there is the IP address and then there is what Emby knows (or thinks it knows) is the IP address. All the symptoms you described pointed to Emby thinking the IP address was something other than it really was. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now