Jump to content
binhex

[Support] binhex - Plex

164 posts in this topic Last Reply

Recommended Posts

I wanted to add something else.  Two different forum posts have found issues with the latest version.  One said AC3 was broken on Chromecast and another stated something like anything lower than Roku4 had audio issues I believe.  Is it possible to add something to specify which version to install?  I think other threads have made mention of this or the ability to roll back.  Thanks again.

Share this post


Link to post

Sorry if I missed it but is there a way to update this via the web gui or do we wait for you to update the docker?  It says version 1.2.6.2975 is out and to install it manually.  That leads to an *.rpm download on my windows machine which I don't think I can apply to the docker myself.  Thanks.

 

See Q10 - http://lime-technology.com/forum/index.php?topic=45811.msg437673#msg437673

Share this post


Link to post

I wanted to add something else.  Two different forum posts have found issues with the latest version.  One said AC3 was broken on Chromecast and another stated something like anything lower than Roku4 had audio issues I believe.  Is it possible to add something to specify which version to install?  I think other threads have made mention of this or the ability to roll back.  Thanks again.

 

See Q11 - http://lime-technology.com/forum/index.php?topic=45811.msg437673#msg437673

Share this post


Link to post

Hi there

 

Great docker as usual. Working flawlessly.

 

Is there a way to update plex inside the docker or is that done where ever the docker is pulled from.

 

I only ask as it says i am running 1.3.4.3285 and is up to date and 1.4.1 has been released which now includes the dvr functionality.

 

Thanks

Share this post


Link to post
On 20/02/2017 at 1:33 AM, Stealth1081 said:

Hi there

 

Great docker as usual. Working flawlessly.

 

Is there a way to update plex inside the docker or is that done where ever the docker is pulled from.

 

I only ask as it says i am running 1.3.4.3285 and is up to date and 1.4.1 has been released which now includes the dvr functionality.

 

Thanks

You are running the latest version of PMS, you're on about the plex pass edition, which is always ahead of plex, i also have a docker image for that.

Share this post


Link to post
12 hours ago, binhex said:

You are running the latest version of PMS, you're on about the plex pass edition, which is always ahead of plex, i also have a docker image for that.

 

O.k. thanks for the reply, i didn't know that. I have plex pass, is there an easy way to install the plex pass docker then migrate the plex server settings, meta data and all that or will i need to rebuild from scratch. Or just update the current docker to pull from the plex pass repo.

Share this post


Link to post
On 21/02/2017 at 10:57 PM, Stealth1081 said:

 

O.k. thanks for the reply, i didn't know that. I have plex pass, is there an easy way to install the plex pass docker then migrate the plex server settings, meta data and all that or will i need to rebuild from scratch. Or just update the current docker to pull from the plex pass repo.

 

Sorry for the delay in getting back to you, ok you should be able to do the following:-

 

1. Stop plex container

2. Copy the entire config folder for plex (this will take a considerable amount of time), this will allow you to roll back to the previous container if things dont pan out too well, example command below:-

 

cp -r /mnt/cache/appdata/config/plex /mnt/cache/appdata/config/plex-pass

 

3. Once the copy has finished, create the new plex-pass container, define it EXACTLY the same as the plex one APART from give it the path to the new copied config folder, e.g. /mnt/cache/appdata/config/plex-pass

4. Start the container, you should find all your metadata is picked up correctly.

5. If things dont go to plan then simply stop the plex-pass container, and start the original plex container.

Edited by binhex

Share this post


Link to post

Can anyone tell me what this means?

 

Mar  5 02:51:47 TheDeathStar kernel: Plex Media Scan[9285]: segfault at 0 ip           (null) sp 00002b7f3b3978d8 error 14 in Plex Media Scanner[400000+42e000]
Mar  5 02:51:55 TheDeathStar kernel: Plex Media Scan[10322]: segfault at 0 ip           (null) sp 00002abf6b3978d8 error 14 in Plex Media Scanner[400000+42e000]
Mar  5 02:52:05 TheDeathStar kernel: Plex Media Scan[11358]: segfault at 0 ip           (null) sp 00002b822e3978d8 error 14 in Plex Media Scanner[400000+42e000]
Mar  5 02:52:23 TheDeathStar kernel: Plex Media Scan[13219]: segfault at 0 ip           (null) sp 00002b3426dff8d8 error 14 in Plex Media Scanner[400000+42e000]

