Impossible to claming server - Connexion plex.tv refused

Plex Media Server
1

Server Version#: 1.25.2.5319
Player Version#:
HI,
I can’t claiming my plex server , it’s seems impossible to connect at plex.tv.

curl -vvvv https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt

  • Hostname was NOT found in DNS cache
  • Trying 52.18.69.157…
  • connect to 52.18.69.157 port 443 failed: Connexion refusée
  • Failed to connect to plex.tv port 443: Connexion refusée
  • Closing connection 0
    curl: (7) Failed to connect to plex.tv port 443: Connexion refusée

LOG :
Dec 18, 2021 09:00:40.412 [0x7f92b7b1db38] DEBUG - Request: [127.0.0.1:33472 (Loopback)] POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxx1i
bmnN (10 live) GZIP
Dec 18, 2021 09:00:40.412 [0x7f92b7b1db38] DEBUG - HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxx1ib
mnN
Dec 18, 2021 09:00:40.412 [0x7f92b7b1db38] ERROR - Error issuing curl_easy_perform(handle): 7
Dec 18, 2021 09:00:40.412 [0x7f92b7b1db38] WARN - HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxx
xx1ibmnN (7, Couldn’t connect to server) (Failed to connect to plex.tv port 443: Connection refused)
Dec 18, 2021 09:00:40.412 [0x7f92b7b1db38] DEBUG - MyPlex: Did token exchange for claim (returnCode: -7)
Dec 18, 2021 09:00:40.413 [0x7f92b7b1db38] DEBUG - MyPlex: Got a token poked, let’s act on it.
Dec 18, 2021 09:00:40.413 [0x7f92b7b1db38] DEBUG - HTTP requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=
Dec 18, 2021 09:00:40.413 [0x7f92b7b1db38] ERROR - Error issuing curl_easy_perform(handle): 7
Dec 18, 2021 09:00:40.413 [0x7f92b7b1db38] WARN - HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxx
xxxxxxxxxt to server) (Failed to connect to plex.tv port 443: Connection refused)
Dec 18, 2021 09:00:40.413 [0x7f92b7b1db38] WARN - [Analytics] Couldn’t get analytics privacy settings. Trying again soon.
Dec 18, 2021 09:00:40.413 [0x7f92b7b1db38] DEBUG - HTTP requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] ERROR - Error issuing curl_easy_perform(handle): 7
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] WARN - HTTP error requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xxxxxxx
xxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443: Connection refused)
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] WARN - [AutoUpdateRequestHandler] Couldn’t get update channels. Trying again soon.
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] ERROR - Error issuing curl_easy_perform(handle): 7
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] WARN - HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxx
xxxxxt to server) (Failed to connect to plex.tv port 443: Connection refused)
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] WARN - FeatureManager: Couldn’t get features. Trying again soon.
Dec 18, 2021 09:00:40.414 [0x7f92b7b1db38] DEBUG - Sync: onMyPlexSignOut
Dec 18, 2021 09:00:40.415 [0x7f92b8330b38] DEBUG - Completed: [127.0.0.1:33472] 500 POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxx1ibmnN
(10 live) GZIP 3ms 532 bytes (pipelined: 2)
Dec 18, 2021 09:00:40.433 [0x7f92b80cab38] DEBUG - [MediaProviderManager] we had 1 cloud providers online, we now have 1
Dec 18, 2021 09:00:40.433 [0x7f92b80cab38] DEBUG - [MediaProviderManager] cloud provider (Metadata) is online and available
Dec 18, 2021 09:00:44.065 [0x7f92b8330b38] DEBUG - Completed: [127.0.0.1:33470] 200 GET /player/proxy/poll?deviceClass=pc&protocolVersio
n=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (10 live) GZIP 20000ms 5 bytes (pipelined: 1)
Dec 18, 2021 09:00:44.197 [0x7f92b7b1db38] DEBUG - Request: [127.0.0.1:33472 (Loopback)] GET /player/proxy/poll?deviceClass=pc&protocolV
ersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (9 live) GZIP
Dec 18, 2021 09:00:44.198 [0x7f92b7b1db38] DEBUG - Content-Length is -1 (of total: -1).

Could you help me ??

Thx !

:

2

Is your server on a remote VPS or local to your home ?

If the server is your workstation, use http://127.0.0.1:32400/web to claim it.
If it is on your home LAN, use the LAN IP address http://LAN.IP.of.Server:32400/web
(LAN must also be compliant with RFC-1918 192.168.x.x,10.x.x.x, or 172.16…x.x->172.31.x.x)

