Plex server not working yet again - it ALWAYS breaks!

Server Version#:
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

This plex server was created years ago on a linux server with help from here, I don’t know the first thing about getting you logs or fixing it.

But I am BEYOND frustrated at this point - help from here has only led to yet another broken piece of crap!

I need good help.

Someone help me get this thing to work!

Sick and tired of this - why can’t anyone make anything that actually works right?

It seems that for whatever reason, Plex randomly decides to trash itself at times and completely stop working on my server.

And multiple times now, I’ve had to fix it by rerunning a script that was created for me that builds it.

Here’s an excerpt of a thread with the instructions to run the script I have:

  1. Open the file in Nano
cd /root
nano make-plexomv
  1. Cursor over to where claim- begins , get ready to paste a new token in there.
  2. Browser window - https://plex.tv/claim
  3. COPY the token
  4. Come back to the nano window & PASTE (overwriting the token there)
  5. SAVE the file
  6. Run the script ./make-plexomv
  7. Let it whirl about as it deletes the old test container and recreates it from scratch
  8. When that finishes, open http://ip.addr.of.omv:32400/web
  9. see the ‘Got it’ (might take a second to start up) and click it.
  10. Define a library section.

Except - now when I run it, after step 9, I don’t have a “got it”, I have my server, and my content working again.

Is this the intended design of Plex - have it be an unstable piece of crap that stops working without warning at random times like a timebomb, that you then have to go in and run scripts to re-create it? If so, that’s a piss poor design.

Would love to get these problems fixed - I’ve only been complaining about them for years now!

I have PMS in a ProxMox VM.
Most times it behaves.

I, just now, upgraded it to latest and it lost the PlexOnlineToken (the value is null).

Null tokens is a known problem (race condition) we can’t track down yet.

  1. It reads the token when it starts
  2. It uses the token
  3. At next Preferences.xml update – it writes a NULL token. :man_facepalming:

Anyway, I have one way to deal with this rather than cutting/pasting in Preferences.xml or other stuff.

I use it this way:

chuck@buntu22:~$ sudo ./UserCredentialReset.sh 
 
          Plex Media Server user credential reset and reclaim tool (Ubuntu 22.04.3 LTS)
 
This utility will reset the server's credentials.
It will next reclaim the server for you using a Plex Claim token you provide from https://plex.tv/claim
 
Please enter Plex Claim Token copied from http://plex.tv/claim : claim-XXsQxpzj6H7n8GsMzD7N
Clearing Preferences.xml
Getting new credentials from Plex.tv
Claim completed without errors.
 Username: ChuckPA
 Email:    ChuckIsCrazy@loonies.com
 
Complete.  You may now start PMS.
chuck@buntu22:~$ sudo systsemctl start plexmediaserver
chuck@buntu22:~$

There is a -p "/full/pathname/to/Preferences.xml" option so you can use it inside or outside containers. -p is “manual mode” where it trusts you’re giving it a valid file.

See if this helps ?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.