Studio Server on a Synology NAS

Community provided instructions!
Whilst I don't personally own a Synology NAS (I use, support and test on Debian, Ubuntu, TrueNAS, Proxmox and UnRAID), the below instructions have been proven to work for Synology NAS users and has been provided by a member of the community. I am currently building a fund to purchase a Synology NAS (purely for testing Studio Server on and that will enable me to provide actual support to Synology users). If you would like to contribute to this fund and enable me to fully/officially support Synology users faster, please consider donating today.

In order to run the Studio Server software on a Synology NAS you will first need to configure a "macvlan" (but don't worry, this is super easy to set up) so that Studio Server will work as you expect, this is due to the fact that Synology already listens on one of the ports required by Studio Server.

You can follow the steps below to set up a macvlan on your Synology NAS, and then we'll continue on and deploy the Studio Server software.

Before we continue though, please be aware that if you are NOT using a Synology NAS then you should follow the "generic" installation notes on the main Studio Server software page instead.


In the below example, it is assumed that your LAN IP address (subnet and gateway) is 192.168.1.x and, the IP address that will be used to access the Studio Server will be configured as You may need to customise these IP addresses/ranges to match your network requirements!

Firstly we must create the "macvlan" (essentially a dedicated/virtual IP address) that Docker will use to "serve" the Studio Server software on, we can do this by running the following command at the Synology Shell (SSH terminal):

sudo docker network create -d macvlan \
    -o parent=eth0 \
    --subnet= \
    --gateway= \
    --ip-range= \
You should then create a few directories on your Synology NAS where Studio Server will store it's data and configurations. Using the terminal, run the following commands:
cd /volume1/docker
mkdir studio-server
cd studio-server
mkdir backups
mkdir jobs
mkdir hooks
mkdir database

At this point we are ready to deploy the container, run the following command in order to automatically pull the latest version and set up and deploy the container:

Please note that the below example uses the "Europe/London" timezone and therefore, depending on your local timezone, you will to change this!

sudo docker run --name studio-server \
    -d \
    --restart unless-stopped \
    --network studio_network \
    -e TZ=Europe/London \
    -p \
    -p 50059:50059 \
    -p 8543:8543 \
    -v /volume1/docker/studio-server/hooks/:/var/studio-server/hooks/ \
    -v /volume1/docker/studio-server/database/:/var/studio-server/database/ \
    -v /volume1/docker/studio-server/backups/:/var/studio-server/backups/ \
    -v /volume1/docker/studio-server/jobs/:/etc/cron.d/ \

Once the container image has been pulled and the container is started, it will automatically configure itself for "first use" and so, give it a few seconds before navigating to the web-based administration panel to finalise the configuration (set up an admin account password), to do this, simply use a web browser and navigate to this URL: http://{YOUR_MACVLAN_IP_ADDRESS}:8543, using the above examples, this would be

If you would like to see a step-by-step video of how to set this up on a Linux Server, please watch this video tutorial on YouTube.

Docker container configuration notes

Other configuration settings can be found on the main Studio Server page.

Scroll to top