Share this post


Link to post
5 minutes ago, xhaloz said:

Can anyone tell me what this means?

 


Mar  5 02:51:47 TheDeathStar kernel: Plex Media Scan[9285]: segfault at 0 ip           (null) sp 00002b7f3b3978d8 error 14 in Plex Media Scanner[400000+42e000]
Mar  5 02:51:55 TheDeathStar kernel: Plex Media Scan[10322]: segfault at 0 ip           (null) sp 00002abf6b3978d8 error 14 in Plex Media Scanner[400000+42e000]
Mar  5 02:52:05 TheDeathStar kernel: Plex Media Scan[11358]: segfault at 0 ip           (null) sp 00002b822e3978d8 error 14 in Plex Media Scanner[400000+42e000]
Mar  5 02:52:23 TheDeathStar kernel: Plex Media Scan[13219]: segfault at 0 ip           (null) sp 00002b3426dff8d8 error 14 in Plex Media Scanner[400000+42e000]

Usually indicates an error in the app itself (not the docker per se).  Probably best to post on the Plex forum if its causing problems.  Can occasionally also indicate bad RAM

Edited by Squid

Share this post


Link to post
5 minutes ago, Squid said:

Usually indicates an error in the app itself (not the docker per se).  Probably best to post on the Plex forum if its causing problems.  Can occasionally also indicate bad RAM

Awesome I will post there.  I did a memtest for 30 hours last week with no errors.

Share this post


Link to post
On 24/02/2017 at 10:25 AM, binhex said:

 

Sorry for the delay in getting back to you, ok you should be able to do the following:-

 

1. Stop plex container

2. Copy the entire config folder for plex (this will take a considerable amount of time), this will allow you to roll back to the previous container if things dont pan out too well, example command below:-

 


cp -r /mnt/cache/appdata/config/plex /mnt/cache/appdata/config/plex-pass

 

3. Once the copy has finished, create the new plex-pass container, define it EXACTLY the same as the plex one APART from give it the path to the new copied config folder, e.g. /mnt/cache/appdata/config/plex-pass

4. Start the container, you should find all your metadata is picked up correctly.

5. If things dont go to plan then simply stop the plex-pass container, and start the original plex container.

Thanks for the reply. I didn't get a notification that you responded. 

 

I try this tomorrow and report back. 

Share this post


Link to post
On 24/02/2017 at 10:25 AM, binhex said:

 

Sorry for the delay in getting back to you, ok you should be able to do the following:-

 

1. Stop plex container

2. Copy the entire config folder for plex (this will take a considerable amount of time), this will allow you to roll back to the previous container if things dont pan out too well, example command below:-

 


cp -r /mnt/cache/appdata/config/plex /mnt/cache/appdata/config/plex-pass

 

3. Once the copy has finished, create the new plex-pass container, define it EXACTLY the same as the plex one APART from give it the path to the new copied config folder, e.g. /mnt/cache/appdata/config/plex-pass

4. Start the container, you should find all your metadata is picked up correctly.

5. If things dont go to plan then simply stop the plex-pass container, and start the original plex container.

 

 

Just completed the migration to the plex pass docker, no errors in the log looks like it went off without a hitch.

 

Thanks for your easy to follow guide.

 

Cheers

Share this post


Link to post

I cannot get any plex docker to run as a media server. When it starts it runs as if it's a client, not a server.

If I install the windows version I can set that up on my laptop, but in no way can I get any one of the docker containers to run as a server. Seems to come up as if its a client device instead.

Edited by eagle470

Share this post


Link to post
I cannot get any plex docker to run as a media server. When it starts it runs as if it's a client, not a server.
If I install the windows version I can set that up on my laptop, but in no way can I get any one of the docker containers to run as a server. Seems to come up as if its a client device instead.

I need a lot more into than that, I need screenshots of what you think youre seeing, I need the log file from /config/supervisord.log and any other info you think is relevant.

Sent from my SM-G900F using Tapatalk

Share this post


Link to post

Sorry about the lack of details, here is a reddit thread that I followed to no avail

 

at the bottom is a .7z of the docker folder

 

2017-05-28 15_58_06-unraid1_UpdateContainer.png

2017-05-28 16_15_36-Plex.png

2017-05-28 16_16_16-Plex.png

binhex-plex.7z

Edited by eagle470

Share this post


Link to post
17 hours ago, eagle470 said:

