Refresh Plex Certificate

Plex Media Server Remote Access
1

Dear Plex Support Team,

I am writing to request a manual reset of the SSL certificate for my Plex Media Server. I believe my server’s certificate is stuck during the renewal process, which is preventing remote access from working correctly .

My Plex Username: vadim.barkovsky

Server Platform: Synology NAS (DSM)

Version: Plex Media Server for Synology

Symptoms:

· Remote Access shows as “Fully accessible” in server settings.
· Port 32400 is confirmed open and reachable from the internet (verified via canyouseeme.org and ping.eu).
· I can access the server locally via http://192.168.1.2:32400/web.
· Issue: Remote access from outside my local network fails. The web page at http://[public_ip]:32400/web opens (sometimes partially), but libraries do not load and the connection seems to hang. The Plex app on my phone also cannot access libraries when not on the local network.
· Important: The problem does not occur when using a VPN. All remote clients connect successfully when VPN is enabled, confirming the server itself is working and the port is open.

What I have already tried:

  1. Confirmed the port is open from multiple external checkers.
  2. Reset the “Manually specify public port” setting in Plex.
  3. Restarted the Plex Media Server multiple times.
  4. Restarted the router and NAS.
  5. Verified no firewall issues.

I have also contacted my ISP who confirmed they are not blocking any traffic on their side.

Based on forum discussions, this appears to be a classic certificate issue where the server is unable to obtain a valid certificate from plex.tv (perhaps getting “CERT: Error acquiring new certificate: Failed to upload CSR: 429” in the logs) . This is why the web page loads (HTTP), but the secure connection for data transfer (HTTPS via plex.direct) fails .

I would be very grateful if you could reset the SSL certificate for my server, as is commonly done in the Plex forums for similar cases . Please let me know if you need any additional information from my server logs.

Thank you for your time and assistance.

Best regards,

Vadim

2

Did I write something wrong? I’m concerned that I haven’t received a reply. Please help me figure it out if I’m not in the right place.

3

You mentioned it may be the stuck certificate issue, did you see the CSR: 429 error in your logs? Can post your logs if you want someone to take a look for any potential issues.

On your Synology make sure the time is correct and you’re using a time server to do the sync.

Set the DNS servers on the Synology to 8.8.8.8/8.8.4.4 or 1.1.1.1/1.0.0.1

You can try to force a new cert yourself. Stop plex, remove the cert-v2.p12 file from the Cache directory in the server folder and then start Plex back up. Disable remote access, then enable it and wait a few minutes for it to grab a new cert.

4

Thank you very much for your time and assistance.

I followed your recommendation:

  1. Stopped the Plex Media Server.

  2. Removed the cert-v2.p12 file from the Cache folder.

  3. Restarted the server.

After the restart, the new cert-v2.p12 file did not appear, and remote access is still not working.

I am attaching the full server logs (Logs.zip) for your review.

For context:

  • Remote Access shows as “Fully accessible”.

  • Port 32400 is confirmed open (verified via canyouseeme.org and ping.eu).

  • The web page at http://79.111.12.13:32400/web opens, but libraries do not load.

  • Remote access works perfectly over VPN.

Could you please check my server logs and reset the certificate on your side if needed?

Thank you again for your time.

Logs.zip (2.7 MB)

5

Did you disable, and then enable remote access in Plex after restarting?

Is your VPN disabled? It can be blocking the server from refreshing the certificate. When you connect over vpn, if it’s a vpn you setup for remote connections, you’re essentially connecting locally, so the secure connection piece that the certificate enables isn’t used if it can connect “insecurely”, which is why it’s likely working when you use it.

Hopefully someone from the Plex team can refresh your cert on their end to push a new one.

6

Your cert is reset.

7

@veeejay

Yes, I did disable and re-enable remote access in Plex after the restart — it didn’t help.

Regarding the VPN: I only use it on my phone to connect when I’m away from home. The server itself (on the Synology NAS) does not have any VPN enabled.

I will wait for someone from the Plex team to refresh the certificate on their end, as you suggested.

Thanks again for your time and assistance!

8

@BigWheel @veeejay

Thank you for resetting the certificate on your side. Unfortunately, remote access still does not work when connecting through my (1’st) mobile operator, even after a full server restart and reapplying remote access settings.

To confirm, here’s the situation:

· Port 32400 is open and reachable from the internet (verified with canyouseeme.org and ping.eu).
· Remote access works perfectly when using VPN or when connecting via another connect (my 2’nd mobile operator).
· The issue persists only when using @BigWheel @veeejay

Thank you for resetting the certificate on your side. Unfortunately, remote access still does not work when connecting through my mobile operator (1’st), even after a full server restart and reapplying remote access settings.

To confirm, here’s the situation:

· Port 32400 is open and reachable from the internet (verified with canyouseeme.org and ping.eu).
· Remote access works perfectly when using VPN or when connecting via another mobile operator (2’nd).
· The issue persists only when using 1’s mobile network.

It looks like this is a network-level limitation from the operator, not a Plex-side issue. I’ve also opened a new ticket with 1’s operator to investigate on their side.

If you have any additional suggestions, I’m happy to try them. Otherwise, I’ll follow up with the operator.

Thanks again for your help! mobile network.

