Cannot Claim Plex Server on RaspBerryPi 3 [SOLVED]

Plex Media Server Desktops & Laptops
1

Server Version#: 1.15.3.876
Player Version#: Web PLayer
I had my Plex Server running on my RaspBerry Pi with no issues. But today I was trying to install a new external drive and move all my media to that new drive. After updating the Raspberry Pi I uninstalled the Plex Server because I saw the following message:

##### ATTENTION #####
THIS IS THE LAST UPDATE OF THE dev2day.de PACKAGE!!! UPDATE TO THE OFFICIAL
PACKAGE NOW!!!
Finally, official ARMv7 and ARMv8 Plex packages are available:
https://www.plex.tv/media-server-downloads/
The migration is simple and your Plex library will be preserved.
First, remove the dev2day.de package:
sudo apt-get remove plexmediaserver-installer
Then, remove the dev2day.de repo, e.g. with:
sudo rm /etc/apt/sources.list.d/pms.list
Now, download the appropriate package from https://www.plex.tv/media-server-downloads/ and put it on
your device, e.g.:
wget https://downloads.plex.tv/plex-media-server-new/1.15.3.876-
ad6e39743/debian/plexmediaserver_1.15.3.876-ad6e39743_armhf.deb
Finally, install the package, e.g.:
sudo dpkg -i plexmediaserver_1.15.3.876-ad6e39743_armhf.deb
Also, the official Plex repository is now available:

https://support.plex.tv/articles/235974187-enable-repository-updating-for-supported-linux-server-
distributions/

The following thread has more information: https://forums.plex.tv/t/read-me-first-about-server-armv7-
and-armv8-ubuntu-debian/226567/
Post your questions here: https://forums.plex.tv/tags/server-linux-arm
####################
Setting up libavdevice57:armhf (7:3.2.12-1~deb9u1+rpt1) ...
Setting up ssh (1:7.4p1-10+deb9u6) ...
Setting up ffmpeg (7:3.2.12-1~deb9u1+rpt1) ...
Setting up libav-tools (7:3.2.12-1~deb9u1+rpt1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for initramfs-tools (0.130) ...

But then I noticed that there are no Raspberry PI versions to download from https://www.plex.tv/media-server-downloads/
And that is why I decided to reinstall PMS from the dev2day repository. Nevertheless after reinstalling I get the following message:

image
image.jpg993×459 172 KB

I hit the Claim button but it does nothing after waiting for a while.

Can someone give me a hand with this issue?
here are the logs but I don´t know if I got the right file.
Plex Media Server Logs_2019-04-27_00-18-54.zip (827.6 KB)

Thank you very much in advance.

2

I really need some assistance here, it doesn’t matter If I have to recreate the server from scratch, as long as it works. Can anyone help me?

3

Ok, I was wrong when I said that there were no versions for the raspberry Pi at: https://www.plex.tv/media-server-downloads/
I read carefully again, downloaded the correct version and installed it following the instructions. Nevertheless after installing the correct version I still am getting the Claim server error:

image
image.jpg713×297 91.1 KB

And I don´t know how to fix this.

Any ideas?

Heres is the updated log file:
Plex Media Server Logs_2019-04-27_08-56-05.zip (963.8 KB)

Thank you very much in advance.

4

I decided to perform the setup again as completely new,

  1. stop plex
  2. sudo rm -rf /var/lib/plexmediaserver/Library
  3. start plex
  4. wait a moment (20 seconds) for the directories to be created and initial database to be created.

I did all this and even gave my server a new name this time. but I am still getting the same “Claim Server” message. After hitting the Claim button it begins processing but still cannot claim the server. Right now I am out of options.

Adding logs again this time after trying to do the claim:
Plex Media Server Logs_2019-04-27_10-16-06.zip (144.9 KB)

Hoping anyone could give me a hand…

5

That is usually a network problem. The logs indicate your server is unable to connect to plex.tv. Plex check the network connection of your RPi.

6

uglymagoo, thanks for replying but as you can see here:

image
image801×625 181 KB

My raspberry pi can connect to the internet just fine, and I can navigate plex.tv without any issues

7

If I ping www.plex.tv from the raspberry pi I get this:

image
image.png830×459 61.2 KB

I did notice that it takes a while to start getting some results, while if I do it from my windows PC it gets ping result immediately.

8

I think plex.tv and www.plex.tv are different, you may find that if you try to ping plex.tv you may not get a response (But I am not sure if they have disabled ping on plex.tv, so that does not really help)

Assuming you have curl on your pi, You could try this from your pi and see what happens:

curl https://plex.tv/api/claim/token?X-Plex-Token=1234X-Plex-Client-Identifier=1234

It will give an error if it works as the token and identifier are invalid values, but will at least check if it can access plex.tv

e.g.
<?xml version="1.0" encoding="UTF-8"?> <errors> <error>Invalid authentication token.</error> </errors>

9

Thanks for your reply blim5001, here is what I’ve got after running that command:

image
image826×92 13.1 KB

10

Ok, well that suggests (at least to me) that your Pi can get to plex.tv

I am not familiar with RaspBerryPi’s so am not sure if I can be of any more help.

But I wonder if it would be worth trying the claimit script:

11

Thank you very much for your reply blim5001, this is what I get after running that script:
image

Any ideas?

12

Could this be related to the fact that I am behind two routers?

My personal home router is connected to my ISP router.

13

No idea :frowning:

Looking at the script it appears to be getting all the info it needs from plex.tv but failing when it tries to send the info it has collected to your server to complete the claim (if i read the script correctly) as it makes a call here:

http://$1:32400/myplex/claim?token=$2&X-Plex-Client-Identifier=ClaimIt-$3&X-Plex-Token=$4

Where I think that $1 is replaced with the ip address of your server.

But this call is returning a 401 Unauthorized error

But what I don’t get is the script has to talk to your server in order to get the PMS Server Identifier

I guess so, but tbh not really sure. I might have expected the script to fail earlier, as it looks like it is getting the required data from both your server and plex.tv

Are both routers in router mode or is your isp router in bridge mode?

How does your Pi connect to the network?

14

It’s a fact that there is a problem with your network. As I have said above, your logs are full with (occasional?) network errors.

E.g.:

error issuing curl_easy_perform(handle): 28
Apr 27, 2019 10:05:46.985 [0x6cefe450] DEBUG - HTTP simulating 408 after curl timeout
Apr 27, 2019 10:05:46.986 [0x6cefe450] ERROR - AutoTagging: unable to retrieve updated word lists
Apr 27, 2019 10:05:47.429 [0x696f7450] ERROR - Error issuing curl_easy_perform(handle): 28
Apr 27, 2019 10:05:47.429 [0x696f7450] DEBUG - HTTP simulating 408 after curl timeout
Apr 27, 2019 10:05:47.430 [0x696f7450] WARN - [Analytics] Couldn't get analytics privacy settings. Trying again soon.
Apr 27, 2019 10:05:47.433 [0x696f7450] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
15

I fixed it!!!

I changed my dns server to 1.1.1.1 and 1.0.0.1 using

sudo nano /etc/dhcpcd.conf

and added the following line to that file:

static domain_name_servers=1.1.1.1 1.0.0.1

after that just do:

sudo service dhcpcd restart

And then I was able to claim the server

thanks everyone

16

Each server has a unique ID, and by fetching that, we make sure PMS is up and running, as well as we can access it, since we need that later for claiming. As a side note, we also use the identifier as a param towards plex.tv, since such a param is req. by their API

17

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