From the remote access screen, Plex is showing that my server is fully accessible outside of my network. However, when I attempt to log on from my phone on 5g, or from a family member’s house, my server is not available.
My router is configured properly, and the correct ports are open.
I run other remote services on my server and I’m able to access them outside my network with no issues
My public IP address matches my router, plex server, and whatismyip.com
I’ve tried disabling and re-enabling remote access, no luck
I’ve tried re-starting my router, again, no luck
Can you access the specified public port used by Plex from outside your home network?
Other services working ok will do you little good if your ISP is blocking certain ports or traffic (not saying this is your issue… but it’s a possible scenario).
Original Port: 443
Protocol: TCP
Forward to address: 192.168.2.10
Forward to port: 32400
When I use a port checker online, the tool reports that port 443 is open. This should allow traffic tagged for 32400 to pass and be forwarded on to my server, yes?
seems like.
however… if it’s not working, you’ll need to dig a bit deeper – e.g. will it stream if you use a different public port?
If that’s not it – have you verified the route inside your home network?
Nothing has changed in my internal network. I’ve had remote access up and running for almost 2 years now with no issues. This only started happening after I updated to the most recent version of PMS. So it’s either the update or yesterdays outage, and I’m leaning towards the update.
I believe I am having exactly the same problem. I just did an update and poof remote access is broken. No network changes on my side. Everything was working until the update.
I did find this in the logs if that helps.
Feb 03, 2022 18:03:58.658 [10828] DEBUG - CERT: incomplete TLS handshake from 127.0.0.1:51030: sslv3 alert bad certificate
Feb 03, 2022 18:04:03.963 [10824] WARN - [CERT] TLS connection from 192.168.1.125:28636 came in with unrecognized plex.direct SNI name ‘192-168-1-124.4385a369d66c432db2e3f5421c01548e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 18:04:03.971 [10828] DEBUG - CERT: incomplete TLS handshake from 192.168.1.125:28636: sslv3 alert certificate unknown
Feb 03, 2022 18:04:03.986 [10824] WARN - [CERT] TLS connection from 192.168.1.1:28637 came in with unrecognized plex.direct SNI name ‘97-113-114-105.4385a369d66c432db2e3f5421c01548e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 18:04:03.995 [10828] DEBUG - CERT: incomplete TLS handshake from 192.168.1.1:28637: sslv3 alert certificate unknown
Feb 03, 2022 18:04:04.233 [10824] WARN - [CERT] TLS connection from 127.0.0.1:51032 came in with unrecognized plex.direct SNI name ‘184-105-148-84.4385a369d66c432db2e3f5421c01548e.plex.direct’; using installed plex.direct cert
Feb 03, 2022 18:04:04.397 [10828] DEBUG - CERT: incomplete TLS handshake from 127.0.0.1:51032: sslv3 alert certificate unknown
Similar problem here. Updated to the latest server update and now iPad app takes a very long time to connect to my computer and then seems to freeze and do nothing. Not sure if it was the server update or the updated iOS app.
I seem to be having the same issue it’s accessible locally, shows everything green on the connection page but is inaccessible from outside the network. I’ll try upgrading to v1.25.3 and let you know how it goes. (After I backup my library)
[edit] Sad to report that this didn’t do a thing, neither did refreshing the certificate
I’m also having this same issue. Remote access has worked for a year, but stopped working sometime in February. I added port forwarding settings in my router, still doesn’t work. I get a message “Not enough bandwidth for direct play of this item. Required bandwith is XXXXkbps and only 720kbps is available. Could not transcode because: Not enough CPU for conversion of this item.”
to v1.25.3 and let you know how it goes. (After I backup my library)