[Support] binhex - Plex


Recommended Posts

after reset password for security email from plex i cant claim the server i try all the guide from plex.tv and add CLAIM enviroment from docker but nothing

i try this script https://github.com/ukdtom/ClaimIt and send me this error

Validating IP address
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
Getting User Token from plex.tv ok
Getting PMS Claim Token
Getting PMS Claim Token ok
Claiming server
Fatal error happened
HTTP returned Status 401

someones can help me ?

Link to comment

btw few examples of people getting it claimed back in this other thread:
 



I for one had issues since my laptop and the server were on different subnets; was able to get it claimed via the web login for the server itself after getting on the same subnet and removing the variables from the xml file in the data folder as outlined in that other thread.

Link to comment
13 hours ago, stefan marton said:

after reset password for security email from plex i cant claim the server i try all the guide from plex.tv and add CLAIM enviroment from docker but nothing

i try this script https://github.com/ukdtom/ClaimIt and send me this error

Validating IP address
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
Getting User Token from plex.tv ok
Getting PMS Claim Token
Getting PMS Claim Token ok
Claiming server
Fatal error happened
HTTP returned Status 401

someones can help me ?

i have solved the solution with this method gain ID server to claim with : http://plexip:32400/identity

on : machineIdentifier="id server"

after from console i obtain my token with :

curl -X POST -i -k -L -s https://plex.tv/api/v2/users/signin --data-urlencode "login=your login" --data-urlencode "password=your password" --data-urlencode "X-Plex-Client-Identifier=ClaimIt-machine id" 

search string authToken= and you have your token

the edit file preference.xml on root docker folder and insert the token on

PlexOnlineToken="your_token"

restart docker and work

Link to comment
14 hours ago, stefan marton said:

after reset password for security email from plex i cant claim the server

ahh i get it now!, i wondered why my support threads were littered with claim issues! :-), interestingly i reset my password with no need to perform a claim of my server, it simply worked, maybe i got lucky?.

 

i will see if i can make claiming easier.

Link to comment

So I was also in the boat of I reset my password, and signed out everywhere, which kicked my Plex Docker server (binhex-plex) offline, and I could not claim it through the Plex settings like others had.

 

So what I did was:

  • ssh into my unraid server
  • get a claim code from https://www.plex.tv/claim/
  • run this command with that claim code: 
    curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'

After a few seconds, some XML was printed into my terminal (which you can ignore), and when I went back to https://app.plex.tv , my Plex server showed up again! All content was accessible again.

 

Thanks to this comment for the tips

  • Thanks 1
Link to comment
So I was also in the boat of I reset my password, and signed out everywhere, which kicked my Plex Docker server (binhex-plex) offline, and I could not claim it through the Plex settings like others had.
 
So what I did was:
  • ssh into my unraid server
  • get a claim code from https://www.plex.tv/claim/
  • run this command with that claim code: 
    curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-xxxxxxx'

After a few seconds, some XML was printed into my terminal (which you can ignore), and when I went back to https://app.plex.tv , my Plex server showed up again! All content was accessible again.
 
Thanks to this comment for the tips
Great post! This will definitely help me integrate claim support via env var

Sent from my 22021211RG using Tapatalk

Link to comment

Hi all, suddenlly my unraid becomes unresponsive, and my only solution was to force reset by reset button, but now I get this log and my plex doesn't open. All other docker container works. I really don't know what to do. 

 

