I have a desktop server and Synology NAS 6.4. I followed the instructions on editing the registry in Windows. Lo and behold, I was able to reconnect that server. I then followed the instructions to edit the preferences.xml in Synology (first making a back up of that just in case). It did not even see the server (as was the case after changing my password) even after editing the preferences file. One curious point I’d like input on. Here were the Linux instructions:
- In your text editor, remove the following attribute/key pairs from the
Preferences.xml file:
PlexOnlineHome="1"PlexOnlineMail="jane@example.com"PlexOnlineToken="RanDoMHexIDecIALtoKeNheRE"PlexOnlineUsername="ExampleUser"
On the PlexOnlineToken line in my preferences it only shows this:
PlexOnlineToken=" "
There was nothing like the content they show an example of. Should I not delete the Token line?
And I was unsure on spacing when deleting the items in the Text Editor. It’s not like Windows where it was much simpler - and obvious - as to the files I was deleting in the registry.
Can someone comment on what I should do? I thought I wouldn’t have to get a new certificate (which I’ve not yet tried to do - it’s just one of the many suggestions on these forums related to this ridiculous password change fiasco).
Any help would be appreciate.
Oh, and one more point; I’m supposed to delete the whole line for each?
For example, delete PlexOnLineHome=“1”? Or just “1”?
And to that point, in my preferences file there is a “0” after PlexOnLineHome.
Thoughts please?
Sorry, one more query, can anyone confirm;
- Proper editing and removal of preferences.xml as I showed. What exactly stays/goes?
- Do I need a new certificate? If so, would someone please put simple steps down as to how to do that. I have browsed to "package center/plex - then settings / certificate tab. I already have a Plex certificate (and Synology one). Do I import a new Plex certificate? And where do I get that again? I just import and replace the existing one? If not, please confirm.
Thank you.
My problem was perhaps more complex than most since my PMS was on a remote server and I was unable to access the PMS home screen over an SSN Tunnel. Fortunately the hosting company created a script to fix it. Once I found the script, it was up and running again in minutes, but it was hours of frustration before discovering the script. Also my local Nvidia Shield is running again though it took numerous tries to get connected.
I am very disappointed with how the Plex staff handled this situation. Hopefully they will anticipate the problems that so many people experienced and include more detailed instructions when they send a batch email forcing everyone to change their password next time. Better yet, they should develop an easier way to reconnect to servers after a password change.
This worked for me, thanks!
