Jump to content
linuxserver.io

[Support] Linuxserver.io - Plex Media Server

3190 posts in this topic Last Reply

Recommended Posts

2 minutes ago, Xaero said:

I'm having trouble getting DLNA to work.
The network is set to HOST (as it is by default)
I've enabled DLNA in the plex settings.
I've enabled both of the advanced network options for unauthorized access and lan for 192.168.1.0/24 (my subnet/mask for the local network)
I don't see the plex media server listed in Windows 10 Explorer, Windows Media player or any other DLNA enabled stuff.

Any suggestions?

Top of my head, (but take with a grain of salt since I don't use Plex), but maybe you'll have to give Plex a static IP address in the template instead of having it set to HOST so that it winds up on the same network as everything else instead of on the default docker network.

Share this post


Link to post
1 hour ago, Squid said:

Top of my head, (but take with a grain of salt since I don't use Plex), but maybe you'll have to give Plex a static IP address in the template instead of having it set to HOST so that it winds up on the same network as everything else instead of on the default docker network.

 

I have DLNA working here with Plex set as host. But could it be that there are something else using port 1900, so Plex can't bind to it?

Share this post


Link to post
3 hours ago, Xaero said:

I'm having trouble getting DLNA to work.
The network is set to HOST (as it is by default)
I've enabled DLNA in the plex settings.
I've enabled both of the advanced network options for unauthorized access and lan for 192.168.1.0/24 (my subnet/mask for the local network)
I don't see the plex media server listed in Windows 10 Explorer, Windows Media player or any other DLNA enabled stuff.

Any suggestions?

I have some default settings like this 

image.thumb.png.bdab5f02ede88586c66c1a1100309f63.png

Now if you are speaking about Windows 10. Do a test, just disable the Firewall and the DLNA server should show up. Then start troubleshooting what is being blocked and what not. Maybe you have to create a rule in the windows firewall to allow connections from the plex.

Share this post


Link to post

Interesting, I put the IP=*,DirectPlay=true,DirectStream=true and stopped/started. It kind of showed up, then disappeared. I removed that line, and restarted DLNA again; this time it shows up under "This PC" on my Windows 10 client, and I can open files with Media Player - but the audio is a garbled mess. Not sure what to do about that lol.

Share this post


Link to post
11 minutes ago, Xaero said:

Interesting, I put the IP=*,DirectPlay=true,DirectStream=true and stopped/started. It kind of showed up, then disappeared. I removed that line, and restarted DLNA again; this time it shows up under "This PC" on my Windows 10 client, and I can open files with Media Player - but the audio is a garbled mess. Not sure what to do about that lol.

I knew it was something between those lines.

 

This is what I have

DLNA client preferences

IP=*,DirectPlay=true,DirectStream=true,LocalResolution=1920x1080,RemoteResolution=1280x720,OnlineResolution=1280x720,LocalVideoQuality=74,RemoteVideoQuality=49,OnlineVideoQuality=49,SubtitleSize=100,AudioBoost=100,MusicBitrate=64

DLNA default protocol info

http-get:*:video/mpeg:*,http-get:*:video/mp4:*,http-get:*:video/vnd.dlna.mpeg-tts:*,http-get:*:video/avi:*,http-get:*:video/x-matroska:*,http-get:*:video/x-ms-wmv:*,http-get:*:video/wtv:*,http-get:*:audio/mpeg:*,http-get:*:audio/mp3:*,http-get:*:audio/mp4:*,http-get:*:audio/x-ms-wma*,http-get:*:audio/wav:*,http-get:*:audio/L16:*,http-get:*image/jpeg:*,http-get:*image/png:*,http-get:*image/gif:*,http-get:*image/tiff:*

DLNA media renderer discovery interval

60

DLNA server announcement lease time

1800

DLNA server description icons

png,jpeg;260x260,120x120,48x48

 

But bro, don't use media player for that. Go to the plex website or download the plex player. If you have a smart tv, use the plex app. Honestly don't stress too much about it. Because it's likely an issue with the firewall or the settings in the computer .

Share this post


Link to post

Yeah I figured out why that was as well. The DLNA tells media player what to try to do. So since my setup is Stereo on this PC and the audio from the file is usually 5.1 or higher - I just get garbled mess. It doesn't do any transcoding or anything. So I'll just go back to how I was watching stuff locally - browsing through the share and opening it in MPV.

Share this post


Link to post
16 minutes ago, Xaero said:

Yeah I figured out why that was as well. The DLNA tells media player what to try to do. So since my setup is Stereo on this PC and the audio from the file is usually 5.1 or higher - I just get garbled mess. It doesn't do any transcoding or anything. So I'll just go back to how I was watching stuff locally - browsing through the share and opening it in MPV.

Use the browser or download the plex media player that should do it

Share this post


Link to post

I am facing an issue with playing some movies in the web player. Did some research and it may be an issue relaxed to the linuxserver docker, while claimed to be working in the official plex docker. I haven't tried to switch to the official docker, but at least that's what they are saying in the plex forums. https://forums.plex.tv/t/eae-timeout-eae-not-running-or-wrong-folder/189661/3 and https://forums.plex.tv/t/error-transcoder-ac3_eae-0x2fd4f40-eae-timeout-eae-not-running-or-wrong-folder/189917/33 both state that it works with official docker.

 

The issue is not with all movies, but with some. I cannot identify a pattern, which ones are working and which ones are not. For those it doesn't work, it does not work consistently. Snippet from the log below:

 

Dec 02, 2018 09:25:33.948 [0x14e78ebff700] DEBUG - MDE: Movie (2018): media must be transcoded in order to use the dash protocol
Dec 02, 2018 09:25:33.948 [0x14e78ebff700] DEBUG - MDE: Movie (2018): no direct play video profile exists for http/mkv/h264
Dec 02, 2018 09:25:33.948 [0x14e78ebff700] DEBUG - MDE: Movie (2018): no direct play video profile exists for http/mkv/h264/eac3
Dec 02, 2018 09:25:33.948 [0x14e78ebff700] DEBUG - MDE: Cannot direct stream audio stream due to codec eac3 when profile only allows aac

Share this post


Link to post

Solution: Ended up deleting the library, as no backups occured for the last 6 months, so the database must have been somewhat corrupt for some time.

 

Starting Plex Media Server - Loop

All of a sudden, I experience the Plex docker not starting.

  • It worked fine at Friday, but when the server started today, Plex no longer starts.
  • Friday at midnight, the Plex container automatically updated using app; AutoUpdateApps.

 

  • Using LinuxServer.io LetsEncrypt docker for ReverseProxy, if it is related.
    Which was also updated at Friday midnight.

 

Anyone who has an idea for how to solve this?

 

In the Plex Media Server log (\appdata\plex\Library\Application Support\Plex Media Server\Logs)
It reports that the database image is corrupt.

image.thumb.png.3b29ed013f4cd86b92f6412c3e65c080.png

 

PRAGMA integrity_check outputs the following, and the 'Repair a corrupt database guide from Plex' unfortunately does not solve it.
Instead, making an empty database when converting from the .SQL to .DB

image.png.b54f47c1829ca52b52a2aecb913af9e1.png

 

 

Configuration

image.thumb.png.3bf9ca2e3820348a8ef675f3d029ade2.png

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...
No update required
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting dbus-daemon
Starting Plex Media Server.
[services.d] done.
Starting Avahi daemon
Found user 'avahi' (UID 102) and group 'avahi' (GID 103).
Successfully dropped root privileges.
avahi-daemon 0.7 starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

Joining mDNS multicast group on interface vethfd8410a.IPv6 with address fe80::240d:a4ff:fec5:7105.
New relevant interface vethfd8410a.IPv6 for mDNS.
Joining mDNS multicast group on interface vethc602a55.IPv6 with address fe80::7c89:38ff:fec7:1d5b.
New relevant interface vethc602a55.IPv6 for mDNS.
Joining mDNS multicast group on interface veth26b4467.IPv6 with address fe80::b8f9:8eff:fe46:dc31.
New relevant interface veth26b4467.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe9c235b.IPv6 with address fe80::1c51:14ff:fe9e:d29a.
New relevant interface vethe9c235b.IPv6 for mDNS.
Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:8dff:fee1:edf7.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface br0.IPv6 with address fe80::f884:27ff:fe6f:ebc9.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.14.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface bond0.IPv6 with address fe80::76d0:2bff:fe95:2bb8.
New relevant interface bond0.IPv6 for mDNS.
Joining mDNS multicast group on interface lo.IPv6 with address ::1.
New relevant interface lo.IPv6 for mDNS.
Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
New relevant interface lo.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::240d:a4ff:fec5:7105 on vethfd8410a.*.
Registering new address record for fe80::7c89:38ff:fec7:1d5b on vethc602a55.*.
Registering new address record for fe80::b8f9:8eff:fe46:dc31 on veth26b4467.*.
Registering new address record for fe80::1c51:14ff:fe9e:d29a on vethe9c235b.*.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::42:8dff:fee1:edf7 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::f884:27ff:fe6f:ebc9 on br0.*.
Registering new address record for 192.168.1.14 on br0.IPv4.
Registering new address record for fe80::76d0:2bff:fe95:2bb8 on bond0.*.
Registering new address record for ::1 on lo.*.
Registering new address record for 127.0.0.1 on lo.IPv4.
Server startup complete. Host name is tower.local. Local service cookie is 1672898640.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.

 

Edited by Ctofte

Share this post


Link to post

Am I doing something wrong here? I seem to have to boost the size of my docker.img file every few weeks to account for a growing Plex container. Right now I'm up to about 33GB (with my docker.img size at 40GB). From what I can tell, I have everything setup to be outside of the container.. however note that originally I had the transcode folder setup to run in the container. I have since moved that.

 

Usage:

CONTAINER ID     IMAGE                COMMAND     CREATED             STATUS              PORTS        NAMES               SIZE
b92f3afec57d     linuxserver/plex     "/init"     2 weeks ago         Up 21 minutes                    plex                32.6GB (virtual 33GB)

 

Anyway, let me know if you see any problems with my setup:

2094038824_ScreenShot2018-12-13at11_06_11AM.thumb.png.35c369f18eaedb9a38404e43ae80d306.png

 

Thanks in advance, let me know if any more information is needed!

 

Share this post


Link to post
21 minutes ago, tayshserve said:

Am I doing something wrong here? I seem to have to boost the size of my docker.img file every few weeks to account for a growing Plex container. Right now I'm up to about 33GB (with my docker.img size at 40GB). From what I can tell, I have everything setup to be outside of the container.. however note that originally I had the transcode folder setup to run in the container. I have since moved that.

 

Usage:


CONTAINER ID     IMAGE                COMMAND     CREATED             STATUS              PORTS        NAMES               SIZE
b92f3afec57d     linuxserver/plex     "/init"     2 weeks ago         Up 21 minutes                    plex                32.6GB (virtual 33GB)

 

Anyway, let me know if you see any problems with my setup:

2094038824_ScreenShot2018-12-13at11_06_11AM.thumb.png.35c369f18eaedb9a38404e43ae80d306.png

 

Thanks in advance, let me know if any more information is needed!

 

My plex container size is less than 500MB. My media library is probably somewhat smaller than some. But it does seem like you have something wrong.

 

On the Docker page, what do you get when you click the Container Size button?

Share this post


Link to post
20 minutes ago, trurl said:

My plex container size is less than 500MB. My media library is probably somewhat smaller than some. But it does seem like you have something wrong.

 

On the Docker page, what do you get when you click the Container Size button?

Clicking the Container Size button get's me the following:

Name                              Container     Writable          Log
---------------------------------------------------------------------
plex                                33.0 GB      32.6 GB       495 kB
binhex-krusader                     2.29 GB      30.3 MB       468 kB
radarr                               658 MB      76.6 MB      23.7 MB
ombi                                 633 MB       224 MB       486 kB
sonarr                               617 MB      39.1 MB      29.2 MB
glances                              615 MB       355 kB        130 B
duplicati                            598 MB       301 kB      7.30 kB
DDclient                             315 MB       1.3 MB      2.73 MB
letsencrypt                          294 MB      55.5 MB      17.1 kB
sabnzbd                              268 MB       301 kB       220 MB
tautulli                             234 MB      45.4 MB      1.76 GB
openvpn-as                           221 MB       1.2 MB      9.56 kB
telly                                124 MB          0 B      5.89 MB
transmission                        37.4 MB      6.47 kB       506 kB

Seems like all my other container are within reason except for Krusader which probably just needs a trashcan emptied or something.. Interesting. Is there a way I can browse the containers filesystem to see where all that space is being used?

 

Appreciate the reply

Share this post


Link to post

In the plex application, what do you have set for the transcoder directory?

Share this post


Link to post
52 minutes ago, trurl said:

In the plex application, what do you have set for the transcoder directory?

Ah.. I actually have nothing in there. Didn't see that guy hiding behind the advanced filter. Should that be set to `transcode` or `/transcode`?

1759138592_ScreenShot2018-12-13at12_57_27PM.png.ff9ada50b8dbc877ae8a74d8a703bd7c.png

 

edit - typed `config` instead of `transcode`

Edited by tayshserve

Share this post


Link to post
6 minutes ago, tayshserve said:

`transcode` or `/transcode`?

/transcode to match the specified container path.

 

According to Plex (and they should know 😀), when no transcode directory is defined, Plex defaults to {path to Plex appdata}/Library/Application Support/Plex Media Server/Cache/Transcode

Share this post


Link to post
5 minutes ago, Hoopster said:

/transcode to match the specified container path.

 

According to Plex (and they should know 😀), when no transcode directory is defined, Plex defaults to {path to Plex appdata}/Library/Application Support/Plex Media Server/Cache/Transcode

which would be on mapped Unraid storage so that doesn't seem like it should be the problem. And in fact, I am just using that default myself, but seldom transcode. Might be worth setting it to /transcode though just to see if it makes a difference.

 

I notice you also have a few logs that are pretty large. Have you set log rotation in Settings - Docker?

Share this post


Link to post

Yep I was under the impression that Plex was transcoding to /tmp by default. When I look into the container file structure, it seems like /tmp is the culprit. That bad boy is 31GB but just contains a bunch of XML files. Not sure what these are or how to actually move them elsewhere.. but it seems like I'm missing some kind of path map here.

 

608010696_ScreenShot2018-12-13at2_05_53PM.png.3af519e83980e73ef26b95c228a99700.png

 

Update – so I opened one of the XML files from the tmp directory and it seems to be live TV guide data from schedules direct? Wondering if it's safe to just delete this stuff.. I'm honestly not even sure where this data is coming from as I use the EPG data from Plex/Gracenote, not schedules direct.

 

Update 2 – alright.. I spot checked a bunch of the files and saw they were all schedules direct data.. I was going to back this stuff up but figured since it's in a temporary directory I should be fine. I deleted all the XML files and restarted Plex. My container size dipped down to under a GB. I guess I'll monitor the situation to see what happens.. but I honestly cannot explain how all that crap got dumped into that folder. The only thing I can think of is at one point maybe I tested using schedules direct? Even so.. 30+GB? 

 

Annnnd in the middle of typing the above I noticed that the tmp folder has begun to fill up again... with data from schedules direct? 

Edited by tayshserve

Share this post


Link to post
50 minutes ago, tayshserve said:

Yep I was under the impression that Plex was transcoding to /tmp by default. When I look into the container file structure, it seems like /tmp is the culprit.

 

What is the Plex folder associated with your TV Shows library?  You will have to delete your Plex DVR and recreate if you want to change EPG settings.  I use the HDHomeRun EPG.  It appears the DVR still thinks its using Schedules Direct?

 

I have my Plex transcode set to use /tmp as the host path with /transcode as container path.  /tmp if properly configured is RAM.

Share this post


Link to post

Tried to update today, hung stopping the container before I went to work, came home with it still hung, loading unraid in another tab shows the container is gone. I'm gonna backup the appdata and reinstall it and hopefully be good.

Share this post


Link to post

Hi unraiders, new issue here today. Plex has been running fine for many months and through many docker updates. However, just updated the docker image on my unraid server and now a single core of my i7 8700 is constantly being used 100% by the plex docker. No other cpu cores are affected at all. From time to time the specific core which is at 100% might switch but it is always only 1 core. Ther is nothing in the plex logs to show it is doing anything, and I have restarted the docker image a few times but every time I start it the single core jumps straight back up to 100% again.

 

Any advice much appreciated, thankyou.

 

Edit: I am also seeing that in Netdata my 'IPv4 UDP Sockets Memory' metric is slowly creeping up to levels where it is giving me alarms and registered UDP errors. When I stop the plex docker this jumps back down to zero, and when I start it back up the metric starts to creep up again. Seems related somehow.

Edited by Ascii227

Share this post


Link to post

Advice is to revert the plex server docker to the previous version.

Share this post


Link to post
11 minutes ago, BRiT said:

Advice is to revert the plex server docker to the previous version.

Thankyou very much for your time and advice, but is there an easy way to do that? I cant see any option from within the unraid gui. Thanks again.

Share this post


Link to post

You need to specify the exact previous version in the TAG field instead of "latest". I'm not sure if all dockers have each version tagged, but they really should, to make it easy to get back to exact moments in time. LinuxServer has their docker images tagged properly, so pick a moment in time that used to work for you. Perhaps 158 or 157, or even earlier depending on what version you were running before you updated when things ran fine.

 

https://hub.docker.com/r/linuxserver/plex/tags

 

Latest = 159, updated 7 days ago.

Previous = 158, updated 14 days ago.

Previous Previous = 157, updated 21 days ago.

 

 

Edited by BRiT

Share this post


Link to post
1 hour ago, BRiT said:

You need to specify the exact previous version in the TAG field instead of "latest".

Thanks very much for the crash course in docker management! I specified 158 in the tag field, restarted the docker, and now plex is working fine again with the previous version and minimal cpu usage. I will wait til another version is released and then change the tag back to latest and see if my issue is resolved.

 

Thankyou for the knowledge.

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