2022-09-03 23:04:32.051539 [info] Host is running unRAID
2022-09-03 23:04:32.083017 [info] System information Linux Tower 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux
2022-09-03 23:04:32.118187 [info] OS_ARCH defined as 'x86-64'
2022-09-03 23:04:32.149139 [info] PUID defined as '99'
2022-09-03 23:04:32.313209 [info] PGID defined as '100'
2022-09-03 23:04:32.514503 [info] UMASK defined as '000'
2022-09-03 23:04:32.539509 [info] Permissions already set for '/config'
2022-09-03 23:04:32.581735 [info] Deleting files in /tmp (non recursive)...
2022-09-03 23:04:32.612209 [info] TRANS_DIR defined as '/config/transcode'
2022-09-03 23:04:32.675288 [info] Starting Supervisor...
2022-09-03 23:04:33,422 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2022-09-03 23:04:33,422 INFO Set uid to user 0 succeeded
2022-09-03 23:04:33,432 INFO supervisord started with pid 7
2022-09-03 23:04:34,434 INFO spawned: 'plexmediaserver' with pid 71
2022-09-03 23:04:34,434 INFO reaped unknown pid 8 (exit status 0)
2022-09-03 23:04:35,199 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23274824006864 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stdout)>
2022-09-03 23:04:35,199 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23274824439968 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stderr)>
2022-09-03 23:04:35,200 INFO exited: plexmediaserver (exit status 135; not expected)
2022-09-03 23:04:35,200 DEBG received SIGCHLD indicating a child quit
2022-09-03 23:04:36,204 INFO spawned: 'plexmediaserver' with pid 74
2022-09-03 23:04:36,229 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23274824005760 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stdout)>
2022-09-03 23:04:36,229 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23274824435024 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stderr)>
2022-09-03 23:04:36,229 INFO exited: plexmediaserver (exit status 135; not expected)
2022-09-03 23:04:36,230 DEBG received SIGCHLD indicating a child quit
2022-09-03 23:04:38,234 INFO spawned: 'plexmediaserver' with pid 77
2022-09-03 23:04:38,245 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23274824006864 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stdout)>
2022-09-03 23:04:38,245 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23274824440256 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stderr)>
2022-09-03 23:04:38,245 INFO exited: plexmediaserver (exit status 135; not expected)
2022-09-03 23:04:38,245 DEBG received SIGCHLD indicating a child quit
2022-09-03 23:04:41,252 INFO spawned: 'plexmediaserver' with pid 80
2022-09-03 23:04:41,274 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23274824005760 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stdout)>
2022-09-03 23:04:41,274 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23274824440448 for <Subprocess at 23274824434928 with name plexmediaserver in state STARTING> (stderr)>
2022-09-03 23:04:41,274 INFO exited: plexmediaserver (exit status 135; not expected)
2022-09-03 23:04:41,274 DEBG received SIGCHLD indicating a child quit
2022-09-03 23:04:42,275 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

Going through syslog I got that

Sep  4 00:03:02 Tower kernel: BTRFS warning (device sdf1): csum failed root 5 ino 33528 off 6229639168 csum 0x87b3c2ab expected csum 0x8723c2ab mirror 1
Sep  4 00:03:02 Tower kernel: BTRFS error (device sdf1): bdev /dev/sdf1 errs: wr 0, rd 0, flush 0, corrupt 375, gen 0
Sep  4 00:03:02 Tower kernel: blk_update_request: I/O error, dev loop2, sector 12167264 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sep  4 00:03:02 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 67, flush 0, corrupt 0, gen 0

Edited by jackfowl
Link to comment
On 8/4/2022 at 1:21 AM, Jacon said:

@binhex@SloppyG@thatsthefrickenlightning any updates on iGPU Intel transcoding?  i recently moved to a Haswell Xeon with quicksync.  Drivers are installed but would really like to keep Binhex container instead of moving to linux container

 

Sorry for the lateness of my reply. And I don't know, I haven't checked. Though if it's any consolation, the move to LSIO's container was very easy.

Link to comment
  • 4 weeks later...
  • 3 weeks later...

I've been following this thread on Plex's forums for a while now, in hopes that eventually my AMD APU could do gpu transcoding in plex, and it looks like there was  some recent progress on getting that working:

 

https://forums.plex.tv/t/got-hw-transcoding-to-work-with-libva-vaapi-on-ryzen-apu-ryzen-7-4700u/676546/310

 

I was wondering if there was an easy way to integrate the changes to get the amdgpu drivers working into this image, or if there is a guide somewhere for a straightforward way to port my plex library over to a new container

Link to comment
  • 3 weeks later...

Hi all.

 

I can see somebody had this problem before.

I just tryed to reset my password and make a new token claim (signed out of all devices)

Checked all portforward.

Very wird i have been running plex in windows for years and never had this problem before.

