Minecraft (Bedrock / Console Edition) Server in Container Manager on a Synology NAS

In this guide I am going to take you through the steps to get a Minecraft Bedrock server up and running in Container Manager on a Synology NAS.

As Container Manager now supports using Docker Compose in the UI we will be using it as it will save you lots of time and steps!

What on earth is a Docker Compose?
Docker Compose allows us to define how Docker should set up one or more containers within a single configuration file. This file is yaml formatted and Container Manager uses the Projects feature to manage them.

What is the Bedrock Edition?

The Bedrock edition is the version used by all consoles such as the Nintendo Switch, Android, iPhone, and the Windows store edition. If you are looking for a JAVA edition see my other guide.

The documentation on how to use the server once it is running can be found here

https://github.com/itzg/docker-minecraft-bedrock-server

Let’s Begin

In order for you to successfully use this guide please complete the two additional steps below

• Step 2: Setting up a restricted Docker user

Folder Setup

First we need to set up a couple of folders to store our World and config files.

Using File Station create the following folders.

/docker/minecraftbedrock
/docker/projects/minecraftbedrock-compose

Container Set Up

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.

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.

services:
  minecraft-bedrock-server:
    image: itzg/minecraft-bedrock-server:latest
    container_name: minecraftbedrock
    tty: true
    stdin_open: true
    environment:
      - UID=1234 #CHANGE_TO_YOUR_UID
      - GID=65432 #CHANGE_TO_YOUR_GID
      - EULA=TRUE
      - VERSION=latest
      - SERVER_NAME=NAMEYOURSERVER
      - SERVER_PORT=19132
      - GAMEMODE=survival
      - DIFFICULTY=normal
      - ONLINE_MODE=true
      - OPS=SEE BELOW
      - ALLOW_LIST=true
    volumes:
      - /volume1/docker/minecraftbedrock:/data
    ports:
      - 19132:19132/udp
    security_opt:
      - no-new-privileges:true
    restart: unless-stopped

Editing the Config and Environment Variables

Let’s make some edits to the compose in order to customise the server. I am covering the basics here, ITZG has great information over on the documentation which covers the additional variables you can change including how to give permissions to your users.

Take note that some items are UPPERCASE and some are lowercase. This is how they should be set.

Once you have made all your required edits click ‘Next’

Nothing to change on the next screen click ‘Next’ again..

On the final screen just click ‘Done’ and you will see a new window appear which will kick of downloading of the required container image and configure your server.

Adding People to the White List

We can now add additional people to the White List otherwise you will get errors when they attempt to connect

Open up container manager and within the Container list select the Bedrock Server and click Details.

On the next screen click ‘Action’ then ‘Open terminal’

On the Terminal that appears type allowlist add then the exact name of the Friend you want to add including any Capital letters and press Enter.

You can repeat this step for each player you want to add including you.

Connecting to the Server

There are two ways to connect to the server, either via the Friends tab or by adding it manually to the Servers tab in Minecraft. Using your NAS IP:19132

(Optional Extra for Remote Play)

So your friends have an easy way to play remotely lets set up an address for them to connect to, please note that the section below opens port 443 however you will also need to forward port 19132.

External Access

You have some choices when it comes to making your new container accessible from outside your home network, these come with different levels of security and convenience. This mini section is generic but covers the basics of getting this guide up and running and is entirely optional.

• Synology’s DDNS (Dynamic Domain Name System) with a TLS Certificate and Reverse Proxy
  This is useful if you have some family members or friends that need access to something like Overseerr or Jellyseer and is covered below.
  
  
• Tailscale or Wireguard VPN
  If just you are accessing these services, and you don’t want to expose them to the internet this would be the more secure choice. See my other separate guides.
  
  
• Cloudflare Tunnels
  I don’t currently use these, so I would recommend watching the Wundertech guide on how they work.

A note on Double NAT or CGNAT
Unfortunately more ISPs are moving to these methods of address allocation as the IPv4 address space is getting low on available addresses. If your ISP is doing this your choices are more limited.

You can test if this is the case by checking the WAN IP on your Router/Modem settings and then comparing it to the one shown on portchecker.co. If they are different you are likely Double NAT and will either need to see if you can pay your ISP for a standard IPv4 address or use Tailscale or Cloudflare Tunnels for access.

Using the built-in tools on DSM

The first step of this process is to forward port 443 on your Router to your NAS IP Address, how you do this will depend on your router model, so please refer to its manual.

Router (External):443 > NASIP (Internal):443

Next make sure you have registered for a Synology Account as we are going to be using their DDNS service. https://account.synology.com/en-uk/register/ If you already have this set up move to the next step.

DDNS (Dynamic Domain Name System)

A DDNS address allows you to get external access to your container via an address provided by Synology, this is useful on home internet connections where your ISP will change your IP address on a semi-regular basis.

In the DSM Control panel go to ‘External Access’ and then to the ‘DDNS’ tab

Click on ‘Add’, then fill out the following sections.

Now press OK, DSM will apply your settings. It can take a few moments to set up and the DSM interface will refresh. You will likely receive a certificate error which you will need to accept to get back into DSM.

Reverse Proxy

We are going to set up a reverse proxy subdomain for the address you just register. This means you and your users can access the container without using a port number as it will route all traffic through the secure 443 port.

Go back into the Control Panel and access the ‘Login Portal’ then in the ‘Advanced’ tab click ‘Reverse Proxy’ and then click on ‘Create’.

We are now going to enter some rules, so when you or your users access the URL specified the request will automatically be sent to the containers web UI.

Use the settings below, you will need to amend the Hostname sections in line with the hostname you registered earlier, and the IP of your NAS.

On the second tab ‘Custom Header’ click on Create then WebSocket, this will add two entries for WebSockets to function correctly, you can now press save.

You should now be able to access the web UI of the container by going to the address you just set up in the reverse proxy, it will be a secure connection, and you should have no certificate errors.

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.