How do I claim my newly installed server?

Plex Media Server Desktops & Laptops
1

Server Version#: 1.18.2.2058
Player Version#:

Hi,

I installed a fresh new server, but all I get is “No soup for you, you do not have access to this server”
Wtf, it is a FRESH server, I installed Ubuntu twice now and I can’t set up the new Plex installation!
Any one that know how to fix this? Have re-installed Plex server too, with the same crap.

Please help

2

Need some basic info:

  1. Server local or remote?
  2. If local, is the LAN RFC-1918 compliant (192.168.x.x, 172.16.x.x-172.31.x.x, 10.x.x.x) ?
  3. Also if local, on the same subnet?
3

It is a local server, installed Ubuntu 18.04
Server IP 192.168.1.10

4

Everything on the same subnet?

5

Yes same

6

I had to reinstall my server, so I am using the exact same hardware and IP for this server, even had Ubuntu 18.04 on the previous install.
So it is so strange!

7

Sign the Plex/Web player app out of your Plex account.
Open an incognito window to it.

Is this installed from the Ubuntu store, a Docker, or the native app from Plex.tv/downloads?

8

Open an incognito window to it.

I believe that was what I had to do as well. Using a different browser (Edge) worked too.

9

Where did you download from / which packaging did you install?

10

From Plex.tv
https://downloads.plex.tv/plex-media-server-new/1.18.2.2058-e67a4e892/debian/plexmediaserver_1.18.2.2058-e67a4e892_amd64.deb

11

Thanks. The reason I asked is because of where all the data directories are placed.

Each packaging form puts them in different places. Now, if I need give you instructions how to get into it manually, I know I’ll be giving the correct instructions.

12

PMS logs please, in a zip

13

Logs.zip (114.4 KB)

Here you go. Time to hit the bed here in Sweden.
Thanks for helping me.

14

Your computer and server are not on the same subnet, which they should be, either by addressing or netmask.

PMS is treating your computer as if remote. Notice the “WAN” designation below.

PMS won’t let itself be claimed directly by a remote client (default security to protect hosted servers).

Server is at:

Dec 01, 2019 20:49:48.128 [0x7f4df4e33b80] DEBUG - Network interfaces:
Dec 01, 2019 20:49:48.128 [0x7f4df4e33b80] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Dec 01, 2019 20:49:48.128 [0x7f4df4e33b80] DEBUG -  * 2 eno1 (192.168.1.10) (loopback: 0)
Dec 01, 2019 20:49:48.128 [0x7f4df4e33b80] DEBUG -  * 1 lo (::1) (loopback: 1)
Dec 01, 2019 20:49:48.128 [0x7f4df4e33b80] DEBUG -  * 2 eno1 (fe80::1a66:daff:fe38:9e7f%eno1) (loopback: 0)

Computer loading the web client (Plex/web) is at:

Dec 01, 2019 20:49:58.579 [0x7f4dc5ffb700] DEBUG - Request: [192.168.2.46:64288 (WAN)] GET /web/js/chunk-2-b2c07a7794e6186e0e42-plex-4.8.4-d12b992.js (3 live) GZIP
Dec 01, 2019 20:49:58.580 [0x7f4dc5ffb700] DEBUG - Final path: "/usr/lib/plexmediaserver/Resources/Plug-ins-e67a4e892/WebClient.bundle/Contents/Resources/js/chunk-2-b2c07a7794e6186e0e42-plex-4.8.4-d12b992.js"

@dane22
I believe you have a cure for this? :slight_smile:

1 Like
15

crap, that’s right, my pc was on my wlan!!! So simple. Thx

16

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