New plex install on docker (NAS)

[zoubinho]

Hi,
I did reinstall plex on my NAS 920+ on a docker image using default config. The user running the docker image is the same capable of accessing the data folder (media).
Docker works fine, with no error.

Plex was able to start and scan for all the files in the media folder and start indexing.

Problem is: when trying to play a video, it indicates “The file associated with this video is not accessible by the server. Please verify that the file exists and the necessary drive is accessible.”

Is there any way some rights prevents this, or would this be due to some media file path config that has been tempered? Though, destination files haven’t moved and same paths apply. Thanks

[ChuckPa]

A few things:

1. You dont need to use the docker image for HW transcoding and tonemapping (if that’s what you wanted).

2. Making certain all the permissions are set is important. Please see this:

Syno FAQ has many answers:

Synology FAQ - Questions, Answers, and a few How-To's

Synology Frequently Asked Questions Table of Contents Intro: Posting in the Plex Synology Forum DSM 6 & 7 FAQ Some of these FAQ apply equally to DSM 7 and 6. Others do not. Please read carefully before proceeding. Getting access to the Logs Have I installed the latest version…? Which version do I need, Intel or ARM? 3a. Using Plex’s package signing public key - DSM 6 LAN addressing requirements - RFC1918 specification for local LAN? First run & Setup Recommended Media Organization and A…

You want to look at:

Synology FAQ - Questions, Answers, and a few How-To's

FAQ 29 - DSM 7 - Give PlexMediaServer access to your media When you migrate to DSM 7, or are installing a server for the first time, folks forget to read the popup at the end of every installation which tells them about how to set permissions. This FAQ shows in detail how to do what those instructions state. When might you need to perform these steps? When upgrading, changing permissions from Plex to PlexMediaServer is overlooked. Installing Plex for the first time, new installation…

[zoubinho]

Thanks for your reply ChuckPa.
Beyond the personal interest in getting my hands around Docker more, I keep reading everywhere that hardware transcoding can be done only using Docker for plex.

But anyway, after reading the FAQ you pointed out, this is indeed for a local install on NAS directly, where the apps privileges are granted to run plex and access its resources (media included).

I think I understand the concern referred above for local install but for image ones, I’m not sure how to translate that.
And given my config, I think my docker has enough permission:

• can load media folders
• can scan files for metadata
  x cannot play the video file

[ChuckPa]

@zoubinho

I keep reading everywhere that hardware transcoding can be done only using Docker for plex.

Hardware transcoding has always existing for the native app.

The material I suspect you’re seeing is old and now outdated.

PMS comes with all the tone mapping modules included in the native package SPK.

If you download PMS from Package Center (1.29.2.6364). you’ll find it’s already working for you as soon as you enable it in your settings.

I’ve taken care of the rest of the package/hardware management to make HW transcoding immediately available if the host supports it.

[FordGuy61]

@zoubinho

I keep reading everywhere that hardware transcoding can be done only using Docker for plex

Docker is not a requirement for hardware accelerated transcoding or tonemapping.

Plex has supported hardware accelerated transcoding with a native installation for several years. I can’t tell you an exact date, but it worked the day my DS918+ arrived in November 2017.

Plex has supported hardware accelerated tonemapping with a native installation since Plex Media Server 1.29.1.6260, released in September 2022.

PMS 1.29.1.6260 Announcement

• (Linux) External user-mode graphics drivers no longer need to be installed to use hardware tone mapping on Intel systems

[zoubinho]

Noted. Thanks for providing me with up-to-date information. I’ll make sure I’ll read more if I don’t find solution to my blocking point.

Just to clarify, the question is how to make plex running on a docker container, where my install is successful, the scanning of the libraries is successful, but just the running of a media runs into an error.

[ChuckPa]

@zoubinho

Just to clarify, the question is how to make plex running on a docker container, where my install is successful, the scanning of the libraries is successful, but just the running of a media runs into an error.

You would need to provide us with the DEBUG server logs ZIP file to know what happened (which you download right after the failed playback)

With DEBUG on (the default) we can see what PMS wanted to do, tried to do, then ultimately failed.

Unless you create a docker container on Synology with the command line, you won’t get hardware transcoding. This will lead to the “Not Powerful Enough” message

[zoubinho]

Thanks Chuck, that’s helpful.
Let me revert back whenever I manage to make it work. I found some of your work on this forum, I might be able to get my hands around.
Just a side note: on DSM 7 - Plex Media Server - Release Info & Migration instructions, you stated:

• DO NOT use the Package Center version. Package Center offers Beta which is no longer compatible. You must download Plex from Plex.tv/downloads.

as of october 2021. Do you still concur, or did the Plex team took your feedback into consideration and now users can access the plex distrib directly from the Package center? Thanks

[FordGuy61]

@zoubinho

The document is out of date.

The version of Plex Media Server available via Synology Package Center was recently updated from 1.21.0.3744 (beta) to 1.29.2.6364.

1.29.2.6364 is fully compatible with DSM 7 (not including 7.2 beta). It is not a problem to install it via Synology Package Center.

Note: Do not install Synology DSM 7.2 beta. Plex Media Server has not been tested against DSM 7.2 beta. Plex Media Server compatibility with DSM 7.2 beta is unknown.