Plex Employee to Reset Server Certificate? "API rate limit exceeded" error

[CFarence]

Appreciate your and the teams assistance, moved back up and it started up without issue.

[vytux86]

Good evening, @ChuckPa

looks like i am having pretty similar issues with 1.32 failing to update cert. Could it be reset from plex.tv side?

1.31 container starts up just fine with old cert file and is accessible from plex.tv

Apr 18, 2023 21:32:51.345 [0x7fd7f9cd6b38] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
  <error code="1003" message="API rate limit exceeded" status="429"/>
</errors>

[ChuckPa]

@vytux86

Are you using your own certificate ??

Linux Tips

OpenSSL v3.0.0 and PMS. For those using their own domains and certificates with PMS , PMS 1.32.0.6865 and above updates OpenSSL from v1.1.1 to v3.0.0 . (changed the numbering scheme in the process) The consequence of this is OpenSSL v3 removed several “less secure” encryption methods. The impact on you, if you’re using an older distributions where openssl v3 is not the default, if not already doing so, you will need pay special attention to how your certificates are generated As example…

[vytux86]

@ChuckPa

Not as i know. Todays log after deleting old cert:

Apr 20, 2023 10:31:38.777 [0x7f9212e6eb38] DEBUG - CERT: Certificate did not exist, fetching a new one.
Apr 20, 2023 10:31:38.777 [0x7f9212e6eb38] DEBUG - [HCl#17] HTTP requesting GET https://plex.tv/api/v2/devices/fdf0c10410a9170698cee8153c660b48a3dbe573/certificate/subject

Apr 20, 2023 10:31:39.314 [0x7f9214eb2b38] DEBUG - [HttpClient/HCl#1c] HTTP/2.0 (0.1s) 429 response from PUT https://plex.tv/api/v2/devices/fdf0c10410a9170698cee8153c660b48a3dbe573/certificate/csr?reason=missing&invalidIn=0 (reused)
Apr 20, 2023 10:31:39.314 [0x7f9212e6eb38] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
  <error code="1003" message="API rate limit exceeded" status="429"/>
</errors>

Should i share the whole log dump?

[ngsteinberger]

I seem to be having the same issue I think. Any way for you to check mine too? @ChuckPa
Plex Media Server Logs_2023-04-20_10-01-03.zip (3.2 MB)

[ChuckPa]

@vytux86

I’ve reset your certificate. it was a mess.

If you don’t get success this time when restarting, downgrade to PMS 1.31 and wait for them to unscrew the mess

[ChuckPa]

@ngsteinberger

Fix your “Allowed Networks” value.

Apr 20, 2023 09:43:25.997 [2648] ERROR - Error parsing allowedNetworks ‘192.168.1.2\00100’: Invalid Netmask 100
Apr 20, 2023 09:43:25.997 [0496] DEBUG - Request: [127.0.0.1:55281 (Loopback)] PUT /updater/check (2 live) #1 GZIP Token ()

Restart the server,

See if that improves it.

If not, we will turn on VERBOSE logging and restart one last time
(So I can drop it on Engineering)

[ngsteinberger]

Ok, I fixed allowed networks and restarted the server. It is 192.168.1.2/24 (which I think it was set to before I started trying to troubleshooting this issue by changing random settings). My remote access is still not working. All of this randomly broke last night, so I’m still unsure what exactly changed.

My main problem originally was an error saying something about secure connections which ultimately led me to this thread.

This is what I’m getting now. @ChuckPa

Edit:

[ChuckPa]

Limited Connection is your network.
That’s not Plex.

Check Firewalls.

Let me see the updated logs. (about app.plex.tv)

[vytux86]

@ChuckPa

Thank you for the reset. Indeed i do not get any errror in regars of API rate limit exceeded. And the previous PUT returns with http 204 , which i guess is good.

Still no public access with 1.32 so I have rolled back to 1.31 for now ( which works well )

Cheers mate!

[ChuckPa]

@vytux86

Still no public access with 1.32 so I have rolled back to 1.31 for now ( which works well )

Are you using your own certificate for that public access?

If so, you need to update how your certificate is created for PMS
This is the single biggest change in 1.32.0

Linux Tips

OpenSSL v3.0.0 and PMS. For those using their own domains and certificates with PMS , PMS 1.32.0.6865 and above updates OpenSSL from v1.1.1 to v3.0.0 . (changed the numbering scheme in the process) The consequence of this is OpenSSL v3 removed several “less secure” encryption methods. The impact on you, if you’re using an older distributions where openssl v3 is not the default, if not already doing so, you will need pay special attention to how your certificates are generated As example…

[ChuckPa]

“Limited Connection” occurs when the client (Plex/web or any other Plex player) cannot open a direct connection to your server and must route through plex.tv (which PMS is always connected to).

If the client cannot connect to your server, the most common cause is Firewall.

You’re running windows, which I barely remember but, the most common cause for this type ‘but i didn’t touch anything’ failure is a software update which changed settings on you. (I would loathe those)

Check all the firewall ports in your firewall app

https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/

[xXCrazy_SoloXx]

Hello,

I have the same issue with Plex installed on my Shield Pro, I can’t access it to the web app because of « connection not secured », could you please reset my Plex server certificate?
Thanks a lot in advanced.

[BigWheel]

@xXCrazy_SoloXx are you still having the issue? currently the cert on your server looks fine and appears to have been just updated today

[xXCrazy_SoloXx]

Hello,

Thank you for your response.

I had to reset (factory reset) my Shield pro and reinstall several times Plex and Plex Server to run it properly (Plex server stopped for no reason a few times).
It’s seems to be ok since… today.

For the moment Plex is scanning my NAS but the connection is not secured at all (Firefox or chrome issue??), I can only access it directly through its IP address.

I’ll keep you informed if it’s stops running.

Thx

[chrisbuck919]

Hi,

I’m having the same issue on my Nvidia shield. Have tried resetting the shield and deleting the plex media server data etc. On plex.tv it can can see the server but can’t connect. No issues connecting to the nas using vlc. Please could someone reset my server certificate to see if that fixes the problem? Thanks in advance.

[kaeincan]

Can you check my certificate as well – having the SSL certificate problem suddenly. No changes in static IP, and the port is manually forwarded.

@ChuckPa @BigWheel

[ChuckPa]

@kaeincan

Your certificate was stuck “Generating”.
I reset it.

It’s now ready to use.

Restart the server and all players.

[kaeincan]

Thank you! Working like a charm.

[LemonIcedTea]

@ChuckPa or @BigWheel: Would you be able to help me check what’s happening with my Plex Server and help to reset my rate limit? I see the following in my logs:

Jul 05, 2023 00:42:22.760 [140486974094136] DEBUG - [HttpClient/HCl#1b] HTTP/2.0 (0.2s) 200 response from GET https://plex.tv/api/v2/devices/fb119d6b519255400af97f0abbfe57d38d7d257f/certificate/subject (reused)
Jul 05, 2023 00:42:22.972 [140486920969016] DEBUG - [HCl#20] HTTP requesting PUT https://plex.tv/api/v2/devices/fb119d6b519255400af97f0abbfe57d38d7d257f/certificate/csr?reason=missing&invalidIn=0
Jul 05, 2023 00:42:23.184 [140486974094136] DEBUG - [HttpClient/HCl#20] HTTP/2.0 (0.2s) 429 response from PUT https://plex.tv/api/v2/devices/fb119d6b519255400af97f0abbfe57d38d7d257f/certificate/csr?reason=missing&invalidIn=0 (reused)
Jul 05, 2023 00:42:23.185 [140486920969016] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<errors>
  <error code="1003" message="API rate limit exceeded" status="429"/>
</errors>

I noticed that my previous connectivity tests for remote access were failing due to an expired cert, so I removed the cert from the cache.