Server Version#: 1.23.2.4625-a83d2d0f9
Player Version#: 1.31.1.2262-74fdc6b7
Today I upgraded to server version 1.31.1.2262-74fdc6b7 of Plex Windows Server.
Plex never recovered and so I had to shut down and restart the application.
When I started back up my server is now listed twice with the version that I was previously using that had all my home menus and remote access setup saying it’s Unavailable. The second instance of my server is available and “Nearby”, but without my home menus or remote access setup.
Can anyone advise what I need to do to fix this issue and restore my original server connection?
I am running my server local on Windows 10 and everything was fine until I did the Plex server upgrade. I have this issue regardless of client application that is accessing the server.
I have the exact same problem. Installed the upgrade .4625 and it created a new server, moved all my libraries to the new server, and my old server is unavailable. Everything that i use Plex with is screwed, including for the people i share my libraries with, since they are all referred to the old server which is unavailable.
I really wish someone from Plex would chime in…
I have the same issue I believe. Plex server said it has an update ready. I updated, Plex would not reconnect. Reboot, and launching Plex server behaves as if it was never installed and tries to run me through the first-time setup steps. HALP.
EDIT: Checked and this is also the upgrade to .4625, and I have the exact same results as the users above.
Not sure if you got my email (I ended up sending twice because I got an “unknown address” the first time). I tried what you recommended after you reviewed my logs.
You had asked if I was still running 1.23.2.4625 (I was) and if so, to try updating the value for ProcessMachineIdentifier, which I did.
The result of this was as follows after I changed the value you provided to lower case:
The administrator account does now remember my pinned favorites, but the server is still listed twice with the second one showing unavailable (prior to the XML change it was the first that showed as not available).
Friend shares continue to show their pinned favorites as unavailable even though the administrator account shows the friend’s access is granted to the server’s content.
It seems what you provided partially worked, but maybe there is another setting that also needs to be corrected?
