Error Acquiring Certificate after Password Reset

[skam]

yep im not taking more than 1 minute to enter it and start plex again. still shows up as Not Authoriszed You do not have access to this server

[skam]

the new claimid also shows in the docker settings when viewing it via portainer. so appears to startup ok with the correct claimid

[gazmeist]

Did you change your Preferences.xml first?

@ChuckPa

Second Choice (hard reset) is what you want.

When server and device credentials are out of sync.

Use this procedure when:

1. You receive the nasty “No Soup For You” message
2. You’ve changed your Plex password and now have trouble accessing something.
3. You’ve cloned the server or performed a ‘backup & restore’ using the procedures above but now cannot access the server.

First choice - Preferences.xml missing or deleted.

If something happened to “Preferences.xml” and you need to claim the server again, with everything being normal, Start here first.

Begin here:

1. Sign out the plex/web browser
2. Open a new Window
3. Go to to www.plex.tv (not app.plex.tv)
4. Sign into your account settings.
5. Force sign out everything as you change the password.
6. Open an incognito window
7. Open http://ip.addr.of.host:32400/web (or 127.0.0.1:32400/web if on the host)
8. Sign in
9. Claim it again.

The X-Plex-Token (PlexOnlineToken) and other credentials will now all resync
go to your devices and sign them in again.

Second choice - After a hard password reset on plex.tv

If you’ve changed your password on Plex.tv, and things didn’t go well afterwards …

There is a similar method for other hosts:

On the server computer

1. Open a Terminal window / SSH into the machine / get into the container ,
   (whichever case applies)
2. Stop Plex
3. Edit Preferences.xml
   (Use the Linux text editor on the host itself.)
4. Carefully remove the following Name="Value" pairs
   – PlexOnlineName
   – PlexOnlineToken
   – PlexOnlineMail
   – PlexOnlineHome (if it exists)
5. Save the file
6. Start Plex
7. Keep the terminal window open. You will need it again momentarily.

On your computer

1. Open Claim | Plex
2. COPY the token given into your browser

Switch back to the Terminal session window

1. On the command line (where the server is), type:

curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=PASTE_TOKEN_HERE'

2. Hit Enter.
3. Wait 15-20 seconds for Curl / PMS to talk to Plex.tv and setup new credentials.

As confirmation, the curl statement will look like this:

curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'

Confirming success.

You will be able to confirm the server is properly reclaimed and credentials are in sync when, after executing the curl statement, it responds with a stream of XML which ends in </MyPlex>

If this doesn’t work, grab the logs (ZIP/tar.gz) and let me see them please.

[chr1s13]

@ChuckPa Can you reset my plex server cert? as I’m just having issue with the secure connection and I can see error acquring new cert in log

Friendly Name: svr1
OS: ubuntu

[skam]

Thanks for this. I had done this step earlier (before the certificate was reset) but hadn’t done it again after it was reset. I stopped plex container, cleared out below settings,

– PlexOnlineName
– PlexOnlineToken
– PlexOnlineMail
– PlexOnlineHome (if it exists)

grabbed a new claim ID and updated in yml file and re did docker-compose and im back

thanks everyone for their help. good luck everybody

[rmc2000]

@skam Really glad to see you are back up and running! Following this thread is wild.

[rmc2000]

@ChuckPa Hopefully not being a pain, just mentioning again because I have no clue how you are keeping track of this thread! Your head must be on a swivel, appreciate any help you can give.

[david_butlerii_yahoo_com]

Chuck,

All seemed to work out… all running good. Thanks for your help!!

[ChuckPa]

@rmc2000

My head is spinning around in multiple threads like a bad horror movie.

My hair looks like it too

I reset your certificate

I’m waiting for it to generate before giving you the GO

EDIT:

Still not generated yet.
It might be overloaded again.

Give it a shot. Be patient before opening (2-3 minutes)

[rmc2000]

@ChuckPa Looks like that did the trick! Is there anything I can do to assist? Buy the team a round? Genuine offer; you are all handling this so much better than any other company that has suffered exposure like this.

[ChuckPa]

If you want to share thoughts with the team, please feel free to share them through the www.plex.tv web page (at the bottom).

There is a contact form.

[gazmeist]

Presume that’s the same as the Contact link at the bottom of this forum too

Contact | Plex

[dkerstjens]

Was password reset required ? yes
Has the password been changed ? yes
Were all devices signed out (check the box when changing password) ? yes
If all the above is complete, Please provide
– Name of the server (friendly name)
NASEE9714
– Host OS it runs on (to confirm we have the correct server)
QNAP

[ChuckPa]

@dkerstjens

We have a QNAP thread …

Please head over there.

Cannot access QNAP Plex Since resetting password

On QNAP, we need to do a manual reset in two steps. Setup access via FileStation Restart Plex one time (to populate the PlexData share) then stop Plex Navigate (Using FileStation) PlexData/Plex Media Server Install the Text Editor app from the App Center (if not already installed) In FileStation, right click Preferences.xml → Open with Text Editor Carefully, remove 4 preferences from the file Each preference consists of the Name="Some_Value_here" PlexOnlineUserna…

[dkerstjens]

Sorry chuck! Please disregard - got it sorted! Thanks for everything

[Micma99]

Think my thread got overlooked, think I need reset on my remote server. Thread here: Lost remote server after password reset

[ChuckPa]

@Micma99

Responded in your thread

[Dmi3Ger]

Dear,

I would also like to be put in the queue to fix my cert. After the password reset I had problems with access to my server. I fixed these. Remote access supposedly works (see screenshot).

I can access the server via the Plex app for Windows and PlexAmp. However, I can’t access the server on app.plex.tv. I see following error in the local console:

Aug 25, 2022 09:59:08.714 [0x7f0797a48b00] Error — [Req#e8] 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>

Aug 25, 2022 09:59:14.148 [0x7f0799d8fb00] Error — Unknown metadata type: 
Aug 25, 2022 10:01:11.267 [0x7f0795cbdb00] Error — [Req#e8] CERT: Error acquiring new certificate: Failed to retrieve cert from plex.tv: 429, 

To answer the requested questions:

1. Yes, a password reset was required
2. Yes, the password has changed
3. Yes, all devices were signed out
4. Server name NAD, OS DSM7.1

I also want to add that http://127.0.0.1/identity does not work (ERR_CONNECTION_REFUSED).

Thank you for your help in advance.

[RdV]

• Edit: Fixed. Thanks!

Really sorry to bother you ChuckPa, but I keep getting

CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>
<
1. Was password reset required ? → YES
2. Has the password been changed ? → YES
3. Were all devices signed out (check the box when changing password) ? → YES
If all the above is complete, Please provide
– Name of the server (friendly name) → —
– Host OS it runs on (to confirm we have the correct server. → Docker Container (LinuxServer.io) Linux 5.15.0-46-generic

Thank you very much in advance!

[calvin4000]

One more, sorry… @dane22

1. Was password reset required ? → YES
2. Has the password been changed ? → YES
3. Were all devices signed out (check the box when changing password) ? → YES

If all the above is complete, Please provide
– Name of the server (friendly name) → MyPlex
– Host OS it runs on (to confirm we have the correct server. → MacOS Monterey 12.0.1

Re-Claim the server was ok

Thanks guys

Log:

Aug 25, 2022 11:19:44.795 [0x70000711b000] ERROR - CERT: Error acquiring new certificate: Failed to upload CSR: 429, <?xml version="1.0" encoding="UTF-8"?>