sorry…it was just to bring more attention to the problem… more people complaing means that something is wrong with pms server… maybe the plex staff take a look at that if this happening to more people…
@PLEXHOME01 said:
sorry…it was just to bring more attention to the problem… more people complaing means that something is wrong with pms server… maybe the plex staff take a look at that if this happening to more people…
May be - but what you are doing is wrong. Plex Media Server was not intended to be a solution for someone who has 160 shares - what you are doing probably violates the terms of use of the product. It may have worked before
You should sit back - keep a low profile and wait for the final outcome of the investigation
@PLEXHOME01 Still not clear what is causing some of the failures. Whilst timeouts on the repeated back-to-back requests for the large list of access tokens for the 160 shares could be understood, there are some timeouts on simple short requests as well
and the logs show some logged messages like this
Aug 17, 2015 18:54:07:011 [4664] ERROR - MyPlex: Couldn't get list of access tokens from myPlex.
Aug 17, 2015 18:54:07:011 [4664] DEBUG - EventSource: Failure in IdleTimeout (0 - A operação foi concluída com êxito).
Aug 17, 2015 18:54:07:011 [4664] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Aug 17, 2015 18:54:07:011 [4664] ERROR - EventSource: Retrying in 15 seconds.
Aug 17, 2015 18:54:07:011 [4664] DEBUG - EventSource: Got event [data] '<Message command="notifySharingChange"/>'
Could you also now enable Verbose logging to supplement the Debug Logging on the server to see if we get more infromation
So Media Manager / Settings / Server / General / Show Advanced and have both Debug and Verbose enabled.
Save changes
Restart the server and start to use it as normal - i believe if you have a Plex Web window open on the remote access screen it will regularly check for status and connectivity so do that.
when the next disconnection arises, note down the time and the symptom. and collect the logs and any screenshots and zip and attach here
Thanks
@PLEXHOME01 - also check that your router has logging enabled, And when you get the disconnection - save the router log as it may have some information if there were internet connection issues at the time
Updated to new pms and its been logged in since then… Until now no more logging off remote acess… But i will do what you said and if it loggs Out again i tell you the time and i put the log here… Thank you so much for your atention and your interest in helping me… And sorry for some behavior on fórum… But im new in this fórum rules… Thank you once more…
In the router i already had done that… And at the last logging Out yesterday i went to router log and at the time at the log Out Nothing was was wrong… On the same time of the log Out no information on router… On router only the normal loggs… So i think it was not My router…
first loggout today with new pms …here is the log… i think i was betwen 14.oopm and 14.50. here is the router log too…
sorry but that log is not the real one… when upadted to new vrsion it unticked the log option… i wil wait for another logg of remote acess to provide the log resultes… but the router log is the right one… sorry…
Ok - I am out all day so won’t look at logs till later this evening - Please maje You restarted srever with Loggjng on ad i also want You to capture loga For after restart and before disconnection
ok… done that . log after restart… and before desconnection… one question… this could be happening because some of my shares add the v4.0 and others the old one 3.5.3? could that create same kind of conflict?
@PLEXHOME01 said:
ok… done that . log after restart… and before desconnection… one question… this could be happening because some of my shares add the v4.0 and others the old one 3.5.3? could that create same kind of conflict?
Your client app versions should not matter but if for example you set secure connections on the server to required rather than preferred or disabled then plex 3.5.3 clients will not be able to connect
In your last logs what time was the disconnection and when was it working and dd you take any specific action or logs taken of the problem without you making changes to get it to work
And what was the symptom that made you decide it was disconnected
I reallised when i was testing on My iPhone at 14.45pm… Then i went home… Open My pms server and remote access was turned off… Then i manually start de remote access… I did nothing… It was working ok from the last update that i did yesterday around 3.00am… When it logged of i called to My isp provider and asked to put My router on factory settings… Now im waiting… Its logged on from the 15.10pm… 6 or 7 shared users watching… And everything looks ok… The only problem its this randoms logging outs… Never had this problem before…
Maybe this will resolve My random loggout remote access…“We will be performing scheduled maintenance starting 23:59 PDT on August 19 (06:59 GMT, August 20). It should last around 30 minutes, during which the https://plex.tv/ website and login services will be unavailable.”… Lets hope so…
I was searching more information here in the forums and seems that this is not a new problem… “mtsdawsonmtsdawson”
August 14
This issue was introduced in .5 and persists in .8… I confirmed by downgrading to .4… which was stable for over 7 days. However, the new iOS app requires the newer builds so I had to upgrade back to .8… and voila, I’m getting this same issue again. Frustrating as now I HAVE to be home to access my server just to tap the “Retry” button to fix remote connectivity. This is painful, especially considering I’m a Lifetime PlexPass and never been forced to upgrade to a broken version. Are we planning a fix? Plex is worthless if it can’t retain remote connectivity.
This user has the same problem as me… This makes me feel that nothing to do with configurations… Because i only update pms to the latest… And i was using one before the ones that this user said that had the same problem… Hope the devs already have a solution for this…
I am aware of those but until we see logs and compare they have to be treated as separate issues
desconnection happened again at 19.10… everything normal just desconnected the remote access…here the pms server logs and router logs…
now here his the log after i press the reconnect buton on remot access and stays acessible…
@PLEXHOME01 - have been looking at the logs and the disconnection that you reported at 19:10
This appears to be what made Plex Media Server show the connection as lost:
Aug 19, 2015 19:07:45:136 [5064] DEBUG - EventSource: Got event [data] '<Message address="94.61.40.254" port="32400" connectivity="0" command="notifyConnectivity"/>'
Aug 19, 2015 19:07:45:136 [5064] DEBUG - PubSub: Got notified of reachability: 0
There are connectivity tests both ways. The Plex Media Server does regular checks to see if it can reach plex.tv and similarly plex.tv tries to connect to the Plex Media Server through your public IP and Public Port. When this test from plex.tv fails to get a connection through your public IP and port, it reports to the Plex Media Server that reachibility has gone - as above
There may be issues in how that failure is handled afterwards and recovery. The cause of initial failure - reported as 19:07:45 is not known. All we know is that plex.tv tried to connect to your server and it could not.
I am thinking at next failure you could also get netstat output to see how many network connections there are active
So Start / Run/ and type in cmd and cmd.exe appears right click on it and select Run As Administrator
In the command line window type in command
netstat -a -b > %localappdata%
etstat_20150820a.txt
Attach the file %localappdata% etstat_20150820a.txt with your logs
The netstat need to be done when the failure occured - after before recovering or restarting
you could also assess how much syncing users are doing by looking at the xml from
plex.tv/servers/bad34591faef8a01fb210d75523b54e03e490575/sync_lists
all my shares the sync option is disable… here is the nesat log but with everything ok… see if you see anything wrong… when it logs down i send you another…
another logout…here is the logs…log out about between 14.10 and 14.20…
