Server Version#:1.43.5.11029
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
What have you done to try and fix it so far?
Are you using a manual port forward? Did you check if the rule is still valid?
What does this say for the port you opened: https://canyouseeme.org/ ?
Did your ISP move you behind CGNAT? Your router would report it’s WAN IP between 100.64.0.0 - 100.127.255.255 if you were. If it’s not in that range, does the ip match the ip shown at the canyouseeme site above?
What’s your network setup like? What equipment? Just an ISP gateway?
Thank you for answering, I’ve done some of the troubleshooting found today in another post, checked the certificate v2. I’m not using a manual port forwarding, I was relying mostly on the UnPn.
My setup would be the huawei router from my ISP, then all it’s connected through a Deco X20 from Tp Link i t was working previously, after finishing the update, I got an error and I had to reload the page of my server, and then, it didn’t worked, I do not use docker or anything like that, just my laptop connected with some hardrivers and normal plex install on windows.
My 2 sons and myself were having the same issue. We solved it by getting a new cert from plex. Here are the instructions I used on different platforms
On Linux:
sudo systemctl stop plexmediaserver
cd “/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache”
ls *.p12 sudo
mv certificate.p12 certificate.p12.bak
sudo systemctl start plexmediaserver
On macOS:
osascript -e ‘quit app “Plex Media Server”’
cd ~/Library/Application\ Support/Plex\ Media\ Server/Cache
ls *.p12 mvcertificate.p12 certificate.p12.bak
open -a “Plex Media Server”
On Windows, using powershell:
Stop-Process -Name “Plex Media Server” -Force
cd “$env:LOCALAPPDATA\Plex Media Server\Cache”
dir *.p12
Rename-Item certificate.p12 certificate.p12.bak
Then start Plex from the Start menu or tray. If Plex runs as a Windows service, use Stop-Service PlexService and Start-Service PlexService instead of the process commands.
Thank you, seems that helped, I am not guetting the message about my server being available outside my network, it just keeps looking to make the connection, but I was able to reach it… did you experience the same?
In your previous reply you mentioned having v2 of the certificate, so you already had the right cert type.
Same questions as before:
What does this say for the port that is listed in plex next to the public ip: https://canyouseeme.org/ ?
Did your ISP move you behind CGNAT? Your router would report it’s WAN IP between 100.64.0.0 - 100.127.255.255 if you were. If it’s not in that range, does the ip match the ip shown at the canyouseeme site above?
Is the huawei a router or just an ONT/modem? If it’s a router, did you bridge it so that you aren’t doubleNAT with the TPLink?
I am not that tech savy, I getting the message “Your server is signed in to Plex, but is not reachable from outside your network.” yet, I was able to reach it. I see the ip matching but port does not.
I have not changed anything on the router, after ISP installation, I installed the TP Link Deco X20, and it is currently as router mode. I tried setting a static IP for my laptop, as I am running Plex using a Windows computer with some hard drives connected to it.
Let’s start at the beginning, what are the models of each network device you have? Especially the Huawei.
Who is your isp?
Where did you see the ip matching? In the router and on the canyouseeme site?
The port does match? Not sure what that means. You need to enter the port that is being forwarded onto that site to test it.
How were you able to reach it? If the port isn’t open, you are likely connecting over plex relay, which is bandwidth limited to 2Mbps. You can go into the plex network settings and uncheck “enable relay” to see if you can still connect with it disabled.
I’m gonna assume you need to setup a manual port forward, but need to confirm the other questions. UPnP prob got disabled on your router, if that’s how it was working before.
The model of the huawei it is HG8145X6-10, and the Deco it is Deco X20. I am outside of US, so my ISP its company called Claro.
I believe im connecting over the plex relay, because the tab of remote access just keep spining or shows the error that the sever is signed in but it is not reachable outside the network. I do not have access to enable port forwarding on the Huawei, I tried using the Deco but no sucess, I installed the update 1.43.4 which does not give any issue.
A quick Google search (could be wrong) states that Claro uses CGNAT, which will make traditional port forwarding not possible. You can contact them and ask that they remove you and give you a dynamic publicly routable ipv4 address. You can say it’s for work and they require it…
If they do that, you then need to put the Huawei into bridge mode, since the model you shared is also a router and having that plus your TPLink is another DoubleNAT, making it not possible to port forward with the TPLink.
Once you get the bridge mode setup, you can setup the port forward on the TPLink.
If the ISP won’t do the first step, you can ignore the other steps for normal port forwarding
The alternative is if Claro gives you an ipv6 that doesn’t filter traffic. Can test for IPv6 here: https://test-ipv6.com/ , it won’t tell you about the filtering piece though. If it does give you one, you can put the Huawei into bridge mode and then allow 32400 through the ipv6 firewall. This will make your server reachable on IPv6 networks remotely.
Is this the correct syntax for the last command in your Windows instructions?
Rename-Item certificate.p12 certificate.p12.bak
I get an error message: certificate.p12 does not exist.
Thank you in advance.
JLK
Madison, Wisconsin
Go to the Cache directory in your plex media server folder in your user local app data. If you already have cert-v2.p12, there’s nothing to rename, you have the correct cert type.
%LOCALAPPDATA%\Plex Media Server
https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/
If there is a certificate.p12, just right click and rename it after stopping plex.
My Plex server worked properly for years, but after the latest update it constantly says: “Checking remote access.”
I searched for days, checked everything on the network, the port has been open the whole time, and I eventually replaced the certificate as well. After that, it worked continuously for about a day and a half before it again said that it was not remotely accessible this morning. It currently still says it is unavailable, but I can connect to the server.
There is definitely a bug in the latest update. If someone keeps restarting the device, it does not show up, but if it runs continuously, the remote connection error appears. (On my Windows setup.)
So, in my case:
-
It is not a firewall issue
-
It is not a network configuration issue
-
It is not a certificate issue
Suggest creating a new thread with details of your setup and what you’ve done and include debug server logs.
Just some quick questions/suggestions:
When you did the cert refresh, did it download cert-v2.p12? You said it started working after doing that once, but then went back to not working. Did plex download certificate.p12 again and remove the v2?
Do you have Strict TLS enabled in your plex network settings? If not, enable it and restart the server.
Some have had to redownload the entire Cache directory to fix similar issues. Can stop plex, rename the folder Cache.old and then start plex back up.
I rolled back to Version 1.42.2.10156 and remote access is working again 
Do not run that version:
version 11079 does not seem to be good with remote access … i am back on an older version 10903 and its better, but drops occasionally remotely … very upset and confused … was fine for years, then something happed somewhere … still working on a fix …
Thanks for this, it fixed my remote access, but on macOS Monterey I had to look in a different folder.
On this version of MacOS, Plex Media Server doesn’t keep its cache in:
~/Library/Application Support/Plex Media Server/Cache.
It uses:
~/Library/Caches/PlexMediaServer
and that’s where certificate.p12 is.
To quit Plex and rename the certificate do the following:
osascript -e 'quit app "Plex Media Server"'
cd ~/Library/Caches/PlexMediaServer
mv certificate.p12 certificate.p12.bak
open -a "Plex Media Server"
Give it a minute, then in Plex click Retry under Settings → Remote Access.
Mine went green straight away.
Thanks a bunch, this fixed it for me as well. #LifeSaver
I reached out to them and seems they cannot help me with the dynamic ipv4 address. So, I am stuck as I cannot have the remote access available. Last update broke everything.
