@ChuckPa @OttoKerner @BigWheel I assumed this was a one-time fix and then never again. But, you guys fixed my cert on December 29th, and my 429 issues have now returned today in my server logs. Will we need to contact you every 2 weeks to fix our certificates from now on? What’s the permanent fix?
Your server has been fetching a new certificate every restart since it was reset on 30 December. Plex.tv is asserting “No More”.
From the pattern I see, the UID/GID your docker container is running as DOES NOT HAVE PERMISSION to write the certificate into the Cache directory.
You need to get into the regular command line and fix all the ownership for all directories and files ( a sudo chown -R ..... operation) wherever your /config maps to on the real filesystem.
Please let me know when this is done and I’ll reset it again for you.
Everything in there looked like it was already owned by my UID/GID and the file write dates in the Cache directory show a recent time from my last server restart today. Regardless, I ran a chown -R on the host config directory anyway. Is there a specific file that I can be looking for and checking the date on in that Cache dir?
The Cache directory contains your certificate cert-v2.p12
[chuck@lizum Cache.1998]$ ls -la
total 100
drwxr-xr-x 8 chuck chuck 4096 Feb 3 2025 ./
drwxr-xr-x 14 chuck chuck 278 Feb 3 2025 ../
-rw------- 1 chuck chuck 4403 Jan 5 2025 cert-v2.p12
drwxr-xr-x 2 chuck chuck 21 Feb 3 2025 cl-icds-linux-x86_64/
-rw-r--r-- 1 chuck chuck 6048 Feb 3 2025 CloudAccessV2.dat
-rw-r--r-- 1 chuck chuck 12848 Feb 3 2025 CloudAccountV2.dat
-rw-r--r-- 1 chuck chuck 800 Feb 3 2025 CloudUsersF.dat
-rw-r--r-- 1 chuck chuck 4352 Feb 3 2025 CloudUsersServices.dat
-rw-r--r-- 1 chuck chuck 1040 Feb 3 2025 CloudUsersSubscriptionsV2.dat
-rw-r--r-- 1 chuck chuck 400 Feb 3 2025 CloudUsersV2.dat
-rw-r--r-- 1 chuck chuck 14640 Feb 3 2025 Flags.dat
drwxr-xr-x 2 chuck chuck 22 Feb 2 2025 OCSP/
drwxr-xr-x 258 chuck chuck 8192 May 10 2024 PhotoTranscoder/
-rw-r--r-- 1 chuck chuck 8112 Feb 3 2025 Privacy.dat
-rw-r--r-- 1 chuck chuck 4032 Oct 3 2024 relayHostKey.txt
drwxr-xr-x 3 chuck chuck 18 Feb 3 2025 Shaders/
drwxr-xr-x 5 chuck chuck 56 Aug 1 2024 Transcode/
-rw-r--r-- 1 chuck chuck 784 Feb 3 2025 UpdateChannels.dat
drwxr-xr-x 2 chuck chuck 59 Feb 3 2025 va-dri-linux-x86_64/
[chuck@lizum Cache.1999]$
I will reset your certificates now.
You can restart PMS in about 5 minutes
Your new certificate is ready.
If this occurs again then you need to find out what’s causing it
OK, I listed before the chown -R and got this.
total 108
drwxr-xr-x 6 adam adam 4096 Jan 12 20:30 .
drwxr-xr-x 15 adam adam 4096 Jan 12 20:23 ..
-rw------- 1 adam adam 4435 Jan 12 20:15 cert-v2.p12
drwxr-xr-x 2 adam adam 4096 Jan 12 04:00 cl-icds-linux-x86_64
-rw-r--r-- 1 adam adam 6544 Jan 12 20:23 CloudAccessV2.dat
-rw-r--r-- 1 adam adam 14032 Jan 12 20:22 CloudAccountV2.dat
-rw-r--r-- 1 adam adam 1376 Jan 12 20:22 CloudUsersF.dat
-rw-r--r-- 1 adam adam 4528 Jan 12 20:25 CloudUsersServices.dat
-rw-r--r-- 1 adam adam 576 Jan 12 20:23 CloudUsersSubscriptionsV2.dat
-rw-r--r-- 1 adam adam 560 Jan 12 20:23 CloudUsersV2.dat
-rw-r--r-- 1 adam adam 13216 Jan 12 20:22 Flags.dat
drwxr-xr-x 3 adam adam 4096 Jan 12 19:54 Http
drwxr-xr-x 159 adam adam 4096 Jan 12 20:24 PhotoTranscoder
-rw-r--r-- 1 adam adam 8352 Jan 12 20:22 Privacy.dat
-rw-r--r-- 1 adam adam 384 Jan 12 20:22 UpdateChannels.dat
drwxr-xr-x 2 adam adam 4096 Jan 12 04:00 va-dri-linux-x86_64
Restarted just now and now I have this:
total 108
drwxr-xr-x 6 adam adam 4096 Jan 12 20:58 .
drwxr-xr-x 15 adam adam 4096 Jan 12 20:58 ..
-rw------- 1 adam adam 4435 Jan 12 20:49 cert-v2.p12
drwxr-xr-x 2 adam adam 4096 Jan 12 04:00 cl-icds-linux-x86_64
-rw-r--r-- 1 adam adam 6544 Jan 12 20:58 CloudAccessV2.dat
-rw-r--r-- 1 adam adam 14032 Jan 12 20:58 CloudAccountV2.dat
-rw-r--r-- 1 adam adam 1376 Jan 12 20:58 CloudUsersF.dat
-rw-r--r-- 1 adam adam 4528 Jan 12 20:25 CloudUsersServices.dat
-rw-r--r-- 1 adam adam 576 Jan 12 20:58 CloudUsersSubscriptionsV2.dat
-rw-r--r-- 1 adam adam 560 Jan 12 20:58 CloudUsersV2.dat
-rw-r--r-- 1 adam adam 13216 Jan 12 20:58 Flags.dat
drwxr-xr-x 3 adam adam 4096 Jan 12 19:54 Http
drwxr-xr-x 186 adam adam 4096 Jan 12 20:43 PhotoTranscoder
-rw-r--r-- 1 adam adam 8352 Jan 12 20:58 Privacy.dat
-rw-r--r-- 1 adam adam 384 Jan 12 20:58 UpdateChannels.dat
drwxr-xr-x 2 adam adam 4096 Jan 12 04:00 va-dri-linux-x86_64
The only way to know if this is still a problem is to restart the container.
Please stop it, wait 60 seconds, then restart it and check the date/time stamps.
The chown -R should have modified the date/time stamp of ALL directories.
total 108
drwxr-xr-x 6 adam adam 4096 Jan 12 20:58 .
drwxr-xr-x 15 adam adam 4096 Jan 12 20:58 ..
-rw------- 1 adam adam 4435 Jan 12 20:49 cert-v2.p12
drwxr-xr-x 2 adam adam 4096 Jan 12 04:00 cl-icds-linux-x86_64
-rw-r--r-- 1 adam adam 6544 Jan 12 20:58 CloudAccessV2.dat
-rw-r--r-- 1 adam adam 14032 Jan 12 20:58 CloudAccountV2.dat
-rw-r--r-- 1 adam adam 1376 Jan 12 20:58 CloudUsersF.dat
-rw-r--r-- 1 adam adam 4528 Jan 12 20:25 CloudUsersServices.dat
-rw-r--r-- 1 adam adam 576 Jan 12 20:58 CloudUsersSubscriptionsV2.dat
-rw-r--r-- 1 adam adam 560 Jan 12 20:58 CloudUsersV2.dat
-rw-r--r-- 1 adam adam 13216 Jan 12 20:58 Flags.dat
drwxr-xr-x 3 adam adam 4096 Jan 12 19:54 Http
drwxr-xr-x 186 adam adam 4096 Jan 12 20:43 PhotoTranscoder
-rw-r--r-- 1 adam adam 8352 Jan 12 20:58 Privacy.dat
-rw-r--r-- 1 adam adam 384 Jan 12 20:58 UpdateChannels.dat
drwxr-xr-x 2 adam adam 4096 Jan 12 04:00 va-dri-linux-x86_64
I suspect the problem isn’t solved yet.
This is why stopping and restarting the container will be necessary.
Whose image are you using?
lscr.io/linuxserver/plex:latest It was working from April to December with no troubles.
After the stop, 60s wait and restart, the timestamp on the cert is unchanged from before the restart and these are my “cert” log entries:
Jan 13, 2026 14:59:49.032 [128902323341968] DEBUG - [CERT] Subject name is /CN=*.<REMOVED FOR FORUM>.plex.direct
Jan 13, 2026 14:59:49.033 [128902323341968] DEBUG - [CERT] Installed certificate with fingerprint <REMOVED FOR FORUM>.
Jan 13, 2026 14:59:49.033 [128902323341968] DEBUG - [CERT/OCSP] no URL available
Jan 13, 2026 14:59:49.033 [128902323341968] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
Jan 13, 2026 14:59:53.164 [128902254050104] DEBUG - CERT: Certificate will not expire soon; we'll check again in a week.
I have a nightly cron job that cleans data from the Cache and Logs folders and restarts the server. Would a once-daily download of the cert cause 429 errors?
I have the same issue, please can you reset my certificate as well?
Your certificate is not stuck / invalid.
Your server DEBUG logs which capture startup through error will be needed.
If you’re purging the contents of the Cache daily – it ABSOLUTELY will cause this problem.
The ONLY thing you want to delete from Cache is the contents of the Transcode directory. PMS MUST also be stopped if you’re deleting it.
You’re better off moving the transcoder temp to another location first then deleting/purging that location.
Plex certificates are valid for 90 days. Plex.tv allows normal refresh/update based on this schedule (with a 15 cert tolerance for high-fault conditions)
1 Like
debug.txt (136.5 KB)
when users connect to either http://mywanip:port/web or https://app.plex.tv they see my plex logon, but all TV apps failing. The first issue started because I blocked US traffic inbound at the router end and I think you have moved your workers from Ireland to USA, and after opening that up, I can establish a green remote connect, but all remote TV clients just get a spinning wheel after I relink them
Hi there, I’ve started having remote access issues as well. Could you check my cert? I’m getting the secure connection issue as well. @ChuckPa @OttoKerner
Your certificate is valid on both servers.
Next step in diagnosis is to make certain UPNP in the moden/router is not malfunctioning (table might be full and need cleaning)
-or-
The port forwarding rules & port forwarding settings in PMS match
To confirm which server you’re using,
- Make certain DEBUG logging is enabled
- Restart PMS
- Let it sit completely idle for 3 minutes
- Download the logs ZIP file
- Attach here
In that ZIP file we will be able to see which server PMS is reaching out to.
Looks like I needed to disable IPv6 on my router for some reason. It seems to be working properly now. Not sure why it quit as it was working as expected for quite a while before this. Either way, thanks for checking on that!
You DISabled DEBUG logging. Please ENABLE it, SAVE, and restart PMS.
Jan 14, 2026 20:23:24.962 [139806415022904] INFO - Plex Media Server v1.42.2.10156-f737b826c - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT 00:00
Jan 14, 2026 20:23:24.962 [139806415022904] INFO - Linux version: 6.17.8-300.fc43.x86_64, language: en-US
Jan 14, 2026 20:23:24.962 [139806415022904] INFO - Processor: 4-core Intel(R) N150
Jan 14, 2026 20:23:24.962 [139806415022904] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Jan 14, 2026 20:23:24.962 [139806415022904] INFO - /usr/lib/plexmediaserver/Plex Media Server
Jan 14, 2026 20:23:25.013 [139806417603216] WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
Jan 14, 2026 20:23:25.014 [139806417603216] INFO - Running migrations. (EPG 0)
Jan 14, 2026 20:23:25.799 [139806417603216] INFO - Running migrations. (EPG 0)
Jan 14, 2026 20:23:25.801 [139806410246968] INFO - Preemptively preparing driver imd for GPU Intel Alder Lake-N [Intel Graphics]
Jan 14, 2026 20:23:25.801 [139806410246968] INFO - Preemptively preparing driver icr for GPU Intel Alder Lake-N [Intel Graphics]
Jan 14, 2026 20:23:26.960 [139806366899000] WARN - Crash: Crash reporting disabled
Jan 14, 2026 20:23:27.203 [139806360374072] INFO - Refreshing paths watched by LibraryUpdateManager
Jan 14, 2026 20:23:27.277 [139806410246968] WARN - [DatabaseFixups/35DatabaseFixupsConsolidatePeopleTags] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/DatabaseFixups.cpp:374): 0.110000 seconds
Jan 14, 2026 20:23:28.090 [139806400170808] WARN - [EventSourceClient/pubsub/109.237.24.233:443] MyPlex: attempted a reachability check but we're not yet mapped.
Jan 14, 2026 20:23:37.135 [139806291823416] ERROR - Subscription: Error refreshing sub: Could not find providers for subscription
Jan 14, 2026 20:23:37.137 [139806289713976] ERROR - Subscription: Error refreshing sub: Could not find providers for subscription
Jan 14, 2026 20:23:37.142 [139806283414328] ERROR - Subscription: Error refreshing sub: Could not find providers for subscription
Jan 14, 2026 20:23:39.802 [139806369008440] WARN - NAT: PMP, got an error: Not Supported by gateway.
Jan 14, 2026 20:23:43.689 [139806364789560] WARN - [HttpClient/HCl#29] HTTP error requesting GET http://192.168.0.119:80/discover.json (7, Couldn't connect to server) (Failed to connect to 192.168.0.119 port 80 after 3075 ms: Couldn't connect to server)
Jan 14, 2026 20:23:43.696 [139806410246968] ERROR - DVR:Device: Error refreshing existing device device://tv.plex.grabbers.hdhomerun/1250306C, marking as dead.
Jan 14, 2026 20:23:46.159 [139806291823416] ERROR - Subscription: Error refreshing sub: Could not find providers for subscription
Jan 14, 2026 20:23:46.160 [139806283414328] ERROR - Subscription: Error refreshing sub: Could not find providers for subscription
Jan 14, 2026 20:23:46.169 [139806289713976] ERROR - Subscription: Error refreshing sub: Could not find providers for subscription
Jan 14, 2026 20:26:19.881 [139806287604536] INFO - [Req#fb] AutoUpdate: no updates available
Jan 14, 2026 20:26:21.683 [139806354045752] INFO - [Req#114] AutoUpdate: no updates availab
These are the settings for the Plex web app, not those for the Plex media server.
Changes in logging level require a subsequent stop and restart of the server.
