Spoke to soon. I switched to the official container and now I am good. I used Binhex’s container, have for years with no issues.
Not sure if this will work for you since I didn’t use docker on my NAS but this is what I did:
- I uninstalled PMS via Package Centre and it asked if I wanted to keep all my settings for a future reinstall so I chose that option.
- Reinstalled the latest version of PMS from Plex site.
- It asked if I wanted to use a claim code to reclaim a server (it includes a link to get the code)
- entered the code and clicked next. Everything worked after that.
Hope that helps you. If not you then anyone else that has the same problem I did.
Not sure if this will work for you since I used a Synology NAS but this is what I did:
-
I uninstalled PMS via Package Centre and it asked if I wanted to keep all my settings for a future reinstall so I chose that option.
-
Reinstalled the latest version of PMS from Plex site.
-
It asked if I wanted to use a claim code to reclaim a server (it includes a link to get the code)
-
entered the code and clicked next. Everything worked after that.
Hope that helps you. If not you then anyone else that has the same problem I did.
@forynee My bad, should have clarified, I am on Unraid. I did not think that the container would make a difference so I have been troubleshooting using the same container, who new! Appreciate the response!
This worked for me! Thank you - deleting the entire entry (not just the value) is what finally worked for me.
I modified the script mentioned to work for Unraid in case it helps anyone.
- The original script: ChuckPa/UserCredentialReset
- My fork
The original didn’t work for me so I added a conditional that looks for the directory I have Plex installed in. If yours is slightly different you can change it but you’ll recognize the /mnt/user/appdata
bit if you’re an Unraid user.
This seemed to work for me:
- Run script with a fresh claim code:
./script.sh claim-blahblahblah
- Go to HTTPS address (I used https://my-local-ip.hash.plex.direct:32400 - maybe https://app.plex.tv works too). This forced it to renew the cert and then the libraries showed up again.
I’m using Binhex-Plex docker, in my Preferences.xml file I don’t have PLEX_CLAIM variable. Is it advised to create one in Preferences.xml, or create the variable in the docker settings, or both? Thank you, inching forward to resolving this issue
I’m running Plex on a QNAP system and thought I’d share the solution that worked for me.
I tried a ton of solutions from all over the forums and couldn’t get my server to come back online. Logging into Plex was fine: I could see servers that were shared with me and play music and video files without any issues; well, the issue was that I couldn’t play my own media.
- I stopped Plex Media Server on QNAP
- Made a copy of the Preferences.xml in case there were any further issues
- Deleted the Preferences.xml file from the Plex Media Server folder
- Started Plex Media Server on QNAP
After a few minutes, I was able to connect to Plex through my local IP and port 32400 (example: 10.x.x.x:32400) and I was met with the “welcome to Plex” screen. All of the libraries were already listed with the friendly name of my server from before.
When the interface came up, there was still an issue of the server not connecting. I left it for about half and hour and then I stopped PMS in. QNAP again and then started it again a few minutes later.
Everything is working fine now.
I did a an “Empty Trash”, “Clean Bundles”, and “Optimize Database” just in case. I then had to re-pin all of the libraries I wanted quick access to,
Not an ideal solution, but it worked for me.
Thanks to all the posts here and in other forums for allowing me to inch closer to this solution.
To answer my own question, I did steps 1,3,4.
For step 2, I had to run terminal from unraid and use nano to edit the xml file as krusader didn’t have access it.
Instead of step 5, I ran the following command in terminal from unraid and I seem to have access back. Good luck yall.
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'
F you! im uninstalling that ■■■■! Gonna use jellyfin for my music stuff