If I’ve migrated my entire plex config directory (Linux) to a different server and want to basically run it as a secondary/backup (so not at all associated with the first) can I simply just delete the Preferences.xml to in essence make it a brand new server but with all metadata in place? Or do I need to do something to the Plex database as well?
Basically the goal is to create a new PMS linked to the same media that will maintain all the metadata that’s already been generated but be a new instance. I would run this server as a “backup” when my main server is down.
OK I’m super confused. I deleted the Preferences.xml, started up the “new” server, connected to it via http://IPADDRESS:32400/web and it re-directed me to the Plex web app. It then asked me to sign in with my account and once, it’s like I’m still connected to the original server (all settings are in tact, all users are there and libraries shared).
This is all from a different browser and the server is on a completely different network than the original.
Break the VPN. ssh -L 8888:127.0.0.1:32400 natural.ip.of.remote
Open the browser tab to http://127.0.0.1:8888/web and run setup (it’s running as free-standing and Plex/Web won’t get confused)
After signing in and associating with your account, close the tunnel
Reestablish the VPN
I’m not sure what you’re asking me to do. Maybe there is some confusion on my setup.
PMS 1: unRAID Linux server - 10.10.4.30 PMS 2: unRAID Linux server - 192.168.4.30
10.10.4.0 and 192.168.4.0 are connected via an always on Site to Site VPN on pfSense boxes at both locations.
I’m trying to connect to PMS 2 from a host in either network and both will redirect me to the plex web app to sign in. So even when I connect to PMS 2 from say 192.168.4.50, it still redirects me to the plex web app. So the VPN is in no way involved there.
If site-to-site, open the IP of the machine which matches your machine’s subnet.
Crossing subnet boundaries makes the uninitialized PMS treat you as “Remote” and not “Local”. The server can only be claimed by a ‘Local’ IP address (same LAN)
Also, in case you (or anyone else for that matter) didn’t know, after you are logged in, make sure you are still connected to the correct server; check the top left under the home link, the drop down will allow you to select from any server linked or shared to your account.
this drop down is there, even if you are connected locally direct to an IP
If site-to-site, open the IP of the machine which matches your machine’s subnet.
Crossing subnet boundaries makes the uninitialized PMS treat you as “Remote” and not “Local”. The server can only be claimed by a ‘Local’ IP address (same LAN)
Originally I was trying to connect from my PC which is on the other side of the VPN so different subnet. But I’ve since tried connecting from a PC in the same subnet as PMS 2 and I’m getting the same results. No matter what I get redirected to the Plex web app, get asked to sign in, and the only sever that shows up in the drop down is PMS 1.
Because of your configuration, we need to do this differently.
I think PMS is getting hung up on having both networks.
Sign local PMS web client out (upper right corner turns to gray icon)
Stop the local PMS service
Initiate the ssh tunnel to the remote (ssh as above and using local browser http://127.0.0.1:8888/web also as above)
As you start the remote PMS, it will want you to sign in. Instead, in the lower right corner, you will find “what’s this?”
Take it. It will allow you to continue with a completely local-limited, no codecs, initialization.
When you arrive at the Dashboard, Settings - Server - General and sign in
The important point is it brings you ultimately to the Dashboard
What happens is the server will immediately upgrade from that debugging mode to normal mode and be part of your account. Think of it as a one-way door. It gets the minimal pieces running just enough to ‘step up’ and be a proper full server
I don’t understand what you’re asking me to do with step 3. Why am I SSHing and to and from where?
I can’t access either of my servers via a local web browser (127.0.0.1 or localhost) as they are both headless. I can access them via their local IP address.
ssh -L 8888:127.0.0.1:32400 ip.addr.of.host is what puts you on the console of a headless machine.
That’s the trick
You must guarantee you’re not caught up in an accidental cross-subnet addressing. PMS does not allow us to select which adapter to use as Primary. Being on the loopback adapter guarantees there is no ambiguity
In that terminal window ssh -L 8888:127.0.0.1:32400 ip.addr.of.other
Sign in to the other machine and let sit idle.
In fresh browser tab http://127.0.0.1:8888/web
What happens is:
You open a SSH session to the other machine which is signed in then sits idle
The -L option takes port 8888 from the local machine and redirects it through the tunnel to 127.0.0.1:32400 on the other end.
You open 127.0.0.1:8888/web locally.
The 8888 port number fires and the /web part is relayed through the tunnel, What the other end sees is http://127.0.0.1:32400/web just as we want, even though it has no head
