Skip to content

Plex in Container Manager on a Synology NAS (Hardware Transcoding)

Important or Recent Updates
Historic UpdatesDate
New DSM7.2 Container Manager Update 01/05/2023
Added additional security option to the compose to restrict the container from gaining new privileges as well as umask variable25/10/2023
Historic Updates

In this guide I am going to take you through the setup of Plex in Docker using Container Manager.

Plex Pass

You will only benefit from hardware transcoding if you have an active Plex Pass either monthly or lifetime. If you don’t have one you can either follow this guide or jump over to the non hardware transcoding version.

Does my Synology support Hardware Transcoding?

Before we do anything else, you need to make sure your model of Synology has hardware transcoding capabilities. You need to do a quick lookup via the linked Google Sheet below, this is updated by Plex and makes it super easy to look up your model of NAS.

If you find that hardware transcoding is not available on your model you can jump back over to the standard guide on the menu.

Let’s Begin

As usual, it’s important you complete the two proceeding guides which will get your folder structure and docker, user setup.

Folder Setup

Let’s start by getting some folders set up for the container to use. Open up File Station create the following.


Container Manager

Next we are going to set up a ‘Project’ in Container Manager. Open up Container Manager and click on Project then on the right-hand side click ‘Create’.

In the next screen we will set up our General Settings, enter the following:

Project Name:plex
Source:Create docker-compose.yml

Next we are going to drop in our docker compose configuration copy all the code in the box below and paste it into line ‘1’ just like the screenshot.

    image: linuxserver/plex:latest
    container_name: plex
    network_mode: host
      - PGID=65432 #CHANGE_TO_YOUR_GID
      - TZ=Europe/London #CHANGE_TO_YOUR_TZ
      - UMASK=022
      - VERSION=latest
      - PLEX_CLAIM= #Your Plex Claim Code
      - /volume1/docker/plex:/config
      - /volume1/data/media:/data/media
      - /dev/dri:/dev/dri
      - no-new-privileges:true
    restart: always

A note on Network Mode

You will notice that for Plex we don’t put it on the normal bridge network, this is because DSM reserves the DLNA ports Plex requires in order to use DLNA. So we run in Host mode, so it can share the ports.

Environment Variables

We need to make some changes in order for the container to have the correct permissions to save its configuration files and to have access to your media.

PUID(required) The UID you obtained in the user setup guide
PGID(required) The GID you obtained in the user setup guide
TZ(required) Your timezone
PLEX_CLAIMPlease note the PLEX_CLAIM variable is optional and not always required. You can remove this line if you don’t need it or come back and add it if you are unable to sign in to your server on start up.

To get the code go to and sign in, then put the code you receive after the ‘PLEX_CLAIM=’. You have 4 mins to finish the guide after doing this, so best to grab it just before running the project.


I have pre-filled this section to pass the correct paths, the only thing that you may need to change is the /volume1/ if your file paths are on a different volume.

Click ‘Next’

You do not need to enable anything on the ‘Web portal settings’ screen click ‘Next’ again.

On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!

The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.

You will now see your Plex running and should have a green status on the left-hand side.

Firewall Exceptions

(Skip if you don’t have the Firewall configured)

If you have enabled and configured the Synology Firewall you will need to create exceptions for any containers that have a Web UI or have any incoming or outgoing connections. This section covers the basics of how to add these. (Please note this is a generic section and will not show the specific ports used in this guide however it applies in the same way)

Also, I would like to refer people to the great guide on getting the Firewall correctly configured over on WunderTechs site.

Head into the Control Panel> Security > Firewall, from here click Edit Rules for the profile you set up when you enabled the Firewall.

Next click on Create and you will see the screen below. Source IP and Action will be automatically selected to All and Allow, I will leave it up to you as to your own preference on whether you want to lock down specific Source IPs from having access. In this example we will leave as All.

You will now choose ‘Custom‘ and then the Custom button

