Still having issure whith my plex server on ubuntu

Plex Media Server Desktops & Laptops
1

this is a help cry to the devs

i am a network engineering student whith kwite a bit of linux knolage onder my belt

i thing plex is a wonderfoll project and have bin jusing it fot over 5 year now

only last month when i reinstated my home Linux box to ubuntu 18.04.3
and tried to install plex get i gredet whith the error “unabel to caim the server”

i have sins been testing on many different combinations of os acupuncture and network configurations
and the only thin i have gotten to work is on windows 10

plz help :sob: :sob:

i miss my plex server

2

Hope it’s okay if the community help ? :wink:

  • Is both the server and the workstation trying to claim PMS running in Private Address Space ?
  • Is DNS working for your PMS server, as well as Internet Access?
  • Debug logs from PMS would be nice, and please upload as a zip with all of them
3

all server are on a ipv4 LAN network nat to the internet (tested on 3 different ISP)

i used my privet dns servers and as well the cloudflare dns and google dns for testing

my main server fist test
Plex Media Server Logs_2020-02-08_17-02-02.zip (236.9 KB)

my fist test vm
Plex Media Server Logs_2020-02-08_23-08-05.zip (99.1 KB)

the rest of the info can be found in my old topic Unable to claim on version 1.18.6

4

Please be more detailed here…

Your origin post is about a snap install, and then you add links to logs for what I guess is a native install, as well as a VM install ?

So is the one you call

a native install, and if so, we’ll continue with that…

And please clean up your TAG’s on this thread!

5

i have tested the snap install it has the same issue as the .deb install for me

but i propose we begin whit a clean slate

i have booted op a test vm running on my local workstation and installed plex 1.18.7.2438 via the .deb whacked throw the initial install wizard

log file Plex Media Server Logs_2020-02-21_21-42-07.zip (128.2 KB)

6

Having seen your adjustments to the tagging, I have taken the liberty to classify this better. I removed the other tags which did not belong (tips) and put this under normal server.

  1. The logs, just now posted, are much cleaner

  2. It appears there is still a network configuration problem

Feb 21, 2020 21:41:16.372 [0x7f8aff7e6700] DEBUG - Request: [127.0.0.1:35120 (Loopback)] GET / (5 live) GZIP
Feb 21, 2020 21:41:16.373 [0x7f8b3487d700] DEBUG - Completed: [127.0.0.1:35120] 200 GET / (5 live) GZIP 0ms 1192 bytes
Feb 21, 2020 21:41:21.380 [0x7f8b3487d700] DEBUG - Completed: [192.168.2.177:57380] 200 GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (3 live) GZIP 20000ms 5 bytes (pipelined: 6)
Feb 21, 2020 21:41:21.384 [0x7f8aff7e6700] DEBUG - Request: [192.168.2.177:57380 (Subnet)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (3 live) GZIP
Feb 21, 2020 21:41:21.384 [0x7f8aff7e6700] DEBUG - Content-Length is -1 (of total: -1).
Feb 21, 2020 21:41:26.366 [0x7f8b137fe700] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://10.33.10.6:34400/device.xml
Feb 21, 2020 21:41:26.366 [0x7f8b137fe700] DEBUG - HTTP requesting GET http://10.33.10.6:34400/device.xml
Feb 21, 2020 21:41:36.752 [0x7f8b117fa700] DEBUG - NAT: UPnP, not an IGD: <http://10.33.10.6:34400/device.xml>.
Feb 21, 2020 21:41:36.752 [0x7f8b117fa700] DEBUG - NAT: UPnP, didn't find usable IGD.
Feb 21, 2020 21:41:36.752 [0x7f8b117fa700] DEBUG - NAT: PMP, attempting mapping.
Feb 21, 2020 21:41:41.369 [0x7f8b137fe700] ERROR - Error issuing curl_easy_perform(handle): 28
Feb 21, 2020 21:41:41.369 [0x7f8b137fe700] DEBUG - HTTP simulating 408 after curl timeout
Feb 21, 2020 21:41:41.369 [0x7f8b137fe700] ERROR - SSDP: Error parsing device schema for http:

Which network should this be? 192.168.x.x or 10.x.x.x ?

This looks like a NAT within a NAT configuration which will never work.

7

From the log:

Feb 21, 2020 21:39:31.222 [0x7f8b2f77d700] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=408):

Above indicates either a bad gateway, or a bad/slow DNS

If gateway is okay, then try and switch DNS to Google for a short test
(8.8.8.8 & 8.8.4.4)

The report back, and if still not working, new logs please :wink:

10

its 192.168.2.0/24

dns servers are located at 10.10.50.20 and 10.10.50.21

11

Would you mind showing a quasi block step of the topology?

e.g. VM (IP) -> Host (IP) -> LAN devices in the chain… -> Modem/Router -> WAN

12

Switch to Google as suggested!

14

working on that

1 Like
16

hear is a over simplify topology of my network
Untitled Diagram (1)
al the network get routed via ubiquiti edgerouter
9 ms to google

19

Is the modem in bridge mode, or are you having a double NAT ?

22

its a modem not a router

no

23

Then logs after changing DNS, and reboot of the PMS server!

24

i have it working now on one of the testing vm :joy:

i am now trying to get it working on my main box

25

So switching to Google DNS worked?

26

yes soft of

ist strange i have tested last weekend with google and cloudflare with no success

and now it works :joy:

28

Well, I only accept a boolean here :smiley:

So true or false!

1 Like
29

it works

thanks for all the help
still strange that it work but it does :joy:

by the way GitHub - ukdtom/ClaimIt: ClaimIt 4 Plex Media Server cool tool :wink:

1 Like