Hm – sorry, @OttoKerner, a follow-up: the server now populates a “Claim This Server” warning, but if I claim the server, the problem of not connecting to the DB reverts to the earlier issue of saying I don’t have permission to connect to Plex2 (the old name of the computer).
I’ve dismissed the “claim server” notice for now – is it truly important, and is there a fix for this?
Sure, Chuck – I backed up, then restored, the entire contents of /var/lib/plexmediaserver/Library/Application Support/Plex Media Server.
It’s slooooowwwlyyy scanning all the files (there’s about 2TB of stuff, mostly music), and the music etc. seems to be playing fine. It’s just the Claim This Server warning that seems to disconnect me from the database when I tried it (once – now I’m waiting for the scan to finish before trying again, which may take a couple of hours).
So I think I’ve done all of that but not in that order, due to having run the reinstall before knowing I had to remove the old server name from authorized devices.
Steps were:
Stopping PMS
sudo sh
cd /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/
rm -rf *
tar xf /media/plex/EXTBKUP/PlexLibrary.tar.gz
cd /var/lib/plexmediaserver
chown -R plex:plex .
Start PMS
Log into Plex
Remove server name from authorized devices
Re-map media folders in Plex
Waiting for the scan to finish…
The “Claiming” issues have happened while I’m waiting for the scan…
“Claim Server” notice
Click, login, claim server
Back to Plex – now says it can’t connect to Plex2 (old computer name)
Remove server name from authorized sources
Plex now working again, but claim server notice is back
I’m really not sure what happened. The old computer was called “plex2” and I’ve named the new install “plex,” and all the issues seem to be coming from the authentication tokens @OttoKerner referred to above.
IP and subnet are the same as before I reinstalled Ubuntu.
No, haven’t touched Preferences.xml. The only difference between two days ago and now, that I can think of, is that the computer used to be called “plex2” and is now called “plex”.
If I try “Claim Server” in the Plex server settings, it spins, then presents “Claim Server” again as though I hadn’t done anything.
Then, if i refresh the app.plex.tv page, a server DOES appear (named Plex).
But when I return to my Plex server, it once again shows “plex2 - unreachable” in my home screen, and “No soup for you! You do not have access to this server” if I click on any particular library.
If I return to app.plex.tv and DELETE the server from the Authorized Devices, my Plex server display returns to normal and connects to its database again.
I’m not entirely sure what that means, but yes, it’s running on an old Optiplex 990 in the corner of my office, a standalone machine that’s not used as anything but the Plex server and some simple home filesharing through Samba. Its IP is 192.168.1.113.
I’m running the Plex server on the previously mentioned Optiplex 990, whose address is 192.168.1.113. That’s the only computer I’m concerned with at the moment. There are no other computers in the mix. I have the server running (localhost:32400) in one tab in Firefox and apps.plex.tv in another tab. This conversation is in a third tab.