Can't setup new plex instances.

General Discussions
1

Just installed two new plex servers on two VM instances running CentOS 7. I have two previous server instances running on bare metal which I intend to replace.

plexmediaserver-1.9.1.4272-b207937f1.x86_64.rpm

When I go to http://:32400 on either of the two new instances, I am asked to log in to my account, which I do. At that point, I’m dropped into the web interface for one of my existing servers with no option to configure the new server that I have connected to by ip.

Is there something I’m doing wrong?

2

Which IP addresses are you using on those VM’s ?

3

I’ve got local ip’s set up for all of them. 192.168.x.x
Existing bare metal servers: 192.168.1.2 (ms3), 192.168.1.3 (ms2)
New VM’s: 192.168.1.11 (no friendly name yet), 192.168.1.21 (no friendly name yet)
When I hit http://192.168.1.11:32400/web/index.html (or 192.168.1.21), The address bar correctly shows the URL, but the page I get is the web interface for ms3 and the dropdown only shows ms2, ms3, and PlexCloud.

4

I would like to see the PMS logs of these new instances please. My first idea was that you were using a “forbidden IP” (during initial setup IP’s are restricted to private ranges), but since this is not the case, it should be either firewall or PMS rejecting the connection.

5

Clean PMS log after restart and connect attempt.

6

I also have no firewall (firewalld or iptables) and selinux has been disabled.

7

The second node logs.

8

Quick question:

Are you using NAT or bridge networking in the VM? I suspect you have NAT since they would otherwise show up correctly.
(I ask because I often forget to put it in bridge mode and assign it a regular LAN address).

9

What I’ve noticed in the logs is that @OregonGunslinger is trying to setup from a PC with IP 192.168.1.100 and PMS considers this WAN (instead of LAN), which is forbidden during initial setup. @ChuckPA will handle from here.

10

@ChuckPA: VM’s are set up in bridge mode.
@moody_blue: 192.168.1.100 is WAN to 192.168.1.11?

11

Thanks.

In your logs I see the servers at 192.168.1.11 and 192.168.1.21
Connections from 192.168.1.100

Nothing is being treated as remote. (correct behavior)

I’ll refer to the hosts as host 11 and host 21 for clarity

  1. Stop both PMS instances
  2. On host 11 , do the following
  3. Rename "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Preferences.xml" to Preferences.xml.old
  4. Start PMS
  5. Open your browser to http://192.168.1.11
  6. Sign in and run the first-run setup wizard as normal but skip adding Library sections
  7. Click through until you get to the empty dashboard
  8. Go to Settings - Server - General and verify the host is named and signed into your Plex account
  9. Stop PMS

Now repeat the above sequence (steps 2-9) except for host 21,

When complete with host 21 PMS, start host 11 PMS

Both should appear in your left hand drop down Server selector.
When both do, you are free to select the desired host and continue to refine preferences and build library sections as you wish.

12

So, the results are the same. I only tried it with 11.

  1. Stop PMS (I stopped all instances, both the new VM’s and the existing bare metal instances)
  2. Renamed Preferences.xml -> Preferences.xml.old on 11
  3. Started PMS on 11
  4. Browsed to http://192.168.1.11:32400
  5. Ended up on a landing page where, after about 30 seconds, Plex cloud showed up in the left dropdown.

The URL showed http://192.168.1.11:32400/web/index.html but the first setup wizard never appeared.

13

After looking back through the logs, it does look like everything on my local network is being considered as a WAN connection. I’ve tried from three different systems and all of them tag the incoming ip with (WAN). How does plex make this determination? I’ve never encountered this behavior before.

14

I was incomplete in the URL. I apologize. Let’s go back and delete the Preferences.one more time.

after restarting: http://192.168.1.11:32400/web Don’t add anything else. It will land at /web and the first-run mode will kick in. Having /index redirected you away from the /setup endpoint which is both implied and automatic.

15

@OregonGunslinger said:
After looking back through the logs, it does look like everything on my local network is being considered as a WAN connection. I’ve tried from three different systems and all of them tag the incoming ip with (WAN). How does plex make this determination? I’ve never encountered this behavior before.
Possible causes here → https://support.plex.tv/hc/en-us/articles/204604227-Why-can-t-the-Plex-app-find-or-connect-to-my-Plex-Media-Server-

16

Ok, like things usually happen with me, it was a simple problem. During setup of the VM’s, I neglected to properly set the netmask on the network interface. It was set to 192.168.1.11/32 instead of 192.168.1.11/22. Once that was corrected, everything clicked.

Thanks to @moody_blue and @ChuckPA for all the help. Great forum and great response.