Unable to claim server using plexinc/pms-docker

Plex Media Server NAS & Devices
1

Hello

I’m trying to set up a plex server using the official docker image

Here is the command I’m using

 docker run \
  --name plex \
  --network=host \
  -e TZ="Asia/Bangkok" \
  -e PLEX_CLAIM="__REMOVED__" \
  -v $PWD/plex/config:/config \
  -v /tmp/transcode:/transcode \
  -v $PWD/media:/data \
  plexinc/pms-docker

I’ve tried several times with varying configurations with no luck

Here is the debug output from cont-init.d/40-plex-first-run

Attempting to obtain server token from claim token
+ echo 'Attempting to obtain server token from claim token'
++ curl --verbose -X POST -H 'X-Plex-Client-Identifier: __REMOVED__' -H 'X-Plex-Product: Plex Media Server' -H 'X-Plex-Version: 1.1' -H 'X-Plex-Provides: server' -H 'X-Plex-Platform:
Linux' -H 'X-Plex-Platform-Version: 1.0' -H 'X-Plex-Device-Name: PlexMediaServer' -H 'X-Plex-Device: Linux' 'https://plex.tv/api/claim/exchange?token=__REMOVED__'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 52.208.108.2...
* Connected to plex.tv (52.208.108.2) port 443 (#0)
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 592 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
*        server certificate verification OK
*        server certificate status verification SKIPPED
*        common name: *.plex.tv (matched)
*        server certificate expiration date OK
*        server certificate activation date OK
*        certificate public key: RSA
*        certificate version: #3
*        subject: C=US,ST=California,L=Los Gatos,O=Plex\, Inc,CN=*.plex.tv
*        start date: Fri, 10 Feb 2017 00:00:00 GMT
*        expire date: Sun, 10 May 2020 12:00:00 GMT
*        issuer: C=US,O=DigiCert Inc,CN=DigiCert SHA2 Secure Server CA
*        compression: NULL
* ALPN, server did not agree to a protocol
> POST /api/claim/exchange?token=REMOVED HTTP/1.1
> Host: plex.tv
> User-Agent: curl/7.47.0
> Accept: */*
> X-Plex-Client-Identifier: __REMOVED__
> X-Plex-Product: Plex Media Server
> X-Plex-Version: 1.1
> X-Plex-Provides: server
> X-Plex-Platform: Linux
> X-Plex-Platform-Version: 1.0
> X-Plex-Device-Name: PlexMediaServer
> X-Plex-Device: Linux
>
< HTTP/1.1 403 Forbidden
< Cache-Control: no-cache
< Content-Type: application/xml
< Date: Thu, 03 May 2018 10:37:17 GMT
< Referrer-Policy: origin-when-cross-origin
< Server: nginx
< Set-Cookie: _mkra_ctxt=ee2ca4644dda1f2b8e3affb179ffc4ab--403; path=/; max-age=5; secure
< Strict-Transport-Security: max-age=0
< Vary: Origin
< X-Content-Type-Options: nosniff
< X-Frame-Options: DENY
< X-Request-Id: d6dd5ad3-3c6d-4d24-9947-ddd27a5a7336
< X-Runtime: 0.017485
< X-UA-Compatible: chrome=1
< X-XSS-Protection: 1; mode=block
< Content-Length: 1
< Connection: keep-alive
<
{ [1 bytes data]
100     1  100     1    0     0      2      0 --:--:-- --:--:-- --:--:--     2
* Connection #0 to host plex.tv left intact

I’m getting 403 forbidden from the claim API. I’ve tried several times, with different network settings, ensuring to build with an empty plex/config directory and not using cache from previous docker builds

I’m attempting to set this up on a Centos 7 dedicated server. I can provide additional details to help diagnose, but I’m really struggling to figure out why I’m unable to claim the server

The end result is, the docker container successfully runs, and I’m able to access the web ui, but I get stuck with “search for server” and I am missing the “server” option in the settings page.

Halp please

1 Like
2

The tokens obtained from https://www.plex.tv/claim/ expire in a few minutes. The page there tells you how long the claim token will last. Most likely your claim token expired.

3

I saw that the tokens expire in 4 minutes. I tried several times with slight variations on config. Most within a minute of generating a token. I get 403 consistently, this is 100% not due to the token expiring

4

I know this is an old thread but I am having the same issue. Been playing with this for about 4 hours. Can’t figure out how to tunnel in from windows to linux/docker/contianer to get this working either.

2 Likes
5

I have the same issue since a couple of days. Is there a solution for this?