Important or Recent Updates
Historic Updates | Date |
---|---|
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 variable | 25/10/2023 |
Somehow at some point a paragraph about forwarding port 32400 went missing, I had never added it! But it’s in now!! | 13/06/2024 |
Changed ‘version’ variable to ‘docker’ this will stop in container server updates! | 01/07/2024 |
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.
/docker/projects/plex-compose
/docker/plex
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/10/image-91.png)
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’.
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/05/image-1.png)
In the next screen we will set up our General Settings, enter the following:
Section | Setting |
---|---|
Project Name: | plex |
Path: | /docker/projects/plex-compose |
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.
![](https://drfrankenstein.co.uk/wp-content/uploads/2024/07/image-1.png)
services:
plex:
image: linuxserver/plex:latest
container_name: plex
network_mode: host
environment:
- PUID=1234 #CHANGE_TO_YOUR_UID
- PGID=65432 #CHANGE_TO_YOUR_GID
- TZ=Europe/London #CHANGE_TO_YOUR_TZ
- UMASK=022
- VERSION=docker
- PLEX_CLAIM= #Your Plex Claim Code
volumes:
- /volume1/docker/plex:/config
- /volume1/data/media:/data/media
devices:
- /dev/dri:/dev/dri
security_opt:
- 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.
Variable | Value |
---|---|
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 wikipedia.org/wiki/List_of_tz_database_time_zones |
PLEX_CLAIM | Please 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 https://plex.tv/claim 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. |
Volumes
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.
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/05/image-4.png)
On the final screen click ‘Done’ which will begin the download of the container images and once downloaded they will be launched!
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/05/image-5.png)
The image will now be downloaded and extracted. You should see ‘Code 0’ when it has finished.
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/05/image-6.png)
You will now see your Plex running and should have a green status on the left-hand side.
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/05/image-7-1024x494.png)
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.
Make a note of the ports used in the compose section of the guide, these will be the ones you need to create exceptions for.
(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.
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/10/image-2.png)
Head into the Control Panel
> Security
> Firewall
, from here click Edit Rules
for the profile you set up when you enabled the Firewall.
![](https://drfrankenstein.co.uk/wp-content/uploads/2023/10/image-3.png)
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.
![](https://drfrankenstein.co.uk/wp-content/uploads/2024/01/2024-01-22_20-44.jpg)
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.
![](https://drfrankenstein.co.uk/wp-content/uploads/2024/01/2024-01-22_20-49.jpg)
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.
![](https://drfrankenstein.co.uk/wp-content/uploads/2024/01/2024-01-22_21-02-1.jpg)
You have now completed the Firewall changes and can continue with the guide.
Port Forwarding
In order to use Plex remotely and stream your local media you need to forward port 32400 from your Router to the NAS IP on the same port. This varies for everyone’s router so check the manual on how to do this.
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/
e.g. 192.168.0.45:32400/web/
You will be asked to sign in or sign up for an account if you don’t have one already.
![](https://drfrankenstein.co.uk/wp-content/uploads/2021/12/image-24.png)
You should now be able to add your media which will be in the /data/media folder within Plex
![](https://drfrankenstein.co.uk/wp-content/uploads/2022/08/image-3.png)
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
![](https://drfrankenstein.co.uk/wp-content/uploads/2021/12/image-27-1024x442.png)
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.
Looking for some help, join our Discord community
If you are struggling with any steps in the guides or looking to branch out into other containers join our Discord community!
Buy me a beverage!
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 stay hydrated. Plus 10% goes to the devs of the apps I do guides for every year.
I’ve been fighting with “slow response time” when attempting to access my 920+, thought no CPU constraints were being shown. Finally noticed the reported upstream data was consistently 2-300K more than I would have expected, which combined with other things put me pretty closed to a saturated uplink.
Playing a hunch, (and after backing up the plex app data folder), I rolled back to 1.40.3.8555-fef15d30c-ls221 (from the latest which is 1.40.4.8679-424562606-ls222), and everything seems to have settled down.
Wow, I wish I’d found Dr Frank BEFORE that whole “geminilake hardware transcoding broken for MONTHS/multiple versions” debacle.
I have started locking into known working versions on some containers as sometimes being on the bleeding edge comes with issues. They key is not to leave it too long between updates if fixing in a version number 🙂
possible false alarm. further reading indicated some of the new functionality required a meta data refresh, so I re-upgraded and forced a meta refresh, and everything seems to be behaving now.