hassio-addons/addon-plex

after update to 3.1.1 plex won't start anymore

dominiquevocat opened this issue · 7 comments

dominiquevocat commented

Problem/Motivation

after upgrade to 3.1.1 plex won't start anymore

Expected behavior

plex just runs

Actual behavior

borks out in plex/rootfs/etc/cont-init.d/plex.sh in line 59

Steps to reproduce

update plex to 3.1.1

Proposed changes

the file claim_code was empty and the curl did not deliver any usefull result causing plex not to run.

  • redacted output of the curl line with -v :

root@blackbox:~# curl -v --write-out '\n%{http_code}' --request POST -H "X-Plex-Client-Identifier: xxxxxxxxxxxxxx" -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=claim-xxxxxxxxx"

  • Trying 54.229.236.47:443...
  • Connected to plex.tv (54.229.236.47) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
  • TLSv1.0 (OUT), TLS header, Certificate Status (22):
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • TLSv1.2 (IN), TLS header, Certificate Status (22):
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.2 (IN), TLS header, Finished (20):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.2 (OUT), TLS header, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • 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 multiplexing
  • Connection state changed (HTTP/2 confirmed)
  • Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • Using Stream ID: 1 (easy handle 0x562f336b7930)
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):

POST /api/claim/exchange?token=claim-xxxxxxxxxxxxx HTTP/2
Host: plex.tv
user-agent: curl/7.81.0
accept: /
x-plex-client-identifier: xxxxxxxxxxxxxxxxxxx
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

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
  • TLSv1.2 (OUT), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
    < HTTP/2 403
    < cache-control: no-cache
    < content-type: application/xml
    < date: Tue, 20 Sep 2022 20:44:05 GMT
    < referrer-policy: origin-when-cross-origin
    < strict-transport-security: max-age=31536000; includeSubDomains; preload
    < vary: Origin
    < x-content-type-options: nosniff
    < x-frame-options: SAMEORIGIN
    < x-request-id: b4788fc1-1b9c-4802-a37e-a11685efdc70
    < x-runtime: 0.175935
    < x-xss-protection: 1; mode=block
    <
  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • Connection #0 to host plex.tv left intact
AlecRust commented

You have already tried with a new claim code from https://www.plex.tv/claim right?

emre299 commented

After the update, I also do not open plex. Does it give an error about "port 1900"

#169

guiofranca commented

I've had the same problem. The log mentions to update the claim code so I did it. No good. Then I had to rollback to 3.1.0 and it's working again. I also disabled auto updates for this addon.

michelebossa commented

Hello i have changed the claim code and it is worked for me.

tbaumann commented

Same happened to me. It was really obscure. I could see no logs. The docker container stopped very shortly.

Saw this here, got a new claim code and it's running again.

chrisghz commented

I have the same issue with this new update! Rolled back to 3.1.0 and its all working again. Do we know if there is going to be a fix for this?

github-actions commented

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!