it also should not matter but may want to change this to IPv4 only.
By the way, Thank you so much for trying to get this working. Very impressed.
In the Plex Media Server folder should be a caches folder where you should be able to find a file called cert-v2.p12 . This is the cached cert. I think it is trying to use that old locally cached cert instead of installing the new one that was created.
stop server, move that file to desktop for backup, then restart server again. hopefully it will use the new cert.
Not seeing a caches folder
Stopped server, Found cert-v2 and removed to desktop. Restarted. Still no remote.
Did you confirm youâre not behind CGNAT or a double NAT by your isp? I donât usually trust the support folks at the ISPs.
In your router for WAN ip (donât look at the public ip on the plex remote access page), is it between 100.64.0.0. - 100.127.255.255? If not, does it match the ip seen at https://whatsmyip.com ?
Ip address is between those
That means youâre CGNAT and canât use the built in port forwarding. Youâll have to contact the ISP and see if they will remove you and give you a publicly routable dynamic ipv4, either free or for a monthly fee, if not, maybe they offer a static ip, but that will come with a fee.
Strange. I had them give me a static ip address when I first setup Plex. It was no charge. So it has worked for years. Strange that it changed around the same time the Plex DNS issues happened and lost remote access. Maybe I didnât use the right terminology with customer service. Thanks.
All solved. Thanks to all for the help. Much appreciated. I had already setup an appointment for ip to come out. I had an older modem they said needed upgrading. Seems I never had a static ip according to them. Weird how it worked fine for 5 years with Plex. Anyway, paid for a static ip and is working great, minus the monthly charge groans now. Worth it to have it all rolling smooth.
So the mid day issue seemed to only happen once. So Iâm not gonna go down that hole. I will pause my script from running this Friday and see if the issue persists. If it does I will then need to replicate it and grab logs. A quick restart PMS Script after a 4AM reboot is an easy fix. Just odd that it started randomly. But also seems like my issue will be unrealted to this, so i would start a new issue if needed.
Thanks,
