[Support] Linuxserver.io - Plex Media Server


Recommended Posts

On 3/28/2019 at 6:58 AM, aptalca said:

Along with the version for 1.14blah, pass an environment variable where PLEX_DOWNLOAD="https://downloads.plex.tv/plex-media-server"

2087480686_plexversionproblem.thumb.PNG.2efa227e5b943a9b2a9139e6bd4d23ca.PNG

 

No change...

 

749512846_plexversionproblem2.PNG.d52e9e71c6e925ff059310050f294746.PNG

 

I added the variable, as you suggested. But I must be missing something. No matter what I try, the "version" still reports as "latest" and the Plex container still says I'm running 1.15.2.793.

 

Could someone please point out what I'm missing/doing wrong? I'd love to have this control again.

 

Thanks.

Link to comment
8 hours ago, Kudjo said:

2087480686_plexversionproblem.thumb.PNG.2efa227e5b943a9b2a9139e6bd4d23ca.PNG

 

No change...

 

749512846_plexversionproblem2.PNG.d52e9e71c6e925ff059310050f294746.PNG

 

I added the variable, as you suggested. But I must be missing something. No matter what I try, the "version" still reports as "latest" and the Plex container still says I'm running 1.15.2.793.

 

Could someone please point out what I'm missing/doing wrong? I'd love to have this control again.

 

Thanks.

First of all, the additional variable is only needed if you're trying to go back to 1.14, not 1.15. Second, you're missing some digits in the version you are entering. It needs to be longer than that.

Third, the "latest" you're seeing in that screenshot is for the docker image, not the version of Plex inside the image

Link to comment
8 hours ago, trurl said:

You have to create a mapping for your media.

 

See the Getting Started section of the Docker FAQ:

 

https://forums.unraid.net/topic/57181-real-docker-faq/

 

Thanks. 

 

Got it all set up. Still using about 40% of total CPU load on average while transcoding. Since I reinstalled everything cleanly with all new app data and everything I don't think it's the docker causing the issue. Alas, I will have to look at some Plex forums to see what could possibly be happening. It just started doing this in the past few days. 

Link to comment
49 minutes ago, Vonlaus said:

Thanks. 

 

Got it all set up. Still using about 40% of total CPU load on average while transcoding. Since I reinstalled everything cleanly with all new app data and everything I don't think it's the docker causing the issue. Alas, I will have to look at some Plex forums to see what could possibly be happening. It just started doing this in the past few days. 

What's the source media you're transcoding by the way? Is it h265? 4K? If so, even on a super fast cpu, it is very difficult to sw decode so your experience is perfectly normal

Link to comment
39 minutes ago, aptalca said:

What's the source media you're transcoding by the way? Is it h265? 4K? If so, even on a super fast cpu, it is very difficult to sw decode so your experience is perfectly normal

No 265. No 4K files. It all started the other day probably Sunday the 31st. I have been running the server fine for a few months now. No issues. Each transcode was using up to about 10 percent of the total CPU load from the Dual CPU's. I have been testing with a x264 720p TV Show.

 

I tried to follow the instructions to downgrade to 1.14 just to test the plex version however I can't seem to get the docker to downgrade the version. I also tried version 1.14.1.5488-cc260c476-ls9 and that didn't work either. 

3.PNG

Edited by Vonlaus
Link to comment
9 hours ago, aptalca said:

First of all, the additional variable is only needed if you're trying to go back to 1.14, not 1.15. Second, you're missing some digits in the version you are entering. It needs to be longer than that.

Third, the "latest" you're seeing in that screenshot is for the docker image, not the version of Plex inside the image

This was highly informative. Thank you. Okay, I'll go in order.

1) I didn't know that was specific for 1.14, thank you for telling me that. I don't remember seeing that requirement, so I'm glad I know now. Are there any other times when that variable should be applied?

