Plex Media Server play musical chairs

Server Version#:(1.42.2.10156-f737b826c-x86_64) & (1.42.2.10156-f737b826c-x86_64_DSM7)
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I have been having problems with my Plex Media Servers every since the emails went out to change the user password.
I have 5 different Plex Media Servers which consist of Qnaps (1.42.2.10156-f737b826c-x86_64), Synology (1.42.2.10156-f737b826c-x86_64_DSM7), & Nvidia Shields (currently disconnected). When I claimed one or two servers I’m ok but when I claim a third server then server #1 or server #2 disappears. It was as if the servers were playing musical chairs no matter which servers were claimed.
Then I found this Tip on the board-
Q30: How to reset ownership and reclaim your Plex server on QNAP

  1. Create a shared folder, named “PlexData” (exact capitalization)
  2. Restart Plex
  3. Let it run for 30 seconds then stop it
  4. Install the QNAP “Text Editor” app from App Center if not already installed
  5. Using FileStation, Open PlexData → Plex Media Server (click into it)
  6. Right-click Preferences.xml → Open in Text Editor
  7. Carefully remove the PreferenceName=“Value” pairs for
    • PlexOnlineUsername
    • PlexOnlineToken
    • PlexOnlineMail
    • PlexOnlineHome (This might not exist . OK if it doesn’t)
  8. SAVE the file
  9. Start Plex
  10. Open http://ip.addr.of.QNAP:32400/web from your computer
  11. The server will now be in the state for you to CLAIM it again.
    The instructions above did allow me to claim all the servers and get them to work under my account. However, after a few days I could only see two or three servers under my account. Now I’m back to the musical chair of servers. I have attempted to use the Putty method of claiming the servers but can’t figure it out because it’s over my technical level.
    After months of unclaiming all servers and reclaiming all 5 servers, I don’t know if there’s something I’m missing or something wrong with my account.
    Also, I have enabled Enable Plex Media Server debug logging but the Plex Web Debug Level will change from Enabled to Disabled after I have saved the Dubug Level for each IP Address on a server; so I not sure if the Plex Media Server debug logging is working properly with the Debug Log changing to disabled.

I’m not very familiar with plex on these systems but how are you claiming the server? Are you using the claim token method? If so, you need a new token for each server. If you use the same token, that would explain the musical chair effect.

@dmohead My first guess would be that you copied the servers from one device to another and included the machineidentifier which duplicated the server. Plex can only have one device per ID.

This is the symptom of duplicated ID fields in Preferences.xml
(Copying/cloning a server without deleting Preferences.xml before starting)

  1. On the QNAP (The 3rd server ?), with Plex stopped, Using the QNAP Text Editor, open Preferences.xml

  2. remove MachineIdentifier="value", ProcessedMachineIdentifier="value", and AnonymousMachineIdentifier="value"

  3. Save Preferences.xml

  4. Presuming they all have different Friendly names, When you start this server, it will be visible by the friendly name but will now have a distinct ID.

Repeat this using the Synology Text Editor if needed for the Syno.

This should resolve the issue because PMS will create these three field values fresh when it starts and , using the claiming info already there, claim it for you.

Be careful and make certain each server is stabilized with their new IDs before starting the one which will retain the original ID fields.

After you’re all done, go to https://app.plex.tv/desktop/#!/settings/devices/pms

Clean up and phantom server entries which may linger

I’m not sure about your statement that each server have new IDs but each server has a different value for the MachineIdentifier, ProcessedMachineIdentifier, and AnonymousMachineIdentifier. I did remove each value then checked them among each server value data.

I’m still having problems with my servers appearing/staying on my account at the same time. I was able to get three of the servers to appear on the account at the same time but in time they started the musical chairs bit again.

My servers (two Qnaps & a Synology) have two different IP Address which means I have a total of six IP Address between these servers. I thought my setup may be causing these issues because I have two ethernet connections coming from each server then going into a network switch but this setup has been the same for about 2 years.

These are examples of the type of issues I have ran into.

Take Plex Media server #1 which is a Qnap the first IP Address will show the account with a Qnap server and a Synology server. However, if I use the Qnap’s second IP Address it may only show that Qnap server on the account.

Another example would be using server #2 which is also a Qnap, the first IP Address will show both Qnap servers (#1 server & #2 server). However, the second IP Address would show Qnap server #2 and the Synology server (Synology replaced server #1).

I’m also having problems with sharing these servers. Sometimes when I have the PMS problems, I see all my share friends listed with their access folders and then there are times where all share friends disappear. On occasion I have refreshed the page and one or two friends appear with library access. Then I contact the friend and they see the server but it has the orange triangle which won’t allow them to access the server. After the friend logs out and back in they have been able to access one server in one hour then the lose it just to get access to another server.

Nothing makes sense as to why accounts or servers appear or not appear.

Each of the servers have a different Friendly Names and I have tried the instructions provided but I still have the same issues.

@dmohead

Looked at your account again.

I see that the DS418 and the TS451 both are published to port 32400.

When you have multiple servers on your WAN IP, they must have different external ports.

Is this problem only occurring when using Remote Access (WAN) or LAN as well?

If so, one way of keeping them separate is to:

  • DS418play on port 32400
  • TS451 on port 32401

ChuckPa, thanks for responding to my posted issues. Let me say this first, I’m as green as they come when it comes to these issues and especially to network issues; so please forgive me for my ignorance.
Yes, I see the DS418 and TS451 are published to port 32400 in Plex. In the Remote Access section of Plex I changed the public port for TS451 to 32401 and the system said the TS451 is “Fully accessible outside your network” but minutes later the system reverts back to “Not available outside your network”.
When I changed the TS653D Port to 32402 I noticed the DS418 server disappeared which looks like I may have to reclaim the DS418 again. You didn’t mention the TS653D in your instruction; so, I’m not sure if I should have changed it from Port 32400 to 32402. In any case, the remote access for TS653D is showing “Not available outside your network”.
I seem to be having issues with remote access as well as on the local network.
Before I screw up anything else I will wait for your reply to this message because I feel I may be adjusting things incorrectly.

You have 6 different IP addresses for 3 devices, that is your biggest mistake.

Each device should have a single IP address as far as Plex is concerned, otherwise Plex can send on one adapter, but receive on the other adapter, which means Plex may never get the reply on the first used adapter where it is needed.

For the Synology NAS, go to Control Panel > Network > Network Interface > Create > Create Bond and then select both adapters and bond them together into a single connection/IP Address.

Do the same (or similar) on your QNAP NAS and Plex should work as expected after that.

You should also go to Plex Settings > Server > Network > Preferred network interface and set it to the Bonded connection you created above. Don’t forget to click on Save Changes.