[Support] Linuxserver.io - Plex Media Server


Recommended Posts

On 5/1/2021 at 1:31 PM, audioclass said:

I'm experiencing a minor issue/inconvenience on a consistent basis.  Any time my container is restarted, my Settings > Remote Access configuration is unchecking the 'Manually specify public port' setting, which prompts the screen to indicate that my server is not accessible remotely.  I can recheck the box, and press apply, and I then get the green 'Fully accessible outside your network' message again.  So far, this has not actually impacted the ability of my users to access, despite the message, but it is annoying to have to keep turning it back on again.  I also fear that if my firewall states get cleared during that period it WILL cause issues.  Any idea why this setting does not persist through a restart? 

I've tried searching for similar cases but haven't had much luck.  Of course, if I switch to UPnP this is a non-issue, but I'm keen to keep this disabled on my firewall for obvious security concerns.

 

Sorry to keep dragging this up, but is nobody else running manual port mapping and having this issue?  It is driving me wild that every couple days this setting just reverts itself and my users are stuck with plex relay quality.  I really don't want to enable UPnP or give direct access via a reverse proxy, but I'm running out of ideas.  I can't find any information on this.  Do I have something misconfigured?

Link to comment

@audioclass i assume most (like me) prefer the reverse proxy way (which is not direct access ...), may rather look for help therefore in the plex forums as this looks more like a plex behaviour you want to nail out.

 

and as you mentioned its not locked or so for remote access, more a cosmetic issue (currently) as its working as you said.

 

you also entered your domain name where plex is reachable including the port i guess, network settings, own url to access ...

Link to comment
@audioclass i assume most (like me) prefer the reverse proxy way (which is not direct access ...), may rather look for help therefore in the plex forums as this looks more like a plex behaviour you want to nail out.
 
and as you mentioned its not locked or so for remote access, more a cosmetic issue (currently) as its working as you said.
 
you also entered your domain name where plex is reachable including the port i guess, network settings, own url to access ...

Unfortunately, it isn’t just a cosmetic issue. It seemed like it at first, because it would often still say it was reachable. Now, though, I’ve confirmed that it forces my users onto the relay, locking them at SD resolutions.

I also don’t have this issue with a test server that isn’t containerized.


Sent from my iPhone using Tapatalk
Link to comment
2 hours ago, audioclass said:

I also don’t have this issue with a test server that isn’t containerized.

 

then may try different setups, plex in host mode on unraid or rather setup a reverse proxy so you dont rely on plex about this.

 

last but not least, try a different docker (official plex one) if that may helps ;) but i can tell you, i use the official one and it almost never shows its reachable outside, but as im behind a reverse proxy im fine.

Link to comment
Do you have PlexPass?  Add them as Family rather than a Friend

I do have plexpass. But I fail to see how giving family access will resolve this issue, since they would STILL be unable to access remotely once it decides to switch itself off again in two days.

I don’t wish to use a reverse proxy or UPnP, as the built-in remote access is the solution I’m looking for.

Anyway, thanks for the replies, it seems I’m probably on my own to figure this out.

I will try some different containers as suggested to see if it is unique to the LS container.


Sent from my iPhone using Tapatalk
Link to comment

Did you end up finding a fix for this? I'm having the same issue and haven't been able to find one yet. It only happens when HW acceleration is enabled.

 

On 4/9/2021 at 6:04 PM, NightCharger said:

I have been having an issue getting hardware transcoding to work on the linuxserver.io plex media server docker container. I have a Nvidia Quadro P1000 and I have it installed in my unraid server. I pulled down the docker container and made sure to add the --runtime=nvidia to the extra parameters and also downloaded the Nvidia Driver Plugin so that I could copy the GPU id to the Nvidia Visible Devices variable. I'm using v465.19.01 driver. I have set plex up and let it refresh the metadata of the files. I made the changes in the settings to allow allow hardware transcoding and I do have a lifetime plex pass. When I try transcoding the screen will flash a few times then throw this Playback Error: An unknown error occurred (4294967279)
Error code: 4294967279

Looking at the logs it looks like it's having a hard time find the right codec. Other times when I play a movie it will transcode in hardware just fine at full quality. If I try to force it down to a lower level using either the browser or plex desktop app it will not continue playing and it will be just a blank screen. I've noticed however in the plex dashboard it shows the movies as continuing to play at the lower resolution even though the progress is not changing on the client.

