QNAP certificate missing — CSR request returns 429 — backend reset requested

Plex Media Server Remote Access
1

Hello,

Could a Plex team member please reset the certificate/CSR state for my Plex Media Server?

Platform: QNAP, native Plex QPKG manually installed from the Plex website
Plex Media Server version: 1.43.3.10828-00f62d37d
Secure Connections: Preferred
Strict TLS configuration: Disabled
Server status: Claimed and signed in
Remote Access: Fully accessible outside my network

Clients that permit insecure connections can access the server, but clients that require secure connections report it as unavailable.

The active Plex data directory does not contain Cache/cert-v2.p12.

When Plex starts or when Remote Access is disabled and re-enabled, the certificate request fails with:

CERT: Certificate did not exist, fetching a new one.
HTTP 200 response from GET /certificate/subject
HTTP 429 response from PUT /certificate/csr?reason=missing&invalidIn=0
CERT: Error acquiring new certificate: Failed to upload CSR: 429
API rate limit exceeded

I have already:

  • verified the QNAP system time and NTP synchronization;

  • changed my Plex account password;

  • signed out all connected devices;

  • enabled two-factor authentication;

  • reclaimed the server;

  • confirmed that the server is claimed and authenticated;

  • confirmed that Plex can communicate with servers.plex.tv;

  • confirmed that no custom certificate is configured;

  • disabled and re-enabled Remote Access;

  • confirmed that port forwarding and direct remote access are working;

  • confirmed that no certificate is currently presented on port 32400.

I can provide additional logs or server details privately if required.

Could you please reset the certificate/CSR state for this server on the Plex backend?

Thank you.

2

Please stop and restart the Plex server now.

3

Thank you very much. The reset fixed the issue immediately, and my devices can now connect securely again.

I had been trying to identify this problem on and off for several months, so I’m very relieved to finally have it resolved. The missing certificate and CSR 429 error were not obvious from the client side.

Thank you again for your help.