Hi, I’m experiencing the stuck certificate issue. My server is running fine locally (HTTP on port 32400 works, remote access shows as “Fully accessible”) but all plex.direct HTTPS connections fail and clients can’t connect securely.
-
Server: Plex Media Server v1.43.2.10687 (LinuxServer Docker, Ubuntu 24.04)
-
Symptom: plex.tv resources API shows provides="sync" and productVersion="4.18.1" for this server instead of correct values. All plex.direct connections fail; plain HTTP works.
Could you revoke my stuck certificate? I’ll stop and restart the server immediately after.
TIA
@dylanspann the stuck cert issue will appear in your logs as this error above. If you don’t have this error it is something else. Looking at your account the cert on your servers looks fine. Could just be a DNS issue or similar
Thanks for that. After following up on this I have more detail after digging into this.
The issue is that my server is stuck showing as provides=“sync” and productVersion=“4.18.1” in the plex.tv resources API instead of provides=“server”. Started June 5th after updating my Plex Docker container. The weird thing is that re-claiming temporarily fixes it for a brief window it’ll show provides=“server” but it always reverts back to “sync” even after a clean restart. The lastSeenAt timestamp was also frozen for over 24 hours despite the server being online and running the whole time, which makes me think something’s locked up on the plex.tv side rather than with the server itself.
I’ve ruled out the obvious stuff. DNS is fine — plex.direct resolves correctly to my Lan through both my Pi-hole and AdGuard Home. No 429 cert errors in the logs. HTTP and HTTPS both work on port 32400. The plex.direct URL with the current cert hash (65e8a5a2d5ed4dc3b083ac3a331e704e) connects and validates correctly. So the actual connection path is solid and it seems the problem is purely that plex.tv is misclassifying this server as a sync device instead of a media server, and that’s what’s killing my Android TV client (it won’t connect to anything that isn’t provides=“server”).
Server details if it helps:
Machine identifier: d29c8b18314c24ab2c35b8a7eccb392c2ecd5b49
Account: dylanspann.ds@gmail.com
Running 1.43.2.10687, LinuxServer Docker on Ubuntu 24.04
Any chance you can look at what’s going on with the backend classification for that machine identifier? It’s surviving re-claims and restarts which really does feel like it’s being set on your end rather than anything I can fix locally.
@dylanspann Are you using any third party apps that make API calls to your server?
Please review this thread Server stuck at provides="sync" with phantom productVersion=4.18.1 - #8 by Atomatth
Yes, you nailed it. After some more digging on the forums I found that thread you linked with the same issues where they called out kometa and the need for separate tokens for the different third party apps. That fixed it. Thank you!