2) You're absolutely correct, I'm missing the rest of the tag in that screenshot (I pinky promise I've used the correct tag before). Unfortunately, the tag: "1.15.1.791-8bec0f76c-ls11" still doesn't do the trick for me. Plex is still reporting that it's on version 1.15.2.793. :( I'm getting my tags from: https://hub.docker.com/r/linuxserver/plex/tags if there's somewhere else I should be looking up the tags then maybe that's my problem; incorrect tag names.

3) I'm basing my experience off of the official Plex Inc Docker container. It reported the Tag number I had selected as the version, so I assumed it worked the same for the LinuxServer Container. So, thank you for teaching me that doesn't seem to be the case for this one. 

 

Any ideas of what to try now?

plex version problem 3.PNG

Link to comment
2 hours ago, Kudjo said:

This was highly informative. Thank you. Okay, I'll go in order.

1) I didn't know that was specific for 1.14, thank you for telling me that. I don't remember seeing that requirement, so I'm glad I know now. Are there any other times when that variable should be applied?

2) You're absolutely correct, I'm missing the rest of the tag in that screenshot (I pinky promise I've used the correct tag before). Unfortunately, the tag: "1.15.1.791-8bec0f76c-ls11" still doesn't do the trick for me. Plex is still reporting that it's on version 1.15.2.793. :( I'm getting my tags from: https://hub.docker.com/r/linuxserver/plex/tags if there's somewhere else I should be looking up the tags then maybe that's my problem; incorrect tag names.

3) I'm basing my experience off of the official Plex Inc Docker container. It reported the Tag number I had selected as the version, so I assumed it worked the same for the LinuxServer Container. So, thank you for teaching me that doesn't seem to be the case for this one. 

 

Any ideas of what to try now?

plex version problem 3.PNG

You're confusing different tags.

 

There are docker image tags, which are found on the docker hub page under tags. If you don't select a tag, "latest" is selected by default, which is what you're seeing for our image there, simply because you put in "linuxserver/plex" as your image in the container settings. If you change that to "linuxserver/plex:1.15.1.791-8bec0f76c-ls11", then you'll see "1.15.1.791-8bec0f76c-ls11" as the tag in that screenshot for our image.

 

