There seems to be a bug (maybe related to Windows 10?), that the app from the store doesnt find a server I have shared access to after some (random) time, mostly when the server changes it’s dynamic IP. Clicking the refresh button doesnt help at all, but a workaround always does:
If I go under settings => account and do a sign out and log in again, the server will be there. So this is a bug.
That’s very strange. Is the client losing the server entirely, or just considering it to be unavailable?
Signing out and in is basically a refresh on the server info. You can achieve the same thing by going to the Servers page from the app bar and testing the server.
It sounds like the client is pinging the server periodically to test availability and those tests are failing, so the client is declaring the server unavailable. The usual cause of this kind of thing is a network problem of some sort, obviously. But you can look in the logs to be sure.
Sorry for the late reply, still having the issue, on three different PCs, also friends having shared libraries the same issue. It is like I said it is.
It seems to work until a random time, mostly when the server changes IPs, then the clients, just the Windows 8/10 app, doesnt work anymore, shows the shared server as offline. When I go to settings logout, and login again, it finds the server, and works.
Clicking refresh doesnt work. I need to logout, login (in the app), then it finds the server.
App version is 2.1.0.6, it worked before for over 1,5 years, but since going to Windows 10 it doesnt anymore, it since one of the last app updates, cant say which triggered it.
It is a shared library btw to a internet shared server, not a local server.
Server is also newest version, linux.
Just tested it again, opened the plex app on my laptop => server offline. Went to settings logout, logged in again, aaand app found the server ( before refresh did nothing / stayed offline). Now I can watch/browse through the server.
Now opened the app on my tablet, offline… did the same procedure, server goes online / is found.
It will mostly work now for 24h, then tomorrow, broken again.
“It sounds like the client is pinging the server periodically to test availability and those tests are failing” this sounds to me you / devs, changed something in the client which broke it (on some networks / scenarios), because it always worked over the last years perfectly, and just started to be broken recently.
If we are talking about server changing its public IP address then it could take up to 1 hour for the Plex Media Server to detect that change and that would then be fed to plex.tv and the clients need to have code that re checks with plex.tv if the connection fails
A recent change to plex media server (0.9.12.5) should result in the server detecting the change sooner but if it detects an external network connection failure on its periodic checks on pubsub.plex.tv and then resumption of internet connectivity
So one needs to establish if the client app does re fetch the server details from plex.tv on losing the connection
I don’t think we changed anything in the client around this. I suspect sa2000 is on the money here.
To establish what is happening - it would need Debug Plex Media Server.log from the remote shared server covering the period of the Public IP Address change and debug logging you can get from the Plex for Windows 8.1 client as well as the xml from https://plex.tv/pms/resources.xml?includeHttps=1 for the account used on the Plex for Windows 8.1 machine
We are not talking about a sever issue here… It’s obsolete if the IP changes and the server doesn’t notice it “fast enough”. The problem ONLY happens with the Windows app. Ive tested it on my android phone and the app has no problem at all finding the server, after it had an IP change. Also I checked the connection logs and IP change didnt happen in the last days.
It is only the Windows 8/10 app which doesnt find the server, but like I said… if I clear the login data in the app and re-etner them, it find it… it is clearly a bug with the Windows app.
heres windpws app client log…
heres log again, after done a log out and login again, and server been found… (which obviously didnt change anything on the server… so it’s a problem with your client app)
A Public IP Address has changed
So we start the Plex for Windows App and tries to connect to server on 93.222.190.120:32400 through SSL
It fails
2015-08-08 13:46:07:2147 [5] WARNING - [PlexClient] - PlexException requesting container from https://93-222-190-120.f62c685fd84543d29cd10b26fa0f4ccf.plex.direct:32400/?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx: Timeout connecting to server
Then you force a fresh sign in to plex.tv account within the Plex for Windows 8 App
2015-08-08 13:51:53:4953 [3] DEBUG - [PlexHttpClient] - POST https://plex.tv:443/users/sign_in.xml
And as a result it asks plex.tv for all server connection details
2015-08-08 13:51:55:9540 [3] DEBUG - [PlexHttpClient] - GET https://plex.tv:443/pms/resources.xml?includeHttps=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
So it receives the updated Public IP Address and the Plex app successfully connects to the server
2015-08-08 13:51:57:5020 [30] DEBUG - [PlexHttpClient] - Received OK from https://93-222-155-155.f62c685fd84543d29cd10b26fa0f4ccf.plex.direct:32400/?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
So I believe the issue is that clients (in this case it is Plex for Windows 8.1) are not asking plex.tv for latest connection infomation for servers after getting a failure. It is my belief they should all do
So it is a bug in the Windows app like I said from the beginning… do something about it please.
Will have to wait for @mfeingol to have a look
I would like to chime in here also. I have recently gone to Windows 10 and that is when the problem started. Running Plex Media Server off an i7 machine over a gigabit network. All IPs are static in my home for devices. So the IP isn’t changing but at random intervals I will get a message pop on my Shield TV Plex app saying the connection to the server was lost. I have two options, Cancel or Retry. I hit Retry and playback resumes almost right away.
Now looking at my logs and I can see a few lines about dropping the connection.
Aug 09, 2015 23:13:55:110 [7308] DEBUG - Completed: [192.168.1.9:56960] GET /library/onDeck?type=2&viewOffset=0 (5 live) TLS GZIP 28ms 2118 bytes 200 (pipelined: 3) Aug 09, 2015 23:13:57:060 [7300] VERBOSE - We didn't receive any data from 192.168.1.9:50055 in time, dropping connection. Aug 09, 2015 23:14:04:183 [7308] VERBOSE - We didn't receive any data from 192.168.1.9:50762 in time, dropping connection. Aug 09, 2015 23:14:08:787 [7308] VERBOSE - We didn't receive any data from 192.168.1.9:35127 in time, dropping connection. Aug 09, 2015 23:14:15:111 [7308] VERBOSE - We didn't receive any data from 192.168.1.9:56960 in time, dropping connection.
On my iPad a similar thing occurs except instead of asking to retry the stream seems to pick up again after a few seconds.
So for me the issue lies in either the server not keeping the connection between player and server active or Windows 10 cutting in and preventing the server from polling to check if the connection is still active.
I’m currently rolling one machine back to Win 8.1 to confirm that is still good.
A friend of mine says he has the same issue and he has Windows 8. It more looks like a problem on the web-servers of plex itself. The real IP is send to the plex servers and storied there, shared people will have those information stroed too when they log in with their account, but it seems the information isnt updated to them somehow, and just when they re-login.
@mkdr said:
A friend of mine says he has the same issue and he has Windows 8. It more looks like a problem on the web-servers of plex itself. The real IP is send to the plex servers and storied there, shared people will have those information stroed too when they log in with their account, but it seems the information isnt updated to them somehow, and just when they re-login.
Info is not force fed to the plex clients. It is force fed to plex.tv and it is up to the clients to ask for the information. The issue i raised - to be adopted for all clients - is that if there are difficulties in connecting to the server using the info obtained previously form plex.tv, they should ask again - would need to have some built-in delays between requests.
Please re-read what I said, you totally got me wrong. It is like I said. I didnt say anything about clients I was talking about the web servers behind it storing all the share information. Still a bug though. And no answer yet from the devs on here.
@mkdr said:
A friend of mine says he has the same issue and he has Windows 8. It more looks like a problem on the web-servers of plex itself. The real IP is send to the plex servers and storied there, shared people will have those information stroed too when they log in with their account, but it seems the information isnt updated to them somehow, and just when they re-login.
@mkdr said:
Please re-read what I said, you totally got me wrong. It is like I said. I didnt say anything about clients I was talking about the web servers behind it storing all the share information. Still a bug though. And no answer yet from the devs on here.
I will try and understand
a problem on the web-servers of plex itself. - This I believe you mean plex.tv
The real IP is sent to the plex servers and storied there, Agreed - it is sent to plex.tv and stored on the account information on plex.tv for the PMS owner.
shared people will have those information stroed too when they log in with their account
The updated server information should also be stored (or linked) in the account held information on plex.tv for the shared users.
but it seems the information isnt updated to them somehow, and just when they re-login. I would like to see evidence of that if possible. It could be just the client used by the shared user having old cached information) or it could be that the account on plex.tv is not holding the updated information
To prove which it is, one would need to look at the xml from
plex.tv/pms/resources.xml?includeHttps=1
obtained for both plex.tv accounts - yours and your shared user
What is that link for? It doesnt contain any Windows client apps at all. If or if not re-logged in. It just shows the server and an android device. So I guess it just shows DLNA players/servers (resources) and not clients at all.
@mkdr said:
What is that link for?
It is for clients: Plex for iOS, Plex for Android, Plex Web App, Plex Home Theater etc to use to find out the connection route to use to get to owned or shared servers
One would need to be signed in to the appropriate plex.tv account before. If not signed in then cached info would be used
Like I said, it doesnt contain any Windows app/client at all. Devices count = 2, server and one android device.