4

mir0of

1m

My server is on remote server.
I use tunnel ssh to connect in localhost in my workstation and claim it.

ssh root@remotPlex -L 8080:localhost:32400

I have no proxy ans no firewall in my server

I joined you a screenshot in my workstation with console activate.

image
image943×530 118 KB

5

Hi,

We are using this server with Miroof (OP) for a while now. As we can see in the log, the server got a connection refused by plex.tv but the DNS resolution is okay and the Internet access is working aswell.

If I run a curl from a different public IP :

curl -vvvv https://plex.tv/api/v2/user/

  • Trying 52.18.69.157:443…
  • Connected to plex.tv (52.18.69.157) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • successfully set certificate verify locations:
  • CAfile: /etc/ssl/cert.pem
  • CApath: none
  • TLSv1.2 (OUT), TLS handshake, Client hello (1):
  • TLSv1.2 (IN), TLS handshake, Server hello (2):
  • TLSv1.2 (IN), TLS handshake, Certificate (11):
  • TLSv1.2 (IN), TLS handshake, Server key exchange (12):
  • TLSv1.2 (IN), TLS handshake, Server finished (14):
  • TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
  • TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.2 (OUT), TLS handshake, Finished (20):
  • TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
  • TLSv1.2 (IN), TLS handshake, Finished (20):
  • SSL connection using TLSv1.2 / ECDHE-RSA-AES128-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 22 00:00:00 2021 GMT
  • expire date: Sep 22 23:59:59 2022 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 0x7f860b00c800)

GET /api/v2/user/ HTTP/2
Host: plex.tv
user-agent: curl/7.77.0
accept: /

  • Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
    < HTTP/2 401
    < cache-control: no-cache
    < content-type: application/xml
    < date: Sat, 18 Dec 2021 10:35:00 GMT
    < referrer-policy: origin-when-cross-origin
    < set-cookie: _my-plex_session_32=T21qNEdIK0l0bmFjL3NxeFc0Yzl6UUZ2SUQ1SDBSQTlWanZvTmZ1VGJpS3dubjFQdnVyaGdIbmI4cnVmblBvQm1yU0JBb1MwaTV3RTBGQmFVbU85cGc9PS0tVHZlRTB4NTBYR3dTeWRyRGFTMDJDQT09–e074010e9acc16a8e69bfdde9a3923a5c965470c; 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: 25de5816-90db-4c81-800e-3d3c43ee3ba4
    < x-runtime: 0.003703
    < x-xss-protection: 1; mode=block
    <
<?xml version="1.0" encoding="UTF-8"?> * Connection #0 to host plex.tv left intact

Please advice

6

Also, it looks like the same issue related in that post SSL Certificate error

Could you reset the Miroof’s certificate ?

Thank you

1 Like
7

@brunobruno

Certificate is valid:

Valid	Tue, 16 Nov 2021 11:11:32 +0000	Tue, 16 Nov 2021 11:11:47 +0000

Server certificate:
subject: C=CH; ST=Nidwalden; L=Stans; O=Plex GmbH; CN=*.plex.tv
start date: Sep 22 00:00:00 2021 GMT
expire date: Sep 22 23:59:59 2022 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.

Actual error: HTTP 401 - Account authentication error

HTTP/2 401

Step 1 -

  1. Stop Plex
  2. Open file “Preferences.xml”
  3. Inspect value for PlexOnlineToken="value"
  4. If the value is null – PlexOnlineToken="" – then local error caused the failure.
  5. Carefully edit (remove) PlexOnlineToken="" from file and save.
  6. Verify file owned as plex:plex (or username being run as)
  7. If Token value was null, restart plex and reclaim.

Step 2 -

  1. Are you using your own certificate on the host before claiming ?
  2. Are you using a proxy with certificate ?
8

Hi,

@ChuckPa , the curl’s test of @brunobruno is made on his PC, not in PMS server.

In the PMS server when i do a curl command. The connexion is refused by plex.tv !

curl -v https://plex.tv

  • Rebuilt URL to: https://plex.tv/
  • Hostname was NOT found in DNS cache
  • Trying 52.48.253.46…
  • connect to 52.48.253.46 port 443 failed: Connexion refused
  • Trying 52.18.69.157…
  • connect to 52.18.69.157 port 443 failed: Connexion refused
  • Failed to connect to plex.tv port 443: Connexion refused
  • Closing connection 0
    curl: (7) Failed to connect to plex.tv port 443: Connexion refused
9

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