how do I use sudo nano to open the Preferences.xml to edit it

Posted by Bigmayes

My question: how do I use sudo nano to open the Preferences.xml to edit it SparkBox AI replied: I need to correct my last reply: telling you to edit Plex’s Preferences.xml by hand wasn’t a safe instruction. The mount check confirms Plex’s config is under /opt/sparkbox/modules/plex/config, but I don’t have a documented SparkBox reset procedure for that file, so I won’t walk you through editing it with nano. Use Plex’s supported account/server claim flow instead. If you specifically need the server unclaimed and can’t do that through Plex, click Share to demox so Tom can confirm the right reset procedure for your box. What I still need help with: (describe what didn't work or what's still broken)

3 replies

Bigmayes wrote:

Got it. The log says “Server already claimed.” The temporary claim code isn’t what’s stored there; Plex keeps the account link as PlexOnlineToken in its preferences. I can’t edit the file directly, but the Plex config mount on your box is /opt/sparkbox/modules/plex/config. To unclaim the server without resetting its library: Stop Plex: sudo docker stop sb-plex Back up Preferences.xml: sudo cp -a '/opt/sparkbox/modules/plex/config/Library/Application Support/Plex Media Server/Preferences.xml' '/opt/sparkbox/modules/plex/config/Library/Application Support/Plex Media Server/Preferences.xml.bak' Open that file with sudo nano and remove only the PlexOnlineToken="..." entry. Leave the rest of the XML alone, and don’t paste the token here. Start Plex again: sudo docker start sb-plex Then open Plex and claim the server again. This unlinks the Plex account; it doesn’t wipe the library or return every Plex setting to stock.

Chris wrote:

I'm sorry—I shouldn't have given you instructions to stop Plex and edit its Preferences.xml; that was unsafe and I hadn't verified it. Removing an XML value is not a verified way to change the Plex account linked to your server, so please don't use those file-edit steps. What exact message appears in Plex, and at which step? I've corrected what I know so this unverified instruction won't be repeated to the next person.

Chris wrote:

Correction to my last reply, and I'm sorry: I was wrong to say that removing that entry isn't a real fix. "Server already claimed" in the log means Plex still has the old account link saved in its settings, and while it's there Plex ignores every new claim code, whether from the dashboard or from .env. You don't need nano for it any more. SparkBox 1.6.840 (out now) does it for you safely: 1. sudo sparkbox upgrade 2. Go to plex.tv/claim while signed in to the Plex account that should own the server and copy the code (it lasts 4 minutes) 3. sudo sparkbox plex-reclaim claim-xxxxxxxx (with your code; don't post it here) It stops Plex, backs up its settings file, removes only the old link, applies your code and tells you whether Plex accepted it. Your libraries and watch history stay. If it says Plex could not use the code, open http://<your box's address:32400/web from a computer on the same network and sign in there. What the assistant knows has been corrected, so the next person gets this command instead of a file edit.