Server Version#: 1.40.5.8921
Player Version#:
I’ve used remote access for years. Recently, I started receiving a " Not available outside your network" error. If I click Retry, it comes up as “Fully accessible outside your network” for 10-15 seconds.
Plex Media Server Logs_2024-09-03_14-05-45.zip (3.8 MB)
These are the logs.
The remote access test always is green to start with. After the test, which takes some seconds, it updates the indicator.
If it starts green and turns red, that does not mean that it was working for a few seconds and then stopped. It means it was never working.
I would ignore the built in test and use something like this.
The result I got was:
Success: I can see your service on X.X.X.X on port (32400 )
Your ISP is not blocking port 32400
Well, that is a good start. If remote access is still not working, then something else is going on.
Personally I always specify the IP address and port even though you shouldn’t have to if you aren’t doing something special. 
I use my plex server remotely on a regular. I’ve never had to specify the ip of the server on my roku (using the plex app) or anything like that.
Do Team Members monitor this board?
I can connect to the server remotely via external IP.
When I try to connect from plex.tv I get the following message: “app.plex.tv is unable to connect to “” securely”.
I would really like to get this resolved.
Hi AAron have you sorted this situation out im in that same drama and im not too tech
savy i clicked on what needs to be done following what i can do and im still having server drama is there like a server update where it can search through the settings correcting this drama dont know what to do from here on and people are waiting to watch my Plex
Looking at the logs, the server might be unable to acquire a valid certificate and has been rate limited.
Sep 03, 2024 14:03:44.278 [9060] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429
error code=“1003” message=“API rate limit exceeded” status=“429”/>
Plex Employee to Reset Server Certificate? “API rate limit exceeded” error
I was out and about , cruising and looking for trouble 
Who’s in trouble? ( I don’t see any hung certificates at Plex.tv )
Same problem not fully access outside the network
Thanks for the replies, everyone. I’ve been busy this weekend and haven’t been able to try anything.
I’ll post after I tinker with the certificates.
This really needs to be changed so it reflects it on the UI. It seems like a non-issue, but the number of posts I’ve seen over the years confused about remote access working for a few seconds and then turning off is crazy.
3 Likes
Yep, I complain about it constantly. It’s not the best thing in Plex.
exactly what im getting this has only started to happen surley this has to be last update issues
+1 for another user recently getting this issue of not being able to do remote access, following all the troubleshooting steps and still being told that app.plex.tv cannot connect securely. I posted my logs on this article
How about a write up on how we can fix this ourselves or else a team member jumping in and at least telling us they acknowledge the issue and are working on it!
Did you already have a look at the related troubleshooting support article?
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
There’s also a guide with some more details on how to troubleshoot remote access issues.
Tom,
As I posted in my linked support request, yes. I followed the troubleshooting steps in the article you provided a link to. I verified that my remote port is visible and that port forwarding is working (which it was before the update broke my server). I verified that it is not a Double NAT problem. I verified that port forwarding is working as expected. I tried changing my router configuration to UPnP, back to manual, and back to UPnP
I uploaded my logs but my Plex-specific knowledge is limited when it comes to log interpretation. There are lots of logs in that package. I tried putting them through an indexer and searching for anything vaguely related to remote access still yielded nothing other than there appeared to be several crashes in the time period where I was trying to get it to work. Perhaps that lends a clue?
Like others in this thread, I am a long time user of Plex with Remote Access that has worked perfectly until recently. Now, not only does remote not work through app.Plex.tv, but my local players also cannot see my server as advertised by the Plex brokering service. Methinks something is broken.
I have the similar problem. I have tried manually setting 32400 in the plex, also tried automatic. No luck.
I have a Tp-link modem > pfsense > windows11 pc (10.0.0.6).
Altough I have opened port in the modem settings and pfsense settings. Still “not available outside my network”
Initially I was planning on installing the plex in Unraid docker, but since I failed the remote access, then i installed on a win11 pc.
Plex Media Server Logs_2024-09-20_14-08-28.zip (91.7 KB)
Can anyone check my logs and see what is the reason of this issue.
@ChuckPa can you help here at all? We have several folks who recently had their servers switch from working fully to no longer being accessible both locally and remotely. Looking through my logs, I am seeing a lot of errors in my System log saying:
- CRITICAL (runtime:709) - Private handlers are no longer supported; couldn’t register <bound method StreamService.token_handler of <StreamService object at 0x0000000004772690>>
- CRITICAL (core:574) - Exception in thread named ‘refresh_servers’
- CRITICAL (core:574) - Exception getting hosted resource hashes (most recent call last)
I don’t know a lot about the internal workings of the Plex code but these generally strike me as unhealthy and potentially related to why I can’t reach my server anymore. Can you please weigh in with some additional guidance? I have exhausted all the steps in the troubleshooting guides for remote access and am at a loss as to where to go from here to get back online.