Previously I was running the Plex Media Server docker container with intel quicksync for hardware transcoding just fine as I have a plex pass and I was able to pass the correct parameters to their docker container. I was not sure if that container would work with an Nvidia card so that's why I'm using the linuxserver one. Previously I was transcoding to ram by using the host path /tmp mapped to the container path of /transcode. Does linuxserver support transcoding to ram?

Plex Media Server.log 379.05 kB · 0 downloads

Edited by Airwolf99
more info
Link to comment

New unRAID 6.9.2 install on Ryzen 3600 CPU, 64GB, Nvidia P2000 GPU, 10x12TB WD Red Array w/ single parity, 3 SSD cache pools 1+1 TB WD Black Nvme and 2x1TB Corsair MX500 SATA SSDs.

Really happy with the functionality of this container as it let's me do HW transcoding with my nvidia P2000, also for HDR tone mapping. Actually it was the main reason for finally migrating from a Windows Server 2019 with plex setup.

After pulling down the container after some time I can't access the plex web ui using the <http://serverip:32400/web>. I could initially access the web ui. I have since added other containers but I triple checked that there are no overlapping ports with any of the other containers.

Docker image is running with default host network (just added a few paths)

172.27.10.100:1900/UDP - 172.27.10.100:1900
172.27.10.100:3005/TCP - 172.27.10.100:3005
172.27.10.100:32400/TCP - 172.27.10.100:32400
172.27.10.100:32410/UDP - 172.27.10.100:32410
172.27.10.100:32412/UDP - 172.27.10.100:32412
172.27.10.100:32413/UDP - 172.27.10.100:32413
172.27.10.100:32414/UDP - 172.27.10.100:32414
172.27.10.100:32469/TCP - 172.27.10.100:32469
172.27.10.100:5353/UDP - 172.27.10.100:5353
172.27.10.100:8324/TCP - 172.27.10.100:8324

 

I can manage all aspects of the server through another plex server's web ui and the plex server is otherwise seemingly fully functional. My new unRAID Plex Server is meant to replace the old one so managing the new plex server through the old one's web ui is not an option.

How can I troubleshoot this? I already removed and reinstalled the container as well as doing a force upgrade but no luck. The error message is "connection was reset".

 

Any help very much appreciated.

Edited by extcon
added information
Link to comment
On 5/1/2021 at 7:31 PM, audioclass said:

I'm experiencing a minor issue/inconvenience on a consistent basis.  Any time my container is restarted, my Settings > Remote Access configuration is unchecking the 'Manually specify public port' setting, which prompts the screen to indicate that my server is not accessible remotely.  I can recheck the box, and press apply, and I then get the green 'Fully accessible outside your network' message again.  So far, this has not actually impacted the ability of my users to access, despite the message, but it is annoying to have to keep turning it back on again.  I also fear that if my firewall states get cleared during that period it WILL cause issues.  Any idea why this setting does not persist through a restart? 

I've tried searching for similar cases but haven't had much luck.  Of course, if I switch to UPnP this is a non-issue, but I'm keen to keep this disabled on my firewall for obvious security concerns.

This is happening to me too. I'm pretty sure it's because my ISP has changed settings so I'm now not using an external IP but rather a GNAT carrier address. I will talk to ISP support on Monday to confirm and have them change back as I've had it up and working properly for almost a year before it stopped working last week.

Link to comment
This is happening to me too. I'm pretty sure it's because my ISP has changed settings so I'm now not using an external IP but rather a GNAT carrier address. I will talk to ISP support on Monday to confirm and have them change back as I've had it up and working properly for almost a year before it stopped working last week.

I think most people are confusing what I mean. It isn’t just a matter of people being randomly unable to connect to me. The actual SETTING in Plex is unchecking itself randomly any time the container restarts due to updates or backups. It is the only setting that this occurs with.
Link to comment
2 minutes ago, audioclass said:


I think most people are confusing what I mean. It isn’t just a matter of people being randomly unable to connect to me. The actual SETTING in Plex is unchecking itself randomly any time the container restarts due to updates or backups. It is the only setting that this occurs with.

Yeah, I admit to being confused... I never heard that one before, sorry. Are you saying that while the setting is active everything works as expected and then when plex by itself unchecks the setting it stops working, i.e. the issue is with plex and not network related?

