Hello. My remote access is no longer working as of about 15 days ago with no network or PMS changes. Updated to latest PMS and did not solve. No changes to my wifi/router, but rebooted as well and port forward is still present (upnp is not enabled, but port forward has been working for years). Looking at the forum, seems others are having a the same issue and my certificate may have expired. I am NOT using a custom certificate. I do see an ‘DEBUG - CERT: incomplete TLS handshake from 192.168.1.x:52080: sslv3 alert certificate unknown (SSL routines)’ in the log when I do a retry of the remote access connection. Attached a redacted log as well.
If nothing in my logs seems like my cert expired, then I think my ISP may have decided to enable CG-NAT per your troubleshooting guide (and I might be out of luck), however the public IP (what is my ip) that is showing has not changed in a couple of years as my opendns content settings still work fine.
ALL RFC-1918 addresses are NON-ROUTABLE; meaning they do not need to be redacted. The Internet does not allow those addresses outside your modem-router nor do the Internet routers pass them even if the address did get out.
Your certificate is OK. It was generated in May and is valid through end of this month (when it will renew)
This looks like someone using an old plex.direct address (which expired long ago)
Something did change. – perhaps on your side because I do see your server Published at your WAN address (about 2 hours before my reply here)
Since you previously posted 6 hours ago, Have you been able to resolve it?
Just rechecked…it is still not working. The logs I provided were from a week ago when I first made an inquiry via DM, then was asked to repost here. I have attached updated logs just now when performing a retry again. What do you mean by old plex.direct? Again, no changes on my router or PMS server - just stopped working. Updated to slightly newer version just in case, rebooted, and rebooted router - no difference.
When retrying the remote access on the console, it says 'fully accessible outside your network, then after about 3-5 seconds, it goes back to 'not available outside your network. If you need more logs I can send, just trying to capture the retry effort by the server.
I don’t know if you’re using your own certificate (which PMS isn’t recognizing) or it’s something else.
Would you like to try a certificate reset ?
If you have your own certificate then I’d make certain it meets the new SSL v3.0.0 specification (which PMS requires as of 1.32.0)
I just disabled remote access and will leave it disabled until this evening (more than 8 hours). I am not using a custom cert, so willing to try a cert reset.
If it’s not working then it is definitely on your end.
Check the port numbers and each forwarding rules then also check the Linux firewall rule(s) if you have them enabled.
The host must allow 32400/TCP at the host.
External WAN port (TCP) is whatever port number you decide.
(Did you manually specify one or use UPNP – Is UPNP working?)
I can’t tell what’s happening; You turned off DEBUG logging.
Remote Access issues are 99% not a server certificate.
It’s been common experience for Modem/Router updates (clears/disabled port forwarding / UPNP). OS firewalls reset open ports (Synology DSM frequently does this)
Your best tool is canyouseeme.org.
From there, you walk through to confirm the port is open all the way through.
When confirmed. DEBUG server logs can take us the last step.