Setup wizard never runs on new media server

Plex Media Server Desktops & Laptops
1

Server Version#: plexmediaserver-1.18.7.2457-77cb9455c.x86_64

I am trying to set up a Plex media server for the first time. I’ve created a CentOS 7 (x86_64) virtual machine, installed the plexmediaserver RPM, and opened port 32400 in iptables. When I connect with my browser for the first time, I’m prompted to log in, but after I log in, I’m sent immediately to a screen which says “Add your media to Plex … GET PLEX MEDIA SERVER.”

Of course, I just installed Plex Media Server, so I can’t really get it any more than I already have it. I’ve already rebuilt the VM once, and I’m getting exactly the same results.

Anyone have any idea what is going on?

2

There are some common mistakes which happen. I will point them out and you can see if any apply.

  1. The VM network adapter is NAT which places the server on a different subnet.
  2. Opening http://app.plex.tv in the browser instead of http://ip.addr.of.host:32400/web
5

It’s definitely not NAT’ed. I wouldn’t be able to connect to the web UI on port 32400 if it were, and I’m definitely talking to the VM.

6

If it’s not NAT, then it’s bridge. Bridge gives it its own IP on your LAN (DHCP or static).

Whether you connect to it direct (when bridged on same subnet)
-or-
ssh tunnel to it

You will need to connect to port 32400 in the host. This is how PMS works.

Perhaps it’s appropriate to tell me how you have things setup so I can give direct answers rather than guessing?

7

It’s KVM VM, connected to a VLAN access port on an Open vSwitch bridge, so it has an IP on my “guest” VLAN. I can connect to the web UI on port 32400 from my desktop system (using either the VM’s static IP or the hostname that I created in my DNS server).

To be clear, the web UI is available at http://hostname:32400. It just never shows the setup wizard.

8

Let’s cut right to it then.

  1. I can’t yet rule out a popup or javascript blocker (which the Plex/Web browser is written in,

  2. SSH tunnel into the VM
    a. ssh -L 8888.127.0.0.1:32400 LAN.IP.of.host (add -l username if required)
    b. Once signed in, let it sit idle
    c. Open incognito browser window on local host
    d. In that browser, open http://127.0.0.1:8888/web

  3. If the local machine does not have any blockers, you’ve bypassed all the VLAN / networking blocks and will see the Plex/Web

It will greet you, have you sign in, and then proceed to setup the server.

1 Like
9

PMS has two main requirements when configuring a server on the LAN.

  1. Client (workstation with the browser) and Server computer must be on the same subnet
  2. The subnet must use RFC-1918 compliant addressing.
2 Likes
10

Using an SSH tunnel appears to work.

Client (workstation with the browser) and Server computer must be on the same subnet

That may be it. As I mentioned, the VM hosting the PMS is on my “guest” VLAN, but my desktop is on a different VLAN/subnet.

Wow! That failure mode is … suboptimal.

Thanks for your help!

11

It is done because many users also have the PMS on a remote (hosted) server.

If the server is unclaimed, the last thing you would want is anyone being able to access it and take control while in that state.

12

That makes sense. I was more commenting on the lack of a useful error message or other indication of what was going on. IIRC, the same-subnet requirement wasn’t mentioned in the setup guide that I followed either.

All good now, so certainly not a big deal.

Thanks again!

13

Thank you, this is exactly what I needed. Hey Plex admins: please pin this post, or at least the summary of it from ChuckPA. There is absolutely no indication anywhere that the reason I could not set up my system is that I’m on a wireless that is not connected directly to the server.

14
  • Opening the Plex Web App on a Device Other than the Server Itself
    – On a Different Network
15

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.