Link to comment
Yeah, I admit to being confused... I never heard that one before, sorry. Are you saying that while the setting is active everything works as expected and then when plex by itself unchecks the setting it stops working, i.e. the issue is with plex and not network related?

Yeah, exactly that. It all works fine, I can set a certain bandwidth (ex 10MB/s) for remote users and they can reach that quality. Then, for whatever reason if the container has to restart for any reason (updates, regular backups which restart the container, etc.) the setting becomes unchecked, at which point remote access is disabled and they are forced through the plex relay which has a paltry 2MB/s limit and looks terrible.
Link to comment
14 minutes ago, audioclass said:


Yeah, exactly that. It all works fine, I can set a certain bandwidth (ex 10MB/s) for remote users and they can reach that quality. Then, for whatever reason if the container has to restart for any reason (updates, regular backups which restart the container, etc.) the setting becomes unchecked, at which point remote access is disabled and they are forced through the plex relay which has a paltry 2MB/s limit and looks terrible.

That's really weird.

I just checked and the setting *should persist as it is in the /appdata/plex/Library/Application Support/Plex Media Server/Preferences.xml file. The value is ManualPortMappingMode="1" for enabled and the Preferences.xml file is outside the container in appdata. Can you check this file when it everything is working and again when it seems not to be working, what are the values of the ManualPortMappingMode setting in either case?

 

  • Like 1
Link to comment
19 minutes ago, extcon said:

That's really weird.

I just checked and the setting *should persist as it is in the /appdata/plex/Library/Application Support/Plex Media Server/Preferences.xml file. The value is ManualPortMappingMode="1" for enabled and the Preferences.xml file is outside the container in appdata. Can you check this file when it everything is working and again when it seems not to be working, what are the values of the ManualPortMappingMode setting in either case?

 

Wow, this might be the issue.  The xml does not contain an entry for ManualPortMappingMode.  I'm going to backup the file and then add that entry and see what happens.  If this fixes it I'll feel dumb :D

 

Edit:  I shut down the container, edited the file to include that setting, and started the container only to find the setting unchecked again. Blast!

