Same issue here, locally everything appears fine however plex.tv says my server is unreachable but if I change network security to preferred, then plex.tv says it may not be secure. Never had any issues until last night.
Plex Media Server Logs_2023-10-01_17-33-54.zip (226.9 KB)
a
I haven’t had time to sit with this and figure it out but thank you so much for your insight.
@ChuckPa reset certs please
https://acme-v02.api.letsencrypt.org/acme/order/44416311/212118645556 Valid Sun, 01 Oct 2023 13:45:31 +0000 Sun, 01 Oct 2023 13:45:47 +0000
AUTHORITY LETS ENCRYPT
STATUS GENERATED
CERTIFICATE ISSUED USING A LOCAL CSR? YES
CERTIFICATE EXPIRES AT DECEMBER 30, 2023 12:45
RATE LIMITED BY THE LET'S ENCRYPT API? NO
RATE LIMITED CSR UPLOAD NO
I see manual “Publish” PUT being sent to the server.
This is not necessary. The server is reachable and therefore already published
Next step:
– Stop Plex
– Remove file "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache/cert-v2.p12"
– Start Plex
Wait 2 minutes
Download logs zip and attach
@ChuckPa Thanks for the response, I have followed your steps as suggested. Attached are the logs.
Plex Media Server Logs_2023-10-04_23-08-01.zip (688.9 KB)
Your certificate was properly refreshed. Excellent
Your server is visible to Plex.tv
EventSource: Got event [data] '<Message address=“XX.XXX.XXX.XXX” port=“32400” asyncIdentifier=“12e37b76-ad99-42fa-9f76-0c3c1e6efd37” connectivity=“1”
Everything I see here looks like your machine is not openSSL v3.0.0 compliant.
It seems as if it’s v1.1.1 (now expired as of Sept 2023).
(35, SSL connect error) (OpenSSL/3.1.1: error:0A000410:SSL routines::sslv3 alert handshake failure)
Do you have openSSL v3.0.0 installed ?
Ref: Linux Tips - #25 by ChuckPa
The Linux Tip refers to custom certs but also requires openSSL v3.0.0 compliance.
Lastly, Are you attempting to use the ‘plex.direct’ URL to access the host ?
I got it. This will seem very dumb to a lot of people but I looked literally for a matching “Needed by device” IP address. Instead the answer was just my “Desktop”. See attached photo for anyone who is also sometimes too literal to be a functional human.
Hi there!
I’m hoping you can help. It sounds like I’m having an identical situation as the OP. On Thursday night my server (which has been running problem free for years) suddenly lost remote access and I have been unable to get it to come back no matter what I have tried.
Items I have tried:
Below is log file from Serverlog
Oct 04, 2023 20:14:59.200 [140268346280760] WARN - [HttpClient/HCl#1e66] HTTP error requesting GET https://xxx-xxx-xxx-xxx.60b9961153044df5bf97d12584f2d0f0.plex.direct:32400/identity (60, SSL peer certificate or SSH remote key was not OK) (SSL certificate problem: self-signed certificate)
Please assist, thank you very much.
Are you using your own certificate?
Which distro and version are you using?
Would it be possible to see your DEBUG server logs which are captured about 2 minutes AFTER restarting PMS ?
Hi ChuckPa, here’s the log file for your further assistance, thank you.
Plex Media Server.log (160.5 KB)
Thanks for the log.
Both Plex.tv and your log confirm the certificate is current and valid.
I do see where Plex.tv cannot reach the server (I’ve cut off the IP for your privacy)
PubSub: Got notified of reachability for async identifier 0989b464-c75c-4493-bbe4-90e232daa9c8: 0 for 202.xxx.xxx.xxx:32400
0 = not reachable (no remote access)
1 = reachable (remote access)
Are you certain your modem/router is forwarding port 32400/TCP to 192.168.0.250 (Synology IP)
Yes sir, screenshot as below. If certificate is ok, i will try to troubleshoot again, thank you Sir.
I did a ncat <your WAN IP> and received a timeout.
Connection timed out.
I can run mtr to your router without issue.
I just had a chance to look at your port forwarding: (sorry. the hour is late)
You forgot the WAN port.\
If you want to change the external port, that’s ok.
Whichever port you assign is what you tell PMS as the port number to use.
No problem, thank you very much for your assistance, i’ve tried all type of combination at Port Forwarding page also not able to solve this problem, maybe i will find another router to try again. Thank you.
Thanks Chuck, that was enough for me to solve the issue.
Server Version#: 1.32.6.7557
Player Version#: Multiple Devices
Hi there
Same here…
I‘m using Plex since 2019 and most time it works very well. Today remote access stopped working and I still don‘t know why. Tried it with manual port forwarding and set it up in my Router, but still can not access direct. Also tried to downgrade Plex to another Version, this also didn’t work… @ChuckPa Maybe a certificate Problem too?
Anybody can help?
Thank you all.
I checked both servers. The certificates are valid
Your current server WAN IP is pingable from my machine
Your server is not “published” status which means there is no port listed.
I did try 32400 with no success (timeout)
Thanks for your fast reply.
In this case I‘ll try manual port forwarding again. It‘s confusing, it just happened without any changes… I never had any problems with that…
They do sometimes stop working. What I’ve found for some customers is because the modem/router received a firmware update & reboot from the ISP. In those cases, manual port settings got erased / reset.
This is the other situation, which I just found in your logs
Oct 09, 2023 16:18:00.490 [140168420428600] DEBUG - [HttpClient/HCl#26] HTTP/2.0 (0.2s) 422 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx (reused)
Oct 09, 2023 16:18:00.490 [140168396610360] DEBUG - MyPlex: Published Mapping State response was 422
It got knocked offline and is trying to reset too quickly. Turn off remote access and let it sit a few minutes (up to an hour)
If you have a port number for me, I’ll check right now
