see the ‘Got it’ (might take a second to start up) and click it.
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.
It reads the token when it starts
It uses the token
At next Preferences.xml update – it writes a NULL token.
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.