Server Version#:plexmediaserver_1.20.1.3252-a78fef9a9_amd64.deb
Player Version#: Plex Web Version 4.34.4
Platform: and are Linux 16.04 and 20.04 respectively, headless devices.
Issue: Have had for years. Good server, not powerful, wants to be replaced by better device. So created . serverB is not available in gui after installation.
Details: With still running (and FW forwarding 32400 to it), installed server software above on . Directed browser (on workstation, not either server) to :32400. Asks me to log in. Done. Now URL in browser is :32400/web/blahblahblah. Everything looked perfectly normal, same as if I’d logged into :32400, except the URL is different.
does not appear anywhere in config, can’t do anything to reconfigure it, etc.
SO… well hey the media is all on NAS anyway, so I just deleted from config. Also reconfigured router to forward 32400 to instead of . Stopped services on . Restarted services on . Still log in fine to http://:32400, but it claims I have no servers. Helpfully offers me option of downloading Plex Media Server.
What have i done wrong? Goal here was to install and register with Plex.tv and my Plex Pass (which I assume worked, as that’s how I logged into it), then set up my new libraries, dvr, etc, then eventually shut down and re-route my port32400 forward to . But I just can’t fine available even though if you look at the URL in my browser, that’s what I’m logged into. Have removed plexmediaserver package and reinstalled. Have tried to log into :32400 (by running firefox on the server) but that doesn’t connect.
Oh CRAP. My nomenclature for ServerA and ServerB disappeared in markup. Let me try this again:
Server Version#:plexmediaserver_1.20.1.3252-a78fef9a9_amd64.deb
Player Version#: Plex Web Version 4.34.4
Platform: SERVERA and SERVERB are Linux 16.04 and 20.04 respectively, headless devices.
Issue: Have had SERVERA for years. Good server, not powerful, wants to be replaced by better device. So created SERVERB. serverB is not available in gui after installation.
Details: With SERVERA still running (and FW forwarding 32400 to it), installed server software above on SERVERB. Directed browser (on workstation, not either server) to SERVERB:32400. Asks me to log in. Done. Now URL in browser is SERVERB:32400/web/blahblahblah. Everything looked perfectly normal, same as if I’d logged into SERVERA:32400, except the URL is different.
SERVERB does not appear anywhere in config, can’t do anything to reconfigure it, etc.
SO… well hey the media is all on NAS anyway, so I just deleted SERVERA from config. Also reconfigured router to forward 32400 to SERVERB instead of SERVERA. Stopped services on SERVERA. Restarted services on SERVERB. Still log in fine to http://SERVERB:32400, but it claims I have no servers. Helpfully offers me option of downloading Plex Media Server.
What have i done wrong? Goal here was to install and register SERVERB with Plex.tv and my Plex Pass (which I assume worked, as that’s how I logged into it), then set up my new libraries, dvr, etc, then eventually shut down and re-route my port32400 forward to SERVERB . But I just can’t find SERVERB available even though if you look at the URL in my browser, that’s what I’m logged into. Have removed plexmediaserver package and reinstalled. Have tried to log into LOCALHOST:32400 (by running firefox on the server) but that doesn’t connect.
Going to https://app.plex.tv/desktop#!/settings/web/general directly does not show any servers now. I assume if I restarted SERVERA it would re-appear here (it said it would when I deleted it). Still, SERVERB is running, and I can get this exact GUI by navigating to it.
the orginal server DOES have a “real” external DNS CNAME record (all aliases to my one external IP). I added one for the new one as well. Don’t see how that should affect it, but hey, why not try I guess.
Nope. I’ll just call this lesson learned: Always access your brand-new Plex device by IP only at first, even if it’s got a static and a name. Works great now, BTW, using name only.
I don’t want to hijack the thread, but I’m having a similar issue. The differences this time compared to all the others are that I’ve changed my subnet from common 192.168.0.1 to a non-standard 188.182.81.0, moved from Debian to Ubuntu and re-named Preferences.xml.
Setup
Server Version#: plexmediaserver_1.20.1.3252-*_arm64.deb
Player Version#: Plex Web Version 4.34.4
Platform: SERVER_1 was running Debian Buster, while SERVER_2 is running Ubuntu Focal.
This is what I've done:
Moved data after re-installing, sudo chown -R plex:plex /var/lib/plexmediaserver and renamed Preferences.xml to Preferences.xml_BAK. Earlier, I’ve just removed the ID’s, but as a consequent, my Preferences.xml was 2-3 years old. So I thought it was time to get a fresh one. I’ve deleted the old server from Plex, and should be faced with “claim server or something” as I’ve been earlier.
So, could it be that changing the subnet is the issue? Just to be clear, I’m trying to access my (new) server with http://188.182.81.167:32400/web/index.html#. I can open a new thread if that is preferred.
Why are you changing it? Afaik this just won’t work. It’s gonna get confused with where ever that really is which seems to be assigned to a registrar in Denmark IP Search Results
Using that IP will probably make that entire 188 subnet (how much depends on your mask) unavailable to you, and probably also will make the Plex server see it as “local” thus giving anyone in Denmark in that range free access to your stuff…
Plex simply won’t allow you to declare a public IP range as not in need of authentication.
Which is also the reason why you can’t claim the server from another computer in the same local network. You’ll have to create a “tunnel” connection to the server machine to claim it.
Hence the urgent recommendation not to use public IP ranges for a LAN.
There are enough private IP ranges available. With “subnetting” you can create more different private IP spaces than you’ll ever need.
I changed it to increase the security of the LAN network where my router has ipv4 188.182.81.1. However, I see afterwards that I probably should have chosen a subnet which is in the ipv4 range of private networks according to the link ChuckPa is referring to. This is the first and only issue I’ve met after several weeks of using the subnet.
I guess I could work-around this by setup Plex with reverse proxy through nginx which I do for other services such as Pi-hole. Yet I think it is best to follow practices from IETF and use a subnet in the ipv4 range for private networks. Which there are plenty of options given the vaste range on 10.*.*.* and 172.16.*.*-172.31.*.* etc. So it’s safe to say that if a choose a subnet of example 10.251.250.* which is in the RFC-1918 address space there is likely that my issue will get solved?
If you use RFC1918 ip addresses in your home network, and set up a NAT on your router of port 32400 to your internal IP port 32400 you will have all you need. Don’t set up any nginx or apache reverse proxies, not needed and I wouldn’t think they’re recommended. You can access your stuff via your plex.tv account wherever you are.
Works great now, BTW, using name only.