Sorry about the lack of details, here is a reddit thread that I followed to no avail

 

at the bottom is a .7z of the docker folder

 

2017-05-28 15_58_06-unraid1_UpdateContainer.png

2017-05-28 16_15_36-Plex.png

2017-05-28 16_16_16-Plex.png

binhex-plex.7z

 

those screenshots are of course not for my docker image (official plex docker image i think), but that aside, once the container is succesfully started (check logs) then you would then need to setup the server locally by going to the following url on a machine connected to your lan (not over the internet):-

 

http://<your_hosts_ip_address>:32400/web

if you cant connect to the server using the above url then you have bigger issues with configuring the docker container which you will need to fix, if you can connect then configure the server and finally either use uPnP on your router and let plex configure the port forward for you, or manually setup port forwarding on your router and manually configure plex to use the defined port, the decision is yours.

 

 

 

Share this post


Link to post

as my previous post states, this is NOT an issue with the container, this is purely down to configuration of your router, you need to:-

 

if you can connect then configure the server and finally either use uPnP on your router and let plex configure the port forward for you, or manually setup port forwarding on your router and manually configure plex to use the defined port, the decision is yours.

 

This might help:- https://support.plex.tv/hc/en-us/articles/200484543

Edited by binhex

Share this post


Link to post
On 2/24/2017 at 3:25 AM, binhex said:

 

Sorry for the delay in getting back to you, ok you should be able to do the following:-

 

1. Stop plex container

2. Copy the entire config folder for plex (this will take a considerable amount of time), this will allow you to roll back to the previous container if things dont pan out too well, example command below:-

 


cp -r /mnt/cache/appdata/config/plex /mnt/cache/appdata/config/plex-pass

 

3. Once the copy has finished, create the new plex-pass container, define it EXACTLY the same as the plex one APART from give it the path to the new copied config folder, e.g. /mnt/cache/appdata/config/plex-pass

4. Start the container, you should find all your metadata is picked up correctly.

5. If things dont go to plan then simply stop the plex-pass container, and start the original plex container.

This didn't work for me... I tried it multiple times. It would just create a new folder called Plex Media Server

Is there a work around?

 

Shows the newest one is 1.9.0.4252 and that I am on Version 1.8.4.4249. I was on the most recent before switching from the plug in that was giving me trouble to the dockers. I am hoping that wont cause me more problems.

 

Edited by UtahDeLorean

Share this post


Link to post

"There was an unexpected error loading the dashboard"

 

This is how it's starting up today- It HAD been loading correctly, so it's obviously taken a step backwards. My situation:

 

New install. Public PLEX version. Binhex docker on Unraid 6.35 system. System doesn't seem to be updating the libraries as episodes are added, though it did spend a few days doing nothing but scanning/updating the libraries...just no sign of episodes added to my server in the last few days. Search function sporadically works. Seldom loads the seasons once you select a series.  Nothing looks wrong or presents any sort of outward appearance of malfunction- but PLEX just seems brain-dead.  I've stopped and restarted the docker.  Really need some direction- I know almost nothing about dockers.

 

UPDATE 10/31:  Eventual resolution:  I deleted and reinstalled the docker.  I'm guessing the container became filled with logs, but I didn't know how to tell. 

Edited by johnny121b
Fixed the problem myself

Share this post


Link to post
When updating PLEX, is it best to
 
  • Update the docker or
  • Update PLEX from within the WebUI
??
Always always update the docker image, do not use the built in updater in the app

Sent from my SM-G935F using Tapatalk

  • Like 1

Share this post


Link to post

Hello everybody!

 

I am unable to reach plex from any device, this is for more plex containers but I use this one (binhex) for nearly a year.

 

I tried a few things but can't get it to work unfortunately :(.

 

This error message appears in Chrome if I want to access the webUI:

This site can't be reached

192.168.1.146 refused to connect

ERR_CONNECTION_REFUSED

 

IP is 192.168.1.146:32400

 

Following the Docker Log:

2018-02-04 18:42:29.400597 [info] Host is running unRAID
2018-02-04 18:42:29.420066 [info] System information Linux 764ac0a2e3f6 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-02-04 18:42:29.441691 [info] PUID defined as '99'
2018-02-04 18:42:29.471624 [info] PGID defined as '100'
2018-02-04 18:42:29.567938 [info] UMASK defined as '000'
2018-02-04 18:42:29.586507 [info] Permissions already set for volume mappings
2018-02-04 18:42:29.603815 [info] TRANS_DIR defined as '/config/transcode'
2018-02-04 18:42:29.654874 [info] Starting Supervisor...
2018-02-04 18:42:29,753 CRIT Set uid to user 0
2018-02-04 18:42:29,753 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-02-04 18:42:29,756 INFO supervisord started with pid 7
2018-02-04 18:42:30,758 INFO spawned: 'plexmediaserver' with pid 48
2018-02-04 18:42:30,758 INFO reaped unknown pid 8
2018-02-04 18:42:30,904 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785500744088 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:30,904 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785510353952 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:30,904 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:30,905 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:31,906 INFO spawned: 'plexmediaserver' with pid 51
2018-02-04 18:42:32,005 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785500893696 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:32,005 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785491775928 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:32,006 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:32,006 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:34,008 INFO spawned: 'plexmediaserver' with pid 54
2018-02-04 18:42:34,116 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785510353664 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:34,116 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785500893696 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:34,116 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:34,116 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:37,119 INFO spawned: 'plexmediaserver' with pid 57
2018-02-04 18:42:37,219 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785510353664 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:37,220 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785491775928 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:37,220 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:37,220 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:37,119 INFO spawned: 'plexmediaserver' with pid 57
2018-02-04 18:42:37,219 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785510353664 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:37,220 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785491775928 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:37,220 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:37,220 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:38,221 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

I hope someone can help me! 

 

Thank you very much in advance!

 

Edited by TomSerious

Share this post


Link to post
On 2/4/2018 at 11:52 AM, TomSerious said:

Hello everybody!

 

I am unable to reach plex from any device, this is for more plex containers but I use this one (binhex) for nearly a year.

 

I tried a few things but can't get it to work unfortunately :(.

 

This error message appears in Chrome if I want to access the webUI:

This site can't be reached

192.168.1.146 refused to connect

ERR_CONNECTION_REFUSED

 

IP is 192.168.1.146:32400

 

Following the Docker Log:


2018-02-04 18:42:29.400597 [info] Host is running unRAID
2018-02-04 18:42:29.420066 [info] System information Linux 764ac0a2e3f6 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-02-04 18:42:29.441691 [info] PUID defined as '99'
2018-02-04 18:42:29.471624 [info] PGID defined as '100'
2018-02-04 18:42:29.567938 [info] UMASK defined as '000'
2018-02-04 18:42:29.586507 [info] Permissions already set for volume mappings
2018-02-04 18:42:29.603815 [info] TRANS_DIR defined as '/config/transcode'
2018-02-04 18:42:29.654874 [info] Starting Supervisor...
2018-02-04 18:42:29,753 CRIT Set uid to user 0
2018-02-04 18:42:29,753 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-02-04 18:42:29,756 INFO supervisord started with pid 7
2018-02-04 18:42:30,758 INFO spawned: 'plexmediaserver' with pid 48
2018-02-04 18:42:30,758 INFO reaped unknown pid 8
2018-02-04 18:42:30,904 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785500744088 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:30,904 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785510353952 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:30,904 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:30,905 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:31,906 INFO spawned: 'plexmediaserver' with pid 51
2018-02-04 18:42:32,005 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785500893696 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:32,005 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785491775928 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:32,006 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:32,006 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:34,008 INFO spawned: 'plexmediaserver' with pid 54
2018-02-04 18:42:34,116 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785510353664 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:34,116 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785500893696 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:34,116 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:34,116 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:37,119 INFO spawned: 'plexmediaserver' with pid 57
2018-02-04 18:42:37,219 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785510353664 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:37,220 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785491775928 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:37,220 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:37,220 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:37,119 INFO spawned: 'plexmediaserver' with pid 57
2018-02-04 18:42:37,219 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22785510353664 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stdout)>
2018-02-04 18:42:37,220 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22785491775928 for <Subprocess at 22785500742144 with name plexmediaserver in state STARTING> (stderr)>
2018-02-04 18:42:37,220 INFO exited: plexmediaserver (exit status 255; not expected)
2018-02-04 18:42:37,220 DEBG received SIGCLD indicating a child quit
2018-02-04 18:42:38,221 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

I hope someone can help me! 

 

Thank you very much in advance!

 

I as well am having the same problem as well....Do you have bonded nics?

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now