Getting Installation Error - Raspberry Pi 4

Plex Labs
1

I’ve installed Nodejs (12.22.12) and I’ve got Plex setup using this guide:

When running the command;

node js/index.js

It asks for a code. I go and grab the code but then I’m just hit with the error:

ACCOUNT: Refreshing data.
Auth: Got account data, not authorized.
Error exchanging claim token.

So I tried running it the second time and got something similar:

Exception claiming device. HTTP status 403
Error exchanging claim token.

I’m at a loss. What have I done wrong? :')
Thanks in advance,
~Blood

2

Grab the latest version linked in the release thread.

Seems like a core networking issue between the Pi and plex.tv, hard to say exactly what.

3

Updated to 4.4.0 like said. This time I got to the point where it was asking me to “give the player a name”.
However, right after that I just get the error message: “Error exchanging claim token.” again. Not sure why it’s having trouble getting the claim token.

Not sure if this actually got any further than the previous time.

Edit:
I’ve also made sure that the region/date and time are set correctly.

Code snippet from the command suggested below:

curl -v https://plex.tv
*   Trying 54.75.123.118:443...
* Connected to plex.tv (54.75.123.118) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=CH; ST=Nidwalden; L=Stans; O=Plex GmbH; CN=*.plex.tv
*  start date: Sep 14 00:00:00 2022 GMT
*  expire date: Sep 23 23:59:59 2023 GMT
*  subjectAltName: host "plex.tv" matched cert's "plex.tv"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55b33abce0)
> GET / HTTP/2
> Host: plex.tv
> user-agent: curl/7.74.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 302
< cache-control: no-cache
< content-type: text/html; charset=utf-8
< date: Mon, 10 Oct 2022 18:47:33 GMT
< location: https://www.plex.tv/
< referrer-policy: origin-when-cross-origin
< set-cookie: _my-plex_session_32=OVEzcGtRNE1BV1pPTWJwRTR4bDM3T2Q3dDJCUVVYSkZjM2hnWnlEd3M0RllGaitoTEZnZ1dzRVJwU29CNEM4dHFFU096ZVZzT0NudThWRnlJbW9zTlpNdEpBT01KTGdXMWtkUVpnQXNrS3A2OVdFQUZWSDNRSFB3S3pGOHcyZ3NMZGlIR0lsU0F6OFA4TElYZ1lyNGs4dU9aNEdhTHBSRHU4cVpvZjV3Zjg4PS0tS1JVTGMwdXh0NmMrN0pTZ1RhNE1JZz09--85c4abea2b14c24f326d3cbd18e7afca9162659c; path=/; HttpOnly; secure
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< vary: Origin
< x-content-type-options: nosniff
< x-frame-options: SAMEORIGIN
< x-request-id: d0297c5f-e38e-4da6-9216-064ae6a3e68f
< x-runtime: 0.005795
< x-xss-protection: 1; mode=block
<
* Connection #0 to host plex.tv left intact
<html><body>You are being <a href="https://www.plex.tv/">redirected</a>.</body></html>

~Blood

4

You should be able to find plexamp logs, zip and drop them into your reply for Elan.

At a terminal, maybe run this command and paste the output into a code block </> in your reply in order to verify that TLS connections, certs, and name resolution are okay.

curl -v https://plex.tv

When I roll a new 64bit raspbian lite, I sudo apt update, sudo apt full-upgrade, reboot, set locale, TZ, hostname, WiFi country, static IP, DNS servers 1.1.1.1 and 9.9.9.9, hostname, reboot, node, and plexamp.

just saw your edit how you did a bunch of those :slight_smile:

1 Like
5

Only thing I don’t have is the DNS servers, trying to hold off those for now, I’m wanting to setup Pihole on another Pi before touching anything like this.

But thanks for the suggestion I’ve added it to the other reply I made earlier, seems all good to me, but then again I’ve only started using this recently.

6

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