No Soup For You, Fresh Install

Plex Media Server
1

Server Version#: 1.19.3.2831-181d9145d
OS: CentOS 8, 4.18.0-147.8.1.el8_1.x86_64

This is a plain jane fresh install. I’m not trying to claim or recover anything. I have fully gutted my plex “Authorized Devices”, I have fully deleted plex, and removed all files, I have signed out entirely from the web account, I have signed out of every other portal I can. I have flushed my cache, and even rebooted the server where Plex was installed.

I’m starting fresh.

I go to plex, and download copy the link to the public 64-bit RPM.

$ dnf -y install https://downloads.plex.tv/plex-media-server-new/1.19.3.2831-181d9145d/redhat/plexmediaserver-1.19.3.2831-181d9145d.x86_64.rpm

everything installs just fine.

systemctl status plexmediaserver: RUNNING (no errors)

(in a private browser): 10.0.20.2:32400/web/

I get immediately forwarded to:

http://10.0.20.2:32400/web/index.html#!/setup/

Prompted to sign in … no issues

NO SOUP FOR YOU!

Like I said, I’m not trying to claim a server or anything – fresh install.

I don’t understand what’s going wrong.

P.S. – Been using Plex without issues for 3 years, just decided to do it all over with a dedicated video card, and CentOS 8.

EDIT: Added Logs, of all steps outlined above.Plex Media Server.log (483.0 KB)

2

I’m looking at your logs.

PMS is seeing the incoming request from 10.0.10.15 … which is a different subnet… and denying setup access on that basic.

When performing setup, you must be either:

a. Have server and accessing system on the same RFC-1918 subnet
b. Use SSH tunnel to tunnel to 127.0.0.1

Your log shows how PMS is seeing the system you’re accessing from.

May 21, 2020 13:49:54.411 [0x7fb1d4ff9700] DEBUG - Request: [10.0.10.15:56068 (WAN)] GET /web/ (3 live) GZIP
May 21, 2020 13:49:54.416 [0x7fb1e6ffd700] DEBUG - Completed: [10.0.10.15:56068] 302 GET /web/ (3 live) GZIP 5ms 281 bytes (pipelined: 1) -> http://10.0.20.2:32400/web/index.html#!/setup/cbc45be8a3c545dcd6357a99561e425dfb960fac
May 21, 2020 13:49:54.449 [0x7fb1d4ff9700] DEBUG - Request: [10.0.10.15:56068 (WAN)] GET /web/index.html (3 live) GZIP

Are you using a Proxy? (notice the 302 return code)

3

In this new setup, I now have a pfSense at the head. I do have rules to pass all traffic between the vLans. Since I have the “Media vLan” purposefully segregated, how can I complete this setup? This appears to be something that plex doesn’t like, not an issue on the network layer. Do you agree?

4

Plex only implements this default security when the server isn’t claimed.

The use-case scenario which drove this was:

  1. Server is on a rented / remote host somewhere
  2. Something happens and the server becomes disassociated from your account.
  3. How to prevent unscrupulous individuals from accessing your information.

To get through this and claim it,

  1. ssh -L 8888:127.0.0.1:32400 ip.addr.of.server
  2. Sign in the ssh session and allow to sit idle.
  3. Sign out of Plex/web (your browser)
  4. Open incognito Window
  5. Navigate to http://127.0.0.1:8888/web
2 Likes
5

plex-pfsense
plex-pfsense1161×243 25.2 KB

6

VLANs mean nothing in this scenario. If anything, they only serve to solidify the isolation.

SSH-tunnel will allow you to proceed.

Once signed in, your VLANs will do as you want to control traffic.

EDIT: I also have a pfSense box as my head-edge device . I have two vlans.

7

Okay, standby.

8

This worked great! Thanks! ALL FIXED!

9

outstanding.

Please check the appropriate box so others will be able to find it in the future?

10

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