I’ve been running two up to date Plex Media Servers, Server_A and Server_B on Synology DSM 7. I placed Server_B in a remote location and manually travel to update files. Recently I had a large volume of files to add and wanted to avoid manually updating metadata for each one. Therefore, I copied the entire PlexMediaServer folder from Server_A onto Server_B. Server_B has disappeared from my Plex Dashboard and Server_A continually registers as changing ip addresses depending on which server is online. How can I re-register Server_B as its own server?
The PlexMediaServer shared folder contains Preferences.xml.
This file contains the server’s identity information.
The PlexMediaServer shared folder is very fragile (DSM 7 rules)
When you overwrote it with the other server’s ID information, you effectively cloned one as the other.
In order to make server B visible again.
- Stop PMS
- Using FileStation, go into “PlexMediaServer / AppData / Plex Media Server”
- DELETE Preferences.xml
Given server B is remote from you, you now have no choice but to reclaim it using the package .
-
Uninstall PMS with the KEEP (first radio button) option
-
Reinstall PMS again (same version SPK file) EXCEPT
– Install using Plex Claim Token Open
– Click “Get Plex Claim Token”
– COPY the token it gives you
– QUICKLY PASTE it into the box on the installation form.
– Click NEXT NEXT DONE and let it start installing. -
When complete, if it’s reclaimed correctly, It will respond with your username in the “Claimed by:” results.
-
If that’s not the case or if as you start it, if it does not show up again
– THEN you’ve completely broken all the file permissions in the PlexMediaServer shared folder
(This happens when you copy from one to the other without considering the underpinnings) -
Should this be the case, you’ll need to repair the PlexMediaServer shared folder.
This is the How-To
When all is done, you will need to REMOVE the old instance of server B and share it as a ‘New Server B’.
Thank you for your fast responses!
I was able to uninstall and reinstall through a Plex Claim Token. Having some issues seeing the claimed server appear in my Plex web app. I will look tomorrow and ensure that the server is up and running correctly on Server B.
Do a complete restart of the browser…
That will load the servers again from Plex.tv
How odd. I restarted the browser and Server B. Currently Server A is running and visible in Plex browser/desktop app as ‘nearby’ (local). Server B is running but is not visible in Plex browser/desktop/app. I am accessing Server B through Synology quickconnect so am unable to access locally. Perhaps this is the trigger for me to set up a VPN.
Do you recommend me to retry the Server B removal / reinstall process you outlined above?
Can we stop with the “A/B” thing?
I see you have a DS918 and a DS118 both of which are claimed.
It appears, based on plex.tv, the DS918 last seen some 12 hours ago and the DS118 3 hours ago.
Which is which please ?
For whichever one is not visible on your account, make a zip of the log files please and attach here.
I’m starting to suspect your Remote Access settings are part of the problem here.
Great! Didn’t know you had that visibility.
DS918 is the local source server. DS118 is the destination remote server that I recently transferred metadata, reinstalled, and reclaimed the server through a token.
After restarting DS118, I now see DS118 as a server in Plex! It is listed on my Authorized Devices page.
I’ve “allowed unsecure connections” so we can troubleshoot it. I still receive the “DS118 is currently unavailable” message. Accessing the server from a Plex client on the DS118 local network return “No Content Available”.
I won’t be at the local site to access DS118 - Plex to pull logs files until Saturday. I can only access the Synology NAS where the server sits. I restarted DS118 for good measure but that doesn’t seem to have fixed the connection issues.
I am fine for DS118 to be Local access only (no remote streams needed. Just need to get the server talking to Plex to make local devices work.
You have access to that remote machine through quick connect, right?
If so, that’s all you need.
- Get into that machine
- Start Plex (stop first and wait 30 seconds if needed)
- Let it run 3 minutes
- Stop Plex
- Using FileStation, navigate PlexMediaServer/AppData/Plex Media Server
- RIght-Click “Logs” → Compress to Logs.zip
- Now download the ZIP to your computer
- Upload/attach it here
Logs attached.
Logs.zip (386.5 KB)
If it comes up in the logs, DS918 location is 47.204.XX.XXX. DS118 location is 142.197.XXX.XXX.
Sorry for delay. (cooking and eating time 
)
from what I can see, remote access is not working.
that remote modem/router either isn’t allowing UPNP or the manual port forwarding isn’t active/correct.
May 27, 2024 11:05:12.399 [547653095648] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443] MyPlex: Requesting reachability check.
May 27, 2024 11:05:13.085 [547653095648] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443/HCl#3d] HTTP requesting PUT https://plex.tv/api/servers/cb7db493abaaff7a93ac36e16dfe8ddc0b9d181b/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=533b7fe5-ea0f-487c-9264-b6a760826df6
May 27, 2024 11:05:13.273 [547633393888] DEBUG - [HttpClient/HCl#3d] HTTP/2.0 (0.2s) 200 response from PUT https://plex.tv/api/servers/cb7db493abaaff7a93ac36e16dfe8ddc0b9d181b/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=533b7fe5-ea0f-487c-9264-b6a760826df6 (reused)
May 27, 2024 11:05:13.273 [547653095648] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443] Successfully connected to pubsub.plex.tv.
May 27, 2024 11:05:13.378 [547655205088] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443] EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="533b7fe5-ea0f-487c-9264-b6a760826df6" connectivity="0" command="notifyConnectivity"/>'
May 27, 2024 11:05:13.533 [547655205088] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443] PubSub: Got notified of reachability for async identifier 533b7fe5-ea0f-487c-9264-b6a760826df6: 0 for :0 (responded in 259 ms)
May 27, 2024 11:05:13.534 [547655205088] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443] MyPlex: reachability check - current mapping state: 'Mapped - Not Published (Not Reachable)'.
May 27, 2024 11:05:13.534 [547655205088] DEBUG - [EventSourceClient/pubsub/pubsub.plex.tv:443] MyPlex: mapping state set to 'Mapped - Not Published (Not Reachable)'.
May 27, 2024 11:05:17.758 [547599663328] DEBUG - Request: [127.0.0.1:50722 (Loopback)] GET /servers (2 live) #40 GZIP Signed-in Token (jacobsi1)
reachability 0 = not reachable
Noted. It sounds like a network issue then and nothing to do with the Plex server. Thanks for your help, Chuck.
I think so.
If you don’t have “Relay” enabled, you’ll need Remote Access to get to the machine.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