Now select Destination from the drop-down menu, most web based containers require TCP access but check the guide as it will show the port and protocol. Then add comma separated ports. Then press OK.

Click OK a couple of times to get back to the main screen. You will see by default the new rule is added to the bottom of the list. You must always have your Block All rule last in the list as the rules are applied top down so move your container up.

You have now completed the Firewall changes and can continue with the guide.

Plex Initial Setup

After a few minutes you should be able to access the server and go through the Plex setup by going to the IP of your NAS in your browser followed by port 32400/web/


You will be asked to sign in or sign up for an account if you don’t have one already.

You should now be able to add your media which will be in the /data/media folder within Plex

Once you have got to the main Plex interface make sure you go into the settings and turn on

  • Enable HDR tone mapping
  • Use hardware acceleration when available
  • Use hardware-accelerated video encoding

That’s it you are all setup. When a new server update is available you will just need to restart the container, and it will automatically download the latest update.

Buy Me a Coffee or a Beer

If you have found my site useful please consider pinging me a tip as it helps cover the cost of running things or just lets me get the odd beverage. Plus 10% goes to the devs of the apps I do guides for every year.

Published inPlex 7.2


  1. Manning Manning

    Hi, this all works great for me! However I’m a bit confused by the synobridge host networking. If I wanted one of my apps on the synobridge network (Notifiarr) to talk to Plex, what IP would I give it?

    • Dr_Frankenstein Dr_Frankenstein

      Hey the bridge is purely for internal communication between containers so if Plex is on Host Networking use the IP of your NAS 🙂

      • Manning Manning

        Thanks! I guess I was overthinking it. Turns out Notifiarr can see Plex at 🙂

  2. Paul Crompton Paul Crompton


    Everything seems to work but for some files I get

    Playback Error
    Conversion failed. A required codec could not be found or failed to install.

    How can I fix that? Cheers!

  3. Monny Monny

    Hey! This has worked great for me for a while now, however today I manually restated my NAS and when everything kicked back on, my Plex server migrated to a brand new server. So I had to reassign library access and plex had to rescan all my media for intros/credits and I lost all my watch history. Any advice on how to prevent it from creating a new plex server when I restart my device? It’s happened twice now.

    • Dr_Frankenstein Dr_Frankenstein

      This shouldn’t be happening, all your settings should be stored in the /docker/plex folder are they in there? It sounds like your mounts are not working if everything is lost on a restart / update.

      • Monny Monny

        I do have all my data stored in the /docker/plex folder, and I figured out what was going on. I had the plex media server app for Synology installed as well. It was creating a second library for that app, when I should just be using the plex container app. The problem was the container is showing green in container manager, but when I go the logs it’s giving me a “Plex Media Server Crashed” report. So the only server that was working is the native app, which I have since deleted. Would you happen to have a discord or another way for me to send the container manager log and see if you can help me figure out why it’s crashing?

        • Dr_Frankenstein Dr_Frankenstein

          Yeah Discord link is on the left menu and also on the Help ME! Page also on the left menu

  4. beezer beezer

    Hello, I was able to get the plex container running. Had a question about the firewall section of this guide. My Plex container doesn’t show up in the list of apps to select like the other “arr” apps and gluetun did. Did I do something wrong? I was able to go through initial setup of plex and everything, yet plex is saying my server is unavailable.

    • Dr_Frankenstein Dr_Frankenstein

      Hey, if it’s not showing you can manually create an exception for port 32400 as a starter to get the ui. I would also check the Plex container logs to make sure it has started up successfully

  5. Fedor Fedor

    Hi Dr,

    I used your previous guide and it all works fine. Is there a way to migrate to this newest setup/guide without losing all my plex settings?

    • Dr_Frankenstein Dr_Frankenstein

      Hey, yes if you used the compose version it’s nice and easy just setup in Container Manager as per the guide and point at the same files. This guide marries up with the same folders. Usual caveats to make sure you have backups but it should be seamless.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed. – writing Synology Docker Guides since 2016 – Join My Discord!