Server Version#: 1.14.0.5465
Player Version#: 3.69.1
Why is remote access broken, YET AGAIN ?
Was working fine, updated, now not working.
Restarted Plex, Restarted Server, Rebooted router. Still " Not available outside your network
Your server is signed in to Plex, but is not reachable from outside your network."
Getting fed up with this breaking after nearly every other update.
Same issue here.
I have the same issue…I just updated plex to 1.14.0.5465 and now I cant get remote access to work? I’ve used plex for years and never have had this issue… is there a way to roll back the plex media server to the older version .
Try reverting to the public release channel if you aren’t happy with the beta.
I’ve never had a problem before where I couldn’t connect to remote from any release. How can I roll back the update?
MacOS: High Sierra
PMS: Version 1.14.0.5465
Hi guys… it seems that I am not the only one with this Remote Access problem… 
For years, I’m using the ‘Manually specify public port’ without any trouble.
After a last ‘High Sierra’ update and a reboot, my remote access change randomly from ‘Fully accessible outside your network’ to ‘No remote access’
I activated the ‘Media Server verbose logging’ and the only error looping is:
Nov 13, 2018 07:56:57.127 [0x700000ee8000] ERROR - Error issuing curl_easy_perform(handle): 28
The only working solution I found so far is… disabling the Remote Access… 
Any other idea ?
Working just fine here.
Lucky you… it is totally random on my server… it can stay ‘Fully accessible outside your Network’ for a few hours… and change suddenly…
The main problem is, when it is in ‘No remote access’ state, I cannot access my server from inside my house anymore… that’s really annoying…
Now I disabled the remote access, I can use my other players inside my house… but not from outside anymore…
I also checked my Port Forwarding with ‘http://canyouseeme.org/’ and it is always ‘success’
As this glitch appeared right after the last ‘High Sierra’ security update, I wonder if there is a link with it…
I would say that if you can’t access your server from within your local network when it’s not connecting externally, then I think you are not connecting on your local network properly. It’s as if you are going out through your internet connection to come back in to connect to your server, and conversely the streaming is going the other way. You should be able to access your server on a local network without remote access being needed
Good point…
Without remote access enabled, I can read any movies in Direct Play from inside my house…
I’m going to check it I still can when I enable the remote access again…
But as I never had any problem before my MacOS upgrade, I still have a doubt… maybe a change with the network card ?!
But you’re right, remote access or not, I should be able to access my own server with any player located on the same LAN
My PMS is running on a dedicated CentOS 6.10 box. So I doubt it has anything directly involved with the macOS updates. It is definitely a Plex issue, as I have had this happen before, no response from Plex, then miraculously working with the next update!
It was working fine before the update as my nephew was watching a film at his house from my PMS, so I waited until he had gone to bed before I ran the update, to then see the “Not available…” message.
Thanks for the info, I got exactly the same problem then…
Wait and see then…
Would like to have a look at server logs when remote access fails or local access not working.
Please ensure debug logging is enabled - see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
Restart the server to make sure new log files get created and we capture the launch sequence
When the issue arises, note down the time and capture the logs and upload here with the details
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Good idea, I’ll do it ASAP, but I’m working right now, you know, Europe… 
This morning, I changed the DNS on my server… I was using Google DNS and instead, I set again the default DNS sent by DHCP from my ISP router… actually 192.168.1.1, like the gateway… I imagine that internally, my ISP uses its own DNS… and I was not able to reproduce the error anymore… I also tested my iPhone and iPad from my work wifi and everything is fine… so far… fingers crossed
Bump… it did not work very long… suddenly, no more access to my Plex server… from my LAN or from Outside…
Nothing clear in the logs for me… 
I disabled the Remote Access and my players are fine again on my LAN
Nov 13, 2018 14:25:16.200 [0x7000006b8000] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (4324f6a1-7518-4188-8d9c-20ad83fcea2e, expected 2706486a-59cf-49e5-a9ff-36f06d7e61e4)
Nov 13, 2018 14:25:16.416 [0x700002672000] WARN - WebSocket: Request doesn’t look like upgrade request (websocket, Keep-Alive)
Nov 13, 2018 14:25:16.416 [0x700002672000] WARN - Caught a system exception setting up WebSocket, ignoring.
Nov 13, 2018 14:29:07.854 [0x70000073b000] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (2706486a-59cf-49e5-a9ff-36f06d7e61e4, expected 6af08c8b-8d3e-4415-9154-b99b1a66cb2c)
Plex Media Server Logs_2018-11-13_14-31-15.zip (2.2 MB)
Nov 13, 2018 14:29:07.830 [0x70000073b000] ERROR - EventSource: Retrying in 15 seconds.
Nov 13, 2018 14:29:07.854 [0x70000073b000] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (2706486a-59cf-49e5-a9ff-36f06d7e61e4, expected 6af08c8b-8d3e-4415-9154-b99b1a66cb2c)
Nov 13, 2018 14:29:08.282 [0x700002672000] WARN - WebSocket: Request doesn’t look like upgrade request (websocket, Keep-Alive)
Nov 13, 2018 14:29:08.283 [0x700002672000] WARN - Caught a system exception setting up WebSocket, ignoring.
Nov 13, 2018 14:29:08.580 [0x700001e42000] INFO - AutoUpdate: no updates available
Nov 13, 2018 14:29:10.517 [0x7000003a6000] WARN - WebSocket: Request doesn’t look like upgrade request (websocket, Keep-Alive)
Nov 13, 2018 14:29:10.517 [0x7000003a6000] WARN - Caught a system exception setting up WebSocket, ignoring.
You use to be able to enable remote access using UPnP and not having to manually assign a port?
Nope, I always used the manually assigned 32400 port for several years without any problem… My ISP Router doesn’t accept Plex as a UPnP client…
Have spent the last hour trying to work out what has happened then i come accross this post, quite frankly i have just about had enough of this application now, as stated above every other release seems broken and its so unstable and unreliable
im getting outside port check confirming 32400 is open
tried it using UPnP and also manually assigned
it fails either way, reboot the server i gain access to config again for a short period of time
Ya it should work UPnP, which it doesn’t now.