I know it is danish hope it is okay.

 

It is like unstable in the connection. Works from outside my lan, then it wont work. Then work. What good things cut i try?

Tryed with port 32400 and port 36000 - It ios like Plex is not lisiting on the port (from canyouseeme) 
Error: I could not see your service on X.X.X.X on port (36000)

 

image.thumb.png.0fa9f4c5c2bed64111dd321472857d94.png

 

 

Link to comment

My server crashes within a day whenever I start the Plex Docker container. I have rebuilt it as well as used every repo and they all act the same. regardless of passing through an NVIDIA GPU or not. The server seems to freeze, it will stay powered on but I cannot remote into it and nothing can access the file shares. it will crash anywhere between 1-17 ish hours i have only had it stay up for 24 hours once with plex running but it will stay up for at least a month with out plex running. that is with 7 minecraft server docker containers a nextcloud and database docker and sometimes an ark survival evolved docker so i dont think the issue is with docker. i also run a windows vm 24/7 i usually recycle it every month. if anyone knows how to help i would be much appreciated. 

Capture1.PNG

Capture2.PNG

tower-diagnostics-20221105-1357.zip syslog-192.168.0.211.log hardware.txt

Link to comment
15 hours ago, dnewb89 said:

My server crashes within a day whenever I start the Plex Docker container.

if you have a cache drive then change the path for /config from /mnt/user/appdata/plex/ to /mnt/cache/appdata/plex/, reason being that for a long time (maybe fixed recently i honestly dont know!) there has been an issue when targeting /mnt/user which can cause apps to crash and even bring down the entire array, i personally always target the cache drive directly as opposed to /mnt/user/ def worth a try!.

 

if that doesnt fix it then the next culprit would be memory, boot to MemTest and run it for AT LEAST 12 hours, ensure there are no errors.

Link to comment
8 hours ago, binhex said:

if you have a cache drive then change the path for /config from /mnt/user/appdata/plex/ to /mnt/cache/appdata/plex/, reason being that for a long time (maybe fixed recently i honestly dont know!) there has been an issue when targeting /mnt/user which can cause apps to crash and even bring down the entire array, i personally always target the cache drive directly as opposed to /mnt/user/ def worth a try!.

 

if that doesnt fix it then the next culprit would be memory, boot to MemTest and run it for AT LEAST 12 hours, ensure there are no errors.

I don't have a cash drive but i will do a mem test and get back to you thanks for the reply

Link to comment
On 11/8/2022 at 2:54 AM, binhex said:

if you have a cache drive then change the path for /config from /mnt/user/appdata/plex/ to /mnt/cache/appdata/plex/, reason being that for a long time (maybe fixed recently i honestly dont know!) there has been an issue when targeting /mnt/user which can cause apps to crash and even bring down the entire array, i personally always target the cache drive directly as opposed to /mnt/user/ def worth a try!.

 

if that doesnt fix it then the next culprit would be memory, boot to MemTest and run it for AT LEAST 12 hours, ensure there are no errors.

I haven't seen any errors in memtest and it's been running for just over 24 hours. Is there something that will stress it harder or will it not work without a cash drive

20221109_160817.jpg

Link to comment

I lost power yesterday and now none of my plex clients can connect to the server.  When I launch the WEBUI from inside the Docker tab in Unraid, I get "This site can't be reached"  

 

Is there something that needs to be reset?

 

The link it is trying to load is my server address:32400/web/index.html

 

Thanks,

Brian

Link to comment
On 11/8/2022 at 2:54 AM, binhex said:

if you have a cache drive then change the path for /config from /mnt/user/appdata/plex/ to /mnt/cache/appdata/plex/, reason being that for a long time (maybe fixed recently i honestly dont know!) there has been an issue when targeting /mnt/user which can cause apps to crash and even bring down the entire array, i personally always target the cache drive directly as opposed to /mnt/user/ def worth a try!.

 

if that doesnt fix it then the next culprit would be memory, boot to MemTest and run it for AT LEAST 12 hours, ensure there are no errors.

I bought a new drive as a cache drive and that seemed to fix the issue, the server and docker container have been up for 24 hours now. Thank you

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.