BUT!  After repeating the process and adding both that setting AND ManualPortMappingPort="32400" (from the preferences.xml documentation, it worked!  Upon starting the container remote access was enabled, and after a couple restarts it is STILL enabled!  Woohoo!

 

I'm going to keep holding my breath over the next few days to see if it happens again, but so far I think you've helped me solve the issue.

 

Thank you @extcon !

Edited by audioclass
Link to comment
21 minutes ago, audioclass said:

Wow, this might be the issue.  The xml does not contain an entry for ManualPortMappingMode.  I'm going to backup the file and then add that entry and see what happens.  If this fixes it I'll feel dumb :D

 

Edit:  I shut down the container, edited the file to include that setting, and started the container only to find the setting unchecked again. Blast!

BUT!  After repeating the process and adding both that setting AND ManualPortMappingPort="32400" (from the preferences.xml documentation, it worked!  Upon starting the container remote access was enabled, and after a couple restarts it is STILL enabled!  Woohoo!

 

I'm going to keep holding my breath over the next few days to see if it happens again, but so far I think you've helped me solve the issue.

 

Thank you @extcon !

Keeping my fingers crossed for you🤞

Link to comment

After updating to 6.10.0-rc1 my 11th gen (11500) HW transcoding is not working anymore. Removed the modprobe file, also didn't work. The driver does seem to be loaded fine without modprobe file. Maybe it has to do with the Intel TOP plugin that needs an update, I have no idea. But just be aware that HW transcoding for me is currently fully broken.

 

Before it would HW transcode even in HDR on plenty of movies (not all as we discussed earlier).

Link to comment
On 8/10/2021 at 4:47 AM, Kaizac said:

After updating to 6.10.0-rc1 my 11th gen (11500) HW transcoding is not working anymore. Removed the modprobe file, also didn't work. The driver does seem to be loaded fine without modprobe file. Maybe it has to do with the Intel TOP plugin that needs an update, I have no idea. But just be aware that HW transcoding for me is currently fully broken.

 

Before it would HW transcode even in HDR on plenty of movies (not all as we discussed earlier).

thanks for the heads up, that's really bad news :/

Link to comment

Hey guys,

 

I noticed some giant MP4 files in my plex appdata share.....

 

/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/61/379844.mp4
/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/e8/254825.mp4
 

These are 700-1000MB each.  

 

Are these left over temp files from some failed watching of content?  Can I delete them?  I'm manually tar'ing my appdata folder and have noticed a ton:

 

root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache# find . * | grep mp4
./Transcode/Sync+/36266422/61/379844.mp4
./Transcode/Sync+/36266422/e8/254825.mp4
./Transcode/Sync+/36266422/5f/14352.mp4
./Transcode/Sync+/36266422/32/14353.mp4
./Transcode/Sync+/36266422/4b/14354.mp4
./Transcode/Sync+/36266422/31/14355.mp4
./Transcode/Sync+/36266422/e3/256938.mp4
./Transcode/Sync+/36266422/47/256936.mp4
./Transcode/Sync+/36266422/fb/256939.mp4
./Transcode/Sync+/36266422/36/256940.mp4
Transcode/Sync+/36266422/61/379844.mp4
Transcode/Sync+/36266422/e8/254825.mp4
Transcode/Sync+/36266422/5f/14352.mp4
Transcode/Sync+/36266422/32/14353.mp4
Transcode/Sync+/36266422/4b/14354.mp4
Transcode/Sync+/36266422/31/14355.mp4
Transcode/Sync+/36266422/e3/256938.mp4
Transcode/Sync+/36266422/47/256936.mp4
Transcode/Sync+/36266422/fb/256939.mp4
Transcode/Sync+/36266422/36/256940.mp4
root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache#
  


Safe to delete?

Edited by tucansam
Link to comment

Hi has anyone succeeded with running the commands to repair a database in the docker? Annoyingly my database backups were never made - and I'm trying to avoid using CA as my backup's a bit old.

 

https://support.plex.tv/articles/repair-a-corrupted-database/

 

When I try to run the commands to repair the database (I created a copy of my database) I get this:

root@Highlander:/# "/usr/lib/plexmediaserver/Plex SQLite" com.plexapp.plugins.library2.db "PRAGMA integrity_check"
ok

root@Highlander:/# "/usr/lib/plexmediaserver/Plex SQLite" com.plexapp.plugins.library2.db ".output dump.sql" ".dump"
root@Highlander:/# del com.plexapp.plugins.library2.db
bash: del: command not found

Nothing seems to happen with the dump command, and then the del fails.  Any idea what I'm doing wrong?

Thanks in advance.

Link to comment
On 8/15/2021 at 2:09 PM, tucansam said:

Hey guys,

 

I noticed some giant MP4 files in my plex appdata share.....

 

/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/61/379844.mp4
/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+/36266422/e8/254825.mp4
 

These are 700-1000MB each.  

 

Are these left over temp files from some failed watching of content?  Can I delete them?  I'm manually tar'ing my appdata folder and have noticed a ton:

 

root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache# find . * | grep mp4
./Transcode/Sync+/36266422/61/379844.mp4
./Transcode/Sync+/36266422/e8/254825.mp4
./Transcode/Sync+/36266422/5f/14352.mp4
./Transcode/Sync+/36266422/32/14353.mp4
./Transcode/Sync+/36266422/4b/14354.mp4
./Transcode/Sync+/36266422/31/14355.mp4
./Transcode/Sync+/36266422/e3/256938.mp4
./Transcode/Sync+/36266422/47/256936.mp4
./Transcode/Sync+/36266422/fb/256939.mp4
./Transcode/Sync+/36266422/36/256940.mp4
Transcode/Sync+/36266422/61/379844.mp4
Transcode/Sync+/36266422/e8/254825.mp4
Transcode/Sync+/36266422/5f/14352.mp4
Transcode/Sync+/36266422/32/14353.mp4
Transcode/Sync+/36266422/4b/14354.mp4
Transcode/Sync+/36266422/31/14355.mp4
Transcode/Sync+/36266422/e3/256938.mp4
Transcode/Sync+/36266422/47/256936.mp4
Transcode/Sync+/36266422/fb/256939.mp4
Transcode/Sync+/36266422/36/256940.mp4
root@ffs2:/mnt/disks/ssd/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Cache#
  


Safe to delete?

 

Strange, I've literally just dealt with this about an hour ago (it was sitting at around 40Gig!). I used the unraid terminal to delete the numbered folder, & it's contents, in the Sync+ directory. Wasn't sure if just deleting the Sync+ folder would make a difference, but decided to just keep it and delete everything in it. So far, no issues. 

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.