I recently ported my plex server over to a vm. canyouseeme.org shows port 32400 as open, jumbo frames are disabled. I can also access the server from outside its network via my global ip or my domain name. Retrying the connection ends with it being fully accessible and then switches to not being accessible after a second or to. I’m also seeing “PubSub: Received notifyConnectivity event with incorrect async identifier” in the logs.
Linux lin-virt06 4.15.6-1-ARCH #1 SMP PREEMPT Sun Feb 25 12:53:23 UTC 2018 x86_64 GNU/Linux
Version 1.12.0.4829
I had it working for roughly a day before it disconnected with this error.
I have a similar problem running on native Debian. Everything worked fine until the mid-February update. Now remote access is broken. No changes anywhere except install the new distribution. Now remote access lights up green for a second or two and then says it is not available outside of the local network. Any hints on where to look?
I’ve seen some other forum posts about it and haven’t found anything other then “I restarted the service a few times and it fixed itself”, and the few things I mentioned above. It looks like its not a “just me” thing so I’m hoping a plex staff member can weigh in on it.
I’ve downgraded to plexmediaserver_1.7.5.4035-313f93718_amd64.deb and remote works fine now. This is not the first time Plex has blown up remote access… I now am saving distributions until I have a newer one that works. I have not found an archive of older versions of Plex to get a more recent, working version.
Over the past two days mine has flipped its status a couple of times, also just today it is asking me to claim my server again? When I click claim server it spins for a second and then does nothing, refreshing the page it seems to have fixed itself. I did get a comment from a plex member on another post that I mentioned this issue. There response was
"There is a timing issue that results in the async identifier issue where messages are received out of sequence and may give rise to the wrong status indication being set on the remote access sett8ngs page
Avoiding quick and repeated clicks on retry would reduce the chances of getting the problem"
Going to monitor it for a couple more days to see if the issue continues.
