Unable to set up secondary Plex server?

Hi all-

I’m attempting to set up a secondary Plex server but when I navigate to the http://<server_ip>:32400/web, I’m prompted to sign-in and then after that it only shows my first Plex server. Is there a way to force setup of a new server somehow instead of only showing the first server?

I attempted on both Ubuntu 16.04 and CentOS 7 but neither of them seem to be able to bring me to the setup page. I don’t think it’s a firewall issue (my laptop and server are on different VLANs) seeing as I can get to the server’s local web interface. My laptop is also able to initiate GDM connections to the VLAN the server is in (UDP 32410, 32412-32414) but not the other way around (if that helps any).

Hopefully it’s just something dumb I’m missing!

Should work as http://192.168.0.5:32400/web
Change to your IP.
Then in the upper left area of the web manager, select your server. My main server shows up first, I have to change it to look at my second server.

Or, from the machine the server is installed, if on a VM or another PC, use local http://localhost:32400/web

Those should work.

You can check http://Plex.tv/web as well.

For the initial setup page to work when on a different subnet, you will need to create a ssh tunnel or remote into it.

I think the issue is your port number being the same. Try changing the port number on the first server and you should be golden.

The port number of the server itself cannot be changed. It is always 32400.

Try it this way:
shut down your first/old server
call up the plex web from the new server http://192.168.0.5:32400/web
(substitute the IP address with the local/private IP address of your new server)
do not sign in to Plex web for now
instead, sign in the new server to your plex.tv account (also called ‘claiming’ the server)

Just remembered:
maybe you just didn’t find the switch to change to your new server? You need to switch before you can make any change

@OttoKerner said:
The port number of the server itself cannot be changed. It is always 32400.

Try it this way:
shut down your first/old server
call up the plex web from the new server http://192.168.0.5:32400/web
(substitute the IP address with the local/private IP address of your new server)
do not sign in to Plex web for now
instead, sign in the new server to your plex.tv account (also called ‘claiming’ the server)

…weird…?

look under Settings>Server>Remote Access and the click SHOW ADVANCED

@aschmidtm said:


…weird…?
look under Settings>Server>Remote Access and the click SHOW ADVANCED

this doesn’t relate to the OP’s problem.
If I understood it right, his problem was not how to access his new server from the outside, but how to access it from his own local LAN.
The settings in the screenshot above deal with ‘remote access’, not ‘local access’.

@Peter_W said:
For the initial setup page to work when on a different subnet, you will need to create a ssh tunnel or remote into it.

Got em! Even though all my local routing was in place, I guess Plex only lets you setup a new server if you’re accessing it from the same subnet (which I was not). I realize most people aren’t going to have the issue of multiple subnets on their LAN but I think the Plex setup guide should definitely add the caveat that you will need to be in the same subnet for initial subnet to work. Right now, it only says you need to access the servers locally for initial setup. While technically true, this is only a subset of the real requirement of opening it within the same subnet.

Thanks to everyone for their help!

@OttoKerner said:
this doesn’t relate to the OP’s problem.

I understand this. Though, this was written:

@OttoKerner said:
The port number of the server itself cannot be changed. It is always 32400.

What is written needs to be true. People search this forum.

I’m not trying to be a D or a T, I’m just socially inept.

Hi @aschmidtm

After further research this does not change the local port - it just changes the port the router listen to. As @OttoKerner states the local port will always be 32400.

Sorry for the confusion I caused on this thread!