Installed second Plex server in network - cannot see how to add libraries to that server

Plex Media Server
1

Server Version#: v1.17.0.1709-982421575 - FreeBSD PC amd64
Player Version#: not applicable

I have just brought up a second server into our network. The server will be used for only a few weeks, and will then be shut down. I have good reason to need this second server at this time.

This server is and has been working within the network for years:
plex-nas1

This server is new and seems to be operational but I cannot manage it:
plex2-nas1

Now, when I go to plex2-nas1.lovelady.com, I am shown the library for plex-lovelady.com. When I select Settings on the browser GUI, I do not see plex2-nas1.lovelady.com in the list of servers. It seems to make no difference whether I set my URL to plex-nas1 or plex2-nas1… both show the same display, seen here:

image
image771×649 141 KB

Here is the server when not in settings mode:

image
image918×545 109 KB

What do I need to do in order to make plex2-nas1 appear in the server list so that I can begin manipulating the way that server works? Does it have to do with the Synchronization option?

Thanks for your time.

2

The initial claiming/configuration of the server must be performed on the localhost address or via the device’s local IP address (and that must be an RFC 1918 address). Your domain resolves to a public IP address; so, unless the system from which you’re accessing it can resolve that to a local IP address, you’ll see problems such as what you’re experiencing.

Have a look at the “On a Different Network” section of this support article:

It explains how to set up an SSH tunnel proxy to the server so it can be accessed via localhost for the initial configuration. After the initial configuration (once the server is claimed) you can access it via its public IP address or FQDN.

3

thanks for your reply, philipsw.

I can see why you would say that; it’s intentional that the name will resolve outside and inside. But I assure you we’re on the same internal (10.158.54/24) network.

image
image833×768 21.3 KB

But I will try to get localhost working to see what happens.

4

Got it. All I had to do, was to access it by its IP address as opposed to the name that resolves to that address. Interesting. But it worked, so I’m happy. Thanks so much for pointing me in the right direction. This is now resolved.

5

Yep, that’s why I mentioned it in my post :wink:.

No problem, glad you got it working.