The other tag you're confused about is plex's version tag. Our image (different than the official plex image) supports updating to a custom version inside the container by setting an environment variable to a specific plex version. Other options are "latest", "public" and "docker". docker does no updates and you get the version that comes with that image. Public updates to the latest public release on container start and latest updates to the latest beta/plexpass on container start (as long as you're logged in with a plexpass account). Or you can set the version variable to a long plex version and it will update to that. The long plex version for the current stable is "1.15.2.793-782228f99". That's what you would need to enter in as the "VERSION" variable in container settings. 

 

Now as for the other variable for plex downloads, that's the url our image uses to download plex releases. With 1.15, that url changed. So if you enter in a 1.14 version, our image won't be able to download it from the new endpoint, so you need to override that url by passing in the url for old downloads, which is what I listed before. So if you want to update to a 1.15 version, don't specify that url. If you want to update to a 1.14 or earlier, you need to specify that url.

 

I hope that's clear.

 

If you simply want to use version 1.15.1.791-8bec0f76c, the easiest way would be to set the "VERSION" variable to "docker" so it doesn't do any updates during container start, and use the image "linuxserver/plex:1.15.1.791-8bec0f76c-ls11" so you'll use the image that comes with that version with no in container updates

Link to comment
On 4/1/2019 at 6:21 AM, trurl said:

If you get that problem on a clean install, then that suggests you have a problem with plex, not a problem with reusing a previous library.

I don't see how that could be a problem. It would just mean that plex.tv wouldn't know about that server. I don't think it should be a problem creating a new server at plex.tv

 

I don't specifically remember removing any, but I probably have, since I have had plex server on a number of different platforms over the years, and the only plex server I currently have is the one on my Unraid (and it was originally a needo docker as you know).

 

If you are still in doubt, you might see if anyone has anything to say about removing a server over at the plex forums.

So I hit Remove and now I get this... I tried logging out and in, I even tried a fresh binhex docker. Same damn result! I feel like I'm missing some stupid important step, but I don't know what it would be! I don't even remember what it looks like to set up a new server... shouldn't there be a setup wizard? Is there a way to force it? It just keeps searching for an existing one. Ugh...

 

Thanks for trying though, I appreciate it. I'll hit that forum up too.

Screenshot 2019-04-04 00.27.21.png

Edited by owtlaw333
Link to comment
5 hours ago, owtlaw333 said:

So I hit Remove and now I get this... I tried logging out and in, I even tried a fresh binhex docker. Same damn result! I feel like I'm missing some stupid important step, but I don't know what it would be! I don't even remember what it looks like to set up a new server... shouldn't there be a setup wizard? Is there a way to force it? It just keeps searching for an existing one. Ugh...

 

Thanks for trying though, I appreciate it. I'll hit that forum up too.

Screenshot 2019-04-04 00.27.21.png

Is that in host networking? If not, try host networking. If so, are you on the same network subnet? If not, you need to be. You can ssh tunnel to your host. See the "on a different network" heading at the bottom of this page: https://support.plex.tv/articles/200288586-installation/

Link to comment
On 4/3/2019 at 7:04 PM, aptalca said:

You're confusing different tags.

 

...

 

I hope that's clear.

 

If you simply want to use version 1.15.1.791-8bec0f76c, the easiest way would be to set the "VERSION" variable to "docker" so it doesn't do any updates during container start, and use the image "linuxserver/plex:1.15.1.791-8bec0f76c-ls11" so you'll use the image that comes with that version with no in container updates

I hadn't understood the difference. Thank you for clearly explaining how all that works.

 

That new knowledge, mixed with your instructions got me up and running as desired. Thank you very much!!!

Link to comment
On 4/4/2019 at 5:45 AM, aptalca said:

Is that in host networking? If not, try host networking. If so, are you on the same network subnet? If not, you need to be. You can ssh tunnel to your host. See the "on a different network" heading at the bottom of this page: https://support.plex.tv/articles/200288586-installation/

Definitely on the same network and haven't changed network settings in years (the old docker still functions with no issue.) BUT you triggered a memory of having to forward ports and whatnot back when, so I wiped out a few lines on the router and BOOM... setup wizard activated! Thank you!

 

It's currently scanning my library, but it looks like I'm going to be forced to start from scratch since it's treating everything as new. Once it's done I might try re-copying everything from the old docker, but I doubt it'll work 😞 We'll see. I don't even know how much work I'm getting myself self into given all the custom art, sorting and collections I have set up 😣

Link to comment

Are you guys seeing the PMS docker container fail to upgrade?

 

Atempting to upgrade to: 1.15.3.876-ad6e39743
https://downloads.plex.tv/plex-media-server/1.15.3.876-ad6e39743/plexmediaserver_1.15.3.876-ad6e39743_amd64.deb
2019-04-09 14:18:05 ERROR 404: Not Found.

Quote

 

 

It looks like the folks at Plex changed their path?

 

https://downloads.plex.tv/plex-media-server-new/1.15.3.876-ad6e39743/debian/plexmediaserver_1.15.3.876-ad6e39743_amd64.deb

 

Update: I selected "force update" and Unraid redeployed the container. All is well now.  Something changed on the Plex side as well as something on the container side.  Unfortunately, Unraid didn't update the container nor did it believe it was outdated.  My version was set to "latest" too.  

 

Edited by TheBrian
Link to comment
46 minutes ago, sfnetwork said:

same issue here...

Is there a work around to update or should I temporary switch to another source in meantime?

It's a long time since we updated the container to use the new download location.

Do a force update of the plex container and it should update.

Link to comment
3 hours ago, saarg said:

It's a long time since we updated the container to use the new download location.

Do a force update of the plex container and it should update.

Yeah, I tried that already, same error...

PS. in case it matters, a while back I changed from official plex to this one by just changing the repository, it was working fine though and updating...
Could there be a setting from the other container causing me this issue?

Link to comment
11 minutes ago, sfnetwork said:

Yeah, I tried that already, same error...

PS. in case it matters, a while back I changed from official plex to this one by just changing the repository, it was working fine though and updating...
Could there be a setting from the other container causing me this issue?

Post your container settings

Link to comment
1 hour ago, sfnetwork said:

here it is:
 

2019-04-13 08_18_02-Window.png

 

You need to change from using plex Inc template to ours as you don't have all the needed variables to get it to work as it should. 

Stop the container, take a backup of your plex appdata, then search CA and install our plex version using the exact same volume mappings for media and appdata. That should get you running. But might be the appdata permission is screwed as you just changed the repository to ours and didn't add the PUID and PGID. 

Link to comment
2 hours ago, saarg said:

 

You need to change from using plex Inc template to ours as you don't have all the needed variables to get it to work as it should. 

Stop the container, take a backup of your plex appdata, then search CA and install our plex version using the exact same volume mappings for media and appdata. That should get you running. But might be the appdata permission is screwed as you just changed the repository to ours and didn't add the PUID and PGID. 

thank you very much it worked!
I stopped to container, install this one from CA and set it up the exact same way for the paths , appdata assignment and name.
It ran a permission process and it started without error and up to date.
 

2019-04-13 12_47_26-Window.png

Link to comment

New help request. I'm attempting to move from the needo plex docker to linuxserver plex docker. I've pointed the config of the new linuxserver docker to the same /config location as needo. I get a fatal error and nothing will come up. Here's the entire log file when I try to start. Any help would be appreciated.

 

Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Plex Media Server v1.15.4.919-8e2884e4b - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT -04:00
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Linux version: 4.18.20-unRAID, language: en-US
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Processor AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Apr 13, 2019 19:19:54.141 [0x14bf7d583780] ERROR - SQLITE3:(nil), 5386, os_unix.c:37072: (19) mmap(/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm) - No such device
Apr 13, 2019 19:19:54.141 [0x14bf7d583780] ERROR - SQLITE3:(nil), 5386, disk I/O error in "PRAGMA cache_size=2000"
Apr 13, 2019 19:19:54.142 [0x14bf7d583780] ERROR - Database corruption: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000
Apr 13, 2019 19:19:54.142 [0x14bf7d583780] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE)

 

Link to comment
New help request. I'm attempting to move from the needo plex docker to linuxserver plex docker. I've pointed the config of the new linuxserver docker to the same /config location as needo. I get a fatal error and nothing will come up. Here's the entire log file when I try to start. Any help would be appreciated.
 
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Plex Media Server v1.15.4.919-8e2884e4b - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT -04:00
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Linux version: 4.18.20-unRAID, language: en-US
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - Processor AMD A10-7850K Radeon R7, 12 Compute Cores 4C+8G
Apr 13, 2019 19:19:54.139 [0x14bf7077e700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Apr 13, 2019 19:19:54.141 [0x14bf7d583780] ERROR - SQLITE3:(nil), 5386, os_unix.c:37072: (19) mmap(/config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-shm) - No such device
Apr 13, 2019 19:19:54.141 [0x14bf7d583780] ERROR - SQLITE3:(nil), 5386, disk I/O error in "PRAGMA cache_size=2000"
Apr 13, 2019 19:19:54.142 [0x14bf7d583780] ERROR - Database corruption: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000
Apr 13, 2019 19:19:54.142 [0x14bf7d583780] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE)
 
It's says your database is corrupt, not a DB expert but that probably would keep it from starting.

Sent from my SM-N960U using Tapatalk

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.