Can not claim server besides multiple efforts ... need help!

[laaray]

Server Version#: 1.15.2.793 on ubuntu 18.04.2
Player Version#: 3.83.1 on mac (but irrelevant as issue is with server)

I have the same as many, as I found many posts on the same topics, but unfortunately I could not find a sustainable solution, I still can’t claim my server (well it randomly some time success and then get lost on restart).

Links to a few examples of related topics:

Can't claim Server

I am running a Synology DS218+ and I can’t seem to claim the server? I am running DSM 6.1.4-15217 Update 1. What can I try? SO far I have tried logging out and into Plex. I’ve tried uninstalling and reinstalling the Plex Server on the DS218+ and still nothing. When I attempt to Claim Server it merely cycles the “Claim Server” display.

Unable to Claim Server

Hello ausloki. Did you ever get this resolved? I ran into the same issue about 6 months ago and never figured it out. Didn’t matter if I used Server 2012 or 2016. I never could claim the server. Gave up and installed Windows 10 on the same hardware with the same ip address and everything worked. I find myself once again wanting to use a Server Operating System on newer hardware (so I can team the NICs) and same issue… installs fine but unable to claim the server. I’m almost thinking it’…

Can't Claim Server

so you’re telling me the random IP range i selected by dropping the 2nd 9 to a 7 on my IP address (192.168.0.XXX to 172.168.0.XXX) put me into a ‘public IP’ range? And that simply moving back to 192.168.0.XXX will fix it? This is blowing my mind. Thank you so much for pointing that out. I’ll see if it works!

Why does it keep asking me to claim my server?

The path for Preferences.xml is slightly different for me: /var/lib/plex/Plex Media Server/Preferences.xml What do I do for the Plex Server to be able to write to this file?

What I have tried:

-disable firewall (sudo ufw enable/disable)
-delete Preferences.xml and restart
-restart completely multiples times the server
-try on different hardware
-manually configure dns to point to rooter (192.168.1.1)
-log off and back in my account
-checked plex owns the Preferences.xml file
-Try to access links that fails to be accessed on the logs eg https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=debian&version=1.15.2.793-782228f99, and it worked.

Here is my logs:
Plex Media (746.9 KB)

Over time rarely it would succeed to claim but then it would start again failing to reclaim when the server restarts. It seems to be network issue cause even when once I managed to claim the server it had issue downloading some drivers

If someone can help of give guidance as to where I should look next that would be greatly appreciated !

[dane22]

No idea about why it would unclaim itself, but for the claiming part, try this:

[REL] ClaimIt

If you just installed a new Plex Media Server, but it can’t be found, or you simply can’t claim it, then this might be helpfull

[laaray]

Thanks vm for the prompt response, tried that and it fails, logs below:

Comparing entered passwords
Comparing entered passwords ok
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
Getting User Token from plex.tv ok
Getting PMS Claim Token
Getting PMS Claim Token ok
Claiming server
Fatal error happened
HTTP returned Status 500

rings a bell ?

[dane22]

Sadly not.

http error 500 means internal server error, so it can be everything.

And you used 127.0.0.1 as the IP address, correct?

[taproom]

My problem turned out to be with my Vonage Box. It was double NATing everything and I could not get through to claim the new server. To this day, I can’t figure out how the first Plex Server worked… Anyway, I moved the Vonage box behind my router (instead of before) and everything worked.

[laaray]

Thanks @dane22 appreciate the help, yes I was logged on the server itself but I also tried the local IP 192.168.1.11 and same results

[dane22]

You have network issues, where req. times out

Mar 25, 2019 19:00:39.648 [0x7fc4477fe700] DEBUG - HTTP simulating 408 after curl timeout

Your log is full of 408 errors, so maybe a routing, dns or proxy/firewall issue?

[laaray]

Thanks @taproom, I do not have double NAT, I can actually access my server fine by just port forwarding on my rooter which I would think would not work if there was anything in between double NATing is that right ?

@dane22 yeah i think you are right, I have turn off my firewall, i have played by turning on and off UPnP (logs attached) but still no luck, i have found the below related topics:

Plex Server not resolving hostnames

Oh meh again something seemed to fix it, I removed the dns servers in my DSM, saved, then filled them in exactly the same and saved settings. That seemed to have worked...

could not connect to 127.0.0.1:32400

Something is blocking it. It is normally some 3rd party security product or some proxy software or vpn software getting in the way.  Also at some point there was an Internet Options setting giving rise to such an error They are not easy to troubleshoot Try first to Reset the System and Framework Bundles in case it is a simple issue with the bundles. A selection of topics with such a problem https://forums.plex.tv/topic/109802-internet-page-error/ https://forums.plex.tv/topic/105299-plex-cha…

From the logsPlex Media (838.3 KB)
I see less issues resolving plex.tv but more reaching local host eg:

Request: [127.0.0.1:49838 (Loopback)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (4 live) GZIP

Mar 26, 2019 22:58:28.538 [0x7f12bbfff700] ERROR - Error issuing curl_easy_perform(handle): 28

Not sure why the setting network->List of IP addresses and networks that are allowed without auth, exactly do but I added local host 127.0.0.1 there but no luck neither

Any pointers at what to look at next ?

thanks very much !

[dane22]

@laaray

Any pointers at what to look at next ?

It’s most likely not a PMS issue, but something related to your OS and setup

Start by verifying, that it can browse to a site, by typing:
curl https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=debian&version=1.15.2.793-782228f99 in a terminal

And if that doesn’t work, check DNS settings, default router, and once more firewall

[laaray]

thanks I have tried that and it worked, even as plex user:

sudo -u plex curl “https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=debian&version=1.15.2.793-782228f99”

<?xml version=“1.0” encoding=“UTF-8”?>

<MediaContainer friendlyName=“myPlex” identifier=“com.plexapp.plugins.myplex” machineIdentifier=“9a72506b32433de1f4de5a04421902f96f58080c” size=“0” title=“Updates”>

</MediaContainer>

[laaray]

Also from running the bash script, you nicely provided, the output shows that I can get user and PMS claim token, so that means the PMS can access plex servers right ? That should roll out any DNS/rooter settings no ?

The issue seems to only be on the last step, which seems to post a request to the PMS itself and the response is either 500 or 401, the logs of the PMS when that happens nothing useful even in verbose mode.

[laaray]

Mmm I think I am onto something, when I try the curl query @dane22 requested above or any other that timeout on my logs they take roughly 16s to comeback on my server whereas from the logs timestamps the max time allowed seems below that.

So maybe it is a DNS issue its just the setting somehow on my linux server that causes resolution to be much slower, I ll keep looking in that direction.