It looks like this is a network-level limitation from the operator, not a Plex-side issue. I’ve also opened a new ticket with 1’s operator to investigate on their side.

If you have any additional suggestions, I’m happy to try them. Otherwise, I’ll follow up with the operator.

Thanks again for your help!

9

Just a quick update — after the certificate reset by @BigWheel, I restarted my server and remote access is now working perfectly.

A huge thank you to @BigWheel. I really appreciate your assistance!

10

Hello!

I’ve exhausted all possible troubleshooting steps on my side, and the issue persists…:

  1. Network and Ports: Confirmed port 32400 is open and reachable via canyouseeme.org and ping.eu.

  2. ISP Check: My ISP conducted a full debug and confirmed they do not block Plex traffic, providing an official statement.

  3. Certificate Reset: I have deleted the cert-v2.p12 file from the Cache folder and restarted the server multiple times.

  4. Network Configuration: Disabled IPv6 on both the router and the NAS, set DNS to public servers (8.8.8.8), and confirmed no double NAT or CGNAT.

  5. Network Conflicts: Disabled UPnP on the router to ensure no port conflicts.

  6. Plex Network Settings: Set the network interface to eth0 (192.168.1.2) and the secure connection option to Preferred

Despite all these measures, the problem has not been resolved. Based on forum discussions, this appears to be a classic “stuck certificate” or “API rate limit exceeded (429)” issue that requires a reset on the Plex side.

I would be very grateful if you could clear the stuck certificate state for my server so it can obtain a new, valid one. Deleting cert-v2.p12 and restarting the server has not forced a new certificate to be issued.

Thank you for your time and assistance.

Best regards,
Vadim

11

it is reset @vadim_barkovskii

12

Thank you for resetting my server’s certificate previously. Unfortunately, it did not resolve the issue — the secure connection through app.plex.tv is still not working.

I continued troubleshooting and checked everything possible on my side. Here’s what I’ve done:

  1. Port 32400 confirmed open.
  2. ISP officially confirmed they do not block traffic.
  3. IPv6 disabled on both router and NAS.
  4. Public DNS set (8.8.8.8, 1.1.1.1).
  5. cert-v2.p12 deleted and Cache folder fully cleared.
  6. UPnP disabled.
  7. Router logs checked — no DNS Rebinding errors or plex.direct blocks found. The network is stable.

The issue is not on my local network or equipment.

Since even after the certificate reset the problem persists, and everything works fine over VPN, this strongly suggests that a “stuck” certificate request (API rate limit 429 error) still exists for my server on the Plex.tv side.

I kindly request that you check my server’s status once again and perform a forced certificate reset if needed. I am happy to provide any additional logs if required.

13

I know you provided server logs previously but can you get new ones from after I reset it.

14

@vadim_barkovskii
Make sure you turn off Verbose and restart your Plex server before grabbing the logs.

15

@BigWheel I have disabled verbose logging, restarted the server, and attached fresh logs as requested.

Plex Media Server Logs_2026-07-16_20-29-09.zip (3.1 MB)

16

Can you get the console logs from your browser when using app.plex.tv where it fails. I can’t see anything obvious in your server logs. ( you can message them to me directly as they likely have more sensitive info in them.)

17

Sent via private message.

18

[Log] [Connections] Testing all 2 connection(s) for Библиотека (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Servers] Found all servers = plex.tv (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Commands] Executing testServerConnection (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2, x2)

[Log] [Connections] Retrying connection tests for Библиотека in 18 seconds (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Retrying server events connection for Библиотека in 18 seconds (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Testing connection for Библиотека at https://79-111-12-13.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Testing connection for Библиотека at https://192-168-1-2.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Библиотека is unavailable at https://79-111-12-13.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (Status 0) (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Prevented fallback to insecure connection for Библиотека (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Библиотека is unavailable at https://192-168-1-2.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (Status 0) (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Prevented fallback to insecure connection for Библиотека (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] All connections to Библиотека failed (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Servers] Found all servers = plex.tv (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Testing all 2 connection(s) for Библиотека (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Servers] Found all servers = plex.tv (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Commands] Executing testServerConnection (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2, x2)

[Log] [Connections] Retrying connection tests for Библиотека in 20 seconds (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Retrying server events connection for Библиотека in 20 seconds (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Testing connection for Библиотека at https://79-111-12-13.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Connections] Testing connection for Библиотека at https://192-168-1-2.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Библиотека is unavailable at https://79-111-12-13.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (Status 0) (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Prevented fallback to insecure connection for Библиотека (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Библиотека is unavailable at https://192-168-1-2.d4b21a3bc0684818b28b8999ac3a38a1.plex.direct:32400/media/providers (Status 0) (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] Prevented fallback to insecure connection for Библиотека (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Warning] [Connections] All connections to Библиотека failed (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

[Log] [Servers] Found all servers = plex.tv (9054-9054-983eec1ac3d26e353d6b-plex-4.160.0-75ddd7b.js, line 2)

19

Did I send something wrong?

20

Sorry i have been mostly away for the past few days. That is the correct thing. I was hoping it would have more info. That is the correct cert ID you currently have. So i don’t think this is a cert issue.

Do you mean your server Synology is on a VPN or the computer you are trying to access it from?