# My Cloud Home plex.direct certificate reset needed **URL:** \ **Category:** Remote Access\ **Tags:** server-western-digital, networking\ **Created:** [June 19, 2026, 12:06pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835 "2026-06-19T12:06:20Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![KareemHolt86](https://avatars.discourse-cdn.com/v4/letter/k/9f8e36/32.png) [@KareemHolt86](https://forums.plex.tv/u/KareemHolt86)\ **Post date:** [June 19, 2026, 12:06pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/1 "2026-06-19T12:06:21Z")
WD My Cloud Home running PMS 1.43.0.10492. Remote access only works through Relay. Port 32400 was verified with tcpdump. Logs repeatedly show “SSL certificate problem: unable to get local issuer certificate” and “[CERT/OCSP] getCertInfo failed.” Please check and reset/revoke my server certificate. thanks [plex-logs-upload.tar.gz](https://forums.plex.tv/uploads/short-url/hTSLb9QxDzGzvdsGEuTOlUIILBH.gz) (84.3 KB) ---
**Author:** ![pl\_5309](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@pl\_5309](https://forums.plex.tv/u/pl_5309)\ **Post date:** [June 19, 2026, 2:21pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/2 "2026-06-19T14:21:19Z")
You have other issues contributing to the problem. When the cert was created the ip of you WD was 192.168.0.160, it is now 192.168.0.206 so it is likely that your port forward is also incorrect. Update your port forward and it might be able to untwist itself. ---
**Author:** ![KareemHolt86](https://avatars.discourse-cdn.com/v4/letter/k/9f8e36/32.png) [@KareemHolt86](https://forums.plex.tv/u/KareemHolt86)\ **Post date:** [June 19, 2026, 5:40pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/3 "2026-06-19T17:40:10Z")
> [@pl\_5309](#): > > 192.168.0.206 192.168.0.206 is the client computer accessing Plex Web. The My Cloud Home/PMS is still 192.168.0.160. Tcpdump confirmed WAN traffic is translated to 192.168.0.160:32400 and the server replies. The port forward is correct. The remaining repeated error is “unable to get local issuer certificate” for plex.direct. ---
**Author:** ![pl\_5309](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@pl\_5309](https://forums.plex.tv/u/pl_5309)\ **Post date:** [June 19, 2026, 7:30pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/4 "2026-06-19T19:30:19Z")
Taking a slower look at the files: You do have some CERT weirdness going on but not the 429 rate limit error. DNS doesn’t resolve against your plex.direct address and you have error 60. _cURL error 60 is an SSL certificate verification failure where cURL cannot verify the remote server’s identity against local Certificate Authority (CA) certificates. This typically occurs due to outdated CA bundles, self-signed certificates, expired certificates, or corporate proxy interference._ Other than checking the time on your devices and fixing your DNS I have no other suggestions. ---
**Author:** ![KareemHolt86](https://avatars.discourse-cdn.com/v4/letter/k/9f8e36/32.png) [@KareemHolt86](https://forums.plex.tv/u/KareemHolt86)\ **Post date:** [June 19, 2026, 8:16pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/5 "2026-06-19T20:16:20Z")
> [@pl\_5309](#): > > cURL error 60 is an SSL certificate verification failure where cURL cannot verify the remote server’s identity against local Certificate Authority (CA) certificates. This typically occurs due to outdated CA bundles, self-signed certificates, expired certificates, or corporate proxy interference OpenSSL confirms the certificate is valid and issued by YR2, but PMS serves only 2 certificate blocks. Verification returns error 20. The correct chain should be EE → YR2 → Root YR → ISRG Root X1, so the cross-signed Root YR intermediate appears missing. Since this is My Cloud Home, I cannot manually replace the certificate bundle. Please reset/reissue it with the complete chain. ---
**Author:** ![KareemHolt86](https://avatars.discourse-cdn.com/v4/letter/k/9f8e36/32.png) [@KareemHolt86](https://forums.plex.tv/u/KareemHolt86)\ **Post date:** [June 20, 2026, 12:54am UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/6 "2026-06-20T00:54:01Z")
My Android phone can reach the server directly on cellular by opening [http://172.249.238.22:32400/identity](http://172.249.238.22:32400/identity). It returns the Plex MediaContainer XML with the correct machineIdentifier. A TV on a different network also plays Direct Play remotely. So the server and port forward are reachable. The problem appears to be Plex app discovery/certificate validation. The Android app still shows the server offline while direct HTTP access works. ---
**Author:** ![pl\_5309](https://avatars.discourse-cdn.com/v4/letter/p/2bfe46/32.png) [@pl\_5309](https://forums.plex.tv/u/pl_5309)\ **Post date:** [June 20, 2026, 3:59pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/7 "2026-06-20T15:59:49Z")
The new apps use HTTPS. Since you believe it is a CERT issue: Stop Plex Find your cert-v2.p12 file, rename or remove. Somewhere in the path ~/Library/Application Support/Plex Media Server/Cache Start Plex and wait for a new one to be downloaded. Let’s Encrypt has a rate limit so I would not do this repeatedly. ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [September 18, 2026, 4:00pm UTC](https://forums.plex.tv/t/my-cloud-home-plex-direct-certificate-reset-needed/939835/8 "2026-09-18T16:00:38Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.