Minecraft Bedrock Edition – Ubuntu Dedicated Server Guide

Minecraft Bedrock Edition Logo
Minecraft: Bedrock Edition Logo

Minecraft Bedrock Edition is the version of Minecraft that powers the iPhone / Android versions (formerly Minecraft Pocket Edition), the Xbox / PlayStation / Nintendo Switch editions and the free Windows 10 Minecraft edition.

Mojang has released a dedicated server which is considered to be in alpha testing.  I have found it to be very stable and able to run on a wide variety of hardware.

This script and guide are written to help you get a robust Minecraft Bedrock dedicated server up and running in only a few minutes!

This is the standalone version. The easiest and most problem-free way to run this is using Docker (installed as simply as sudo apt install docker.io): Legendary Minecraft Bedrock Container

I’ve also released a way for Java and Bedrock players to play on the same server using Geyser: Minecraft Java + Bedrock Server Together – Geyser + Floodgate

It’s now possible to convert your worlds between Bedrock and Java versions. Check out my guide on Chunker here for more information.

Features

  • Sets up the official Minecraft Bedrock Server (currently in alpha testing)
  • Fully operational Minecraft Bedrock edition server in a couple of minutes
  • Ubuntu / Debian distributions supported
  • Sets up Minecraft as a system service with option to autostart at boot
  • Automatic backups when server restarts
  • Supports multiple instances — you can run multiple Bedrock servers on the same system
  • Updates automatically to the latest or user-defined version when server is started
  • Easy control of server with start.sh, stop.sh and restart.sh scripts
  • Adds logging with timestamps to “logs” directory
  • Optional scheduled daily restart of server using cron

Requirements

  • A computer with a 64 bit processor (if you are trying to use ARM read my article on the limitations). 32 bit binaries of the official server are not available so it needs to be 64 bit!
  • 1 GB of RAM or higher
  • The only officially supported platform by Microsoft is Ubuntu 22.04 / 20.04 (current LTS, recommended)
  • Other Linux flavors supported by this script as well as long as they use systemd (for the service). The script assumes apt is installed but there are minimal dependencies so you could install these on another distro (that doesn’t have apt present) and use the script normally.

Recommended Gear

Game Editions

Minecraft: Bedrock Edition is the “Windows 10” version of Minecraft as well as the version of Minecraft on the Xbox / Playstation / Switch. The versions of Minecraft for Android and iOS are also the Bedrock edition.

All of these versions support cross-platform play with each other (but not with the Java edition).

Minecraft Bedrock Digital Code
Minecraft Bedrock Digital Code

This is the PC Minecraft for Windows 10 (Bedrock) edition of Minecraft. It is able to play cross-platform with other players on Android / iOS / Playstation / Xbox / Switch. Available as a code that is instantly activated to give you permanent access to the game!

Links: Amazon.com*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*

Minecraft Bedrock Playstation
Minecraft Bedrock Playstation

The Sony PlayStation version of Minecraft: Bedrock edition.

Links: Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.se*, Amazon.sg*

Minecraft Bedrock Nintendo Switch
Minecraft Bedrock Nintendo Switch

This is the Nintendo Switch version of Minecraft: Bedrock edition.

Links: Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*

Minecraft Bedrock Xbox One
Minecraft Bedrock Xbox One

This is the Microsoft Xbox version of Minecraft: Bedrock edition.

Links: Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.sg*

Recommended Storage (Solid State Drive)

I strongly recommend a Solid State drive (SSD) for your server. This is because Minecraft is constantly reading/storing chunks to the disk which makes I/O performance very important.

These are much cheaper than they used to be. Here’s a decent 120 GB one (higher capacity options are available) at a very low price:

Kingston A400 SSD
Kingston A400 2.5″ SATA SSD

The Kingston A400 is reliable, widely available around the world, has low power requirements and performs very well. It’s also very affordable. This drive has been benchmarked over 1000 times at Pi Benchmarks and is the #1 most popular SSD among the community!

Links: AliExpress*, Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*

If you have a M.2 NVME slot in your motherboard you can go with a high end drive. This will give your server maximum performance even if a large number of players are running around on the server changing blocks and triggering disk writes.

This is the one I have in my machine. These range from 250 GB to 2 TB depending on how big your server might grow:

The Samsung 980 Pro (NVMe) is a professional grade SSD and one of the fastest in the world. The Samsung NVMe drives have been at the top of this category for a long time and are well trusted for both their performance and reliability / long life.

Links: AliExpress*, Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*

Computer / CPU / Memory

Almost any PC made in the last few years will be a x86_64 bit computer. If you have an older computer around that isn’t being used then it will most likely have the right CPU and amount of memory (as well as fast storage) to run a basic server.

Throwing a SSD in one of these older computers will provide an excellent server experience for small and larger player counts.

The speed of your storage will make the largest difference. Older HDDs are going to have significantly slower performance than any modern SSD even with all other hardware equal. This is because the Minecraft server is constantly reading/writing chunks of your world as well as updates to it to the disk so this tends to be the bottleneck.

Operating System

I highly recommend using Ubuntu Server to run the Minecraft dedicated server. It is available here.

At the time of writing the current version is Ubuntu Server 20.04. This is a secure and robust operating system and will leave plenty of resources available for the server to run.

The script should run on any Debian based flavor of Linux but since the Minecraft Bedrock server is compiled natively for Ubuntu I recommend sticking with it. If you have a GUI flavor of Ubuntu and a decent PC (>= 2 GB of RAM) the server will work just fine on it.

Note: People have reported in the comments that Ubuntu 16.x is no longer working with the latest official Mojang binaries. Ubuntu 18.04 is the minimum requirement for the latest versions, and 20.04 is recommended!

Installation

Log into your Linux server either using SSH or a mouse and keyboard and paste/type the following command:

curl https://raw.githubusercontent.com/TheRemote/MinecraftBedrockServer/master/SetupMinecraft.sh | bash

The script will setup the Minecraft sever and ask you some questions on how to configure it. I’ll explain here what they mean.

The first question will be the installation path. This is the root installation path for ALL servers you will have. If you add additional servers later you should select the exact same installation path. It should always be left as the default (~).

The only exception is if you have something like a completely dedicated disk for the Minecraft server. In that case you should always use the same root path of /mnt/yourdrive or wherever the path is for every new/additional server you install.

“Start Minecraft server at startup automatically (y/n)?” – This will set the Minecraft service to start automatically when your server boots. This is a great option to set up a Minecraft server that is always available.

“Automatically restart and backup server at 4am daily (y/n)?” – This will add a cron job to the server that reboots the server every day at 4am. This is great because every time the server restarts it backs up the server and updates to the latest version. See the “Scheduled Daily Reboots” section below for information on how to customize the time or remove the reboot.

That is it for the setup script. The server will finish configuring and start!

First Run

The server will start up and start displaying output to the console.

[2019-03-30 20:25:12 INFO] Starting Server
[2019-03-30 20:25:12 INFO] Version 1.10.0.7
[2019-03-30 20:25:12 INFO] Level Name: Bedrock level
[2019-03-30 20:25:12 INFO] Game mode: 0 Survival
[2019-03-30 20:25:12 INFO] Difficulty: 1 EASY
[2019-03-30 20:25:20 INFO] IPv4 supported, port: 19132
[2019-03-30 20:25:20 INFO] IPv6 supported, port: 19133
[2019-03-30 20:25:23 INFO] Server started.

Once you see the “Server started” line you will be able to connect from the client.

To add the server to the client open Minecraft and click “Play”. Then at the top of the screen select the “Servers” tab and click “Add Server”.

This will ask you for a Server Name and Server IP Address. For the name you can put anything and for the server IP address put the address of your Linux server. Leave the port as the default 19132. For more information on how to let people from outside your network on go to the “Port Forwarding” section below.

Now choose the server you just added in the list and connect!

Start, Stop and Restart Server

The server can be started, stopped and restarted two different ways. You can use the provided scripts in the Minecraft folder or you can use systemctl. Here are the commands:

cd ~/minecraftbe
./start.sh
./stop.sh
./restart.sh

-OR-

sudo systemctl start minecraftbe
sudo systemctl stop minecraftbe
sudo systemctl restart minecraftbe

Automatic Backups

The server backs up each time it starts. This helps you recover easily if something goes wrong. This system works best if you configured the server to restart daily since it means you will have a backup every day.

To access these backups type:

cd ~/minecraftbe/backups
ls

When a backup is made the filename will be the date and time the backup was taken. If you need to restore a backup it’s very easy. Substitute the timestamp in my example to the backup you want to roll back to. Type:

cd ~/minecraftbe
./stop.sh
rm -rf worlds
tar -xf backups/2019.02.15.22.06.30.tar.gz
./start.sh

Your world has now been restored! It’s a good idea to download these backups off the server periodically just in case the server’s storage fails.

Installing Resource Packs / RTX Support

For instructions on how to install resource packs (including optional RTX support) view my step by step Minecraft Bedrock Dedicated Server Resource Packs guide here.

Scheduled Daily Reboots

The daily reboots are scheduled using cron. It’s very easy to customize the time your server restarts.

To change the time that the server restarts type: crontab -e

This will open a window that will ask you to select a text editor (I find nano to be the easiest) and will show the cronjobs scheduled on the server. The Minecraft one will look like the following:

0 4 * * * /home/ubuntu/minecraftbe/restart.sh
Crontab's syntax layout
Crontab’s syntax layout

There are 5 fields here. The default restart time is set to reboot at 0 minutes of the 4th hour of the day (4 AM). The other 3 fields are left as * to represent every day of every month. Make any desired changes here and press Ctrl+X to exit nano and update the cronjob.

To remove the daily reboot simply delete the line and save.

Reconfigure / Update Scripts

The scripts can always be reconfigured and updated by downloading the latest SetupMinecraft.sh and running the installer again. It will update all of the scripts in the Minecraft directory and reinstall the startup service for you.

Running SetupMinecraft.sh again will also give you a chance to reconfigure options such as the memory dedicated to the server, daily reboots, starting the server on boot, etc.

This will not overwrite your world or any other data so it is safe to run!

Port Forwarding

If everyone on your server is on the same LAN or WiFi network as you then you don’t need to do this. If you want people to connect from outside your local network then you need to set up port forwarding on your router.

The process for this is different for every router so the best thing to do is just look at your router and find the model # and put that in google with port forwarding for easy instructions on how to do it for your specific router.

You want to forward port 19132. The type of connection is both TCP and UDP. On some routers you need to do both a TCP entry and then a second entry as UDP.

Once you do this people will be able to connect to your Minecraft server through your public IP address. This is different than your local IP which is usually a 192.x.x.x or 10.x.x.x. If you don’t know what that is just go to google and type “what’s my ip” and Google will kindly tell you!

Version Override

You can revert to a previous version with the revert.sh script included in your directory like this:

james@jamesgigabyte-linux:~/minecraftbe/james$ ./revert.sh
Set previous version in version_pin.txt: bedrock-server-1.19.10.20.zip

If you have a specific version you would like to run you can also create version_pin.txt yourself like this:

echo "bedrock-server-1.18.33.02.zip" > version_pin.txt

The version hold can be removed by deleting version_pin.txt. This will allow it to update to the latest version again!

Wired vs. Wireless

Going with an ethernet (wired) connection is going to be faster and more reliable. There’s so much wireless traffic and other interference in the air that running your server on WiFi is not recommended.

Even if it is working great 99% of the time it can ruin your experience very quickly if the WiFi drops for a couple of seconds and you get blown up by a creeper!

All that being said, the server works fine on wireless. The script will work fine as is with a wireless connection.

Benchmarking / Testing Storage

If you’re getting poor performance you may want to run my storage benchmark with:

sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash

PC results won’t show up on the site yet (it’s meant for Raspberry Pi) but it will run on Linux just fine and give you a score. If you search for the model of your drive on Pi Benchmarks you can compare your score with others and make sure the drive is performing correctly!

Troubleshooting Note – Oracle Virtual Machines

A very common problem people have with the Oracle Virtual Machine tutorials out there that typically show you how to use a free VM is that the VM is much more difficult to configure than just about any other product / offering out there.

It is because there are several steps you need to take to open the ports on the Oracle VM. You need to both:

  • Set the ingress ports (TCP/UDP) in the Virtual Cloud Network (VCN) security list
  • *and* set the ingress ports in a Network Security Group assigned to your instance

Both of these settings are typically required before you will be able to connect to your VM instance. This is purely configuration related and has nothing to do with the script or the Minecraft server itself.

I do not recommend this platform due to the configuration difficulty but the people who have gone through the pain of configuring an Oracle VM have had good experiences with it after that point. Just keep in mind it’s going to be a rough ride through the configuration for most people.

Troubleshooting Note – Hyper-V

There is a weird bug in Hyper-V that breaks UDP connections on the Minecraft server. The fix for this is that you have to use a Generation 1 VM with the Legacy LAN network driver.

Conclusion

The Minecraft Bedrock Edition dedicated server runs much better than previous third party servers in the past that were missing critical features. The performance is very good even on low end hardware. It has never been easier to set up a Minecraft Bedrock server.

If you have any feedback or suggestions let me know in the comment section. A lot of the changes and developments in this script and guide are directly from readers.

Have fun!

Other Resources

For a guide on how to set up resource packs check out my Minecraft Bedrock Resource Pack guide

If you’re trying to run this on the Raspberry Pi check out the Raspberry Pi specific guide here

1,556 thoughts on “Minecraft Bedrock Edition – Ubuntu Dedicated Server Guide”

  1. Avatar for Henry

    Greetings,

    I’m on Ubuntu 18.04 LTS, followed your tutorial and been playing for last three weeks. Today the server didn’t start, all I see on the logs when I manually start the server is:

    [2020-02-20 09:39:09 INFO] Starting Server
    [2020-02-20 09:39:09 INFO] Version 1.14.30.2
    [2020-02-20 09:39:09 INFO] Session ID e8b471d4-e4e0-43af-b9ac-3f97f9a62950
    [2020-02-20 09:39:09 INFO] Level Name: Bedrock Vanilla
    [2020-02-20 09:39:09 INFO] Game mode: 0 Survival
    [2020-02-20 09:39:09 INFO] Difficulty: 1 EASY
    [2020-02-20 09:39:09 ERROR] Network port occupied, can't start server.

    I’ve checked process running on the port 19132 or 19133 (IPv6) but nothing is running. If i change the level-name on server.properties the server starts as usual, but obviously my previous seed and constructions are missing.

    Today I downloaded the installer form minecraft web and copy my world to the new installation and I’m getting the same error. If it is a corrupted world problem, how can I restore to last version or migrate my world constructions.

    Thx.

    1. Avatar for James A. Chambers

      Hey Henry,

      It sounds like a duplicate of the server may already be running (it says network port occupied meaning it is in use already).

      Try the command ps -AF to list all processes and look for any instances of “screen” or the bedrock server. You can kill these processes by using the command kill and the PID for the process given from the ps command (example: kill 1056)

      Once you have killed them try restarting the server again and you should be in business!

      1. Avatar for Henry

        After running the command, this is my results:
        ps -AF | grep screen
        user 1596 1428 0 19473 5372 3 feb19 ? 00:00:10 xscreensaver -no-splash
        user 1764 1 0 107440 23568 1 feb19 ? 00:00:00 /usr/bin/gnome-screensaver --no-daemon
        user 16964 27672 0 5383 1108 4 11:33 pts/3 00:00:00 grep --color=auto screen

        ps -AF | grep
        avahi 1013 1 0 11848 3740 5 feb19 ? 00:00:09 avahi-daemon: running [.local]
        user 18066 27672 0 5383 1036 2 11:44 pts/3 00:00:00 grep --color=auto

        If I change the level-name= string on server.properties, the server starts as usual:
        [2020-02-20 09:29:58 INFO] Starting Server
        [2020-02-20 09:29:58 INFO] Version 1.14.30.2
        [2020-02-20 09:29:58 INFO] Session ID ace91c9a-0c5f-41e2-a1c2-7aaefc478a83
        [2020-02-20 09:29:58 INFO] Level Name: Bedrock
        [2020-02-20 09:29:58 INFO] Game mode: 0 Survival
        [2020-02-20 09:29:58 INFO] Difficulty: 1 EASY
        [2020-02-20 09:29:59 INFO] IPv4 supported, port: 19132
        [2020-02-20 09:29:59 INFO] IPv6 supported, port: 19133
        [2020-02-20 09:29:59 INFO] IPv4 supported, port: 45923
        [2020-02-20 09:29:59 INFO] IPv6 supported, port: 57382
        [2020-02-20 09:30:00 INFO] Server started.

  2. Avatar for DE

    I think this is more of a quirk with how the bedrock servers start up, but I have two servers setup, one on the default port, 19132, the other on port 19134. on a server reboot and during the cron scheduled reboots, the server on port 19132 regularly complains the port is in use. I need to stop all servers, start server 1 then start server 2 and all is good. I’ve also manually modified the cron job to be 5 minutes apart. Thought I’d post here in case anyone else is running into the same issue.

  3. Avatar for run_tron

    Everything seems to work for me! Has anyone tried to install python modules mpci or the custom python interface bedrock? I’ve tried installing both, but cant seems to get mcpi to work, or find the correct path/usage for bedrock. It’s been great having MCBE on Ubuntu but it would be nice to also be able to use python to interact with BE.

    1. Avatar for Steve

      did you find a solution? I’ve been working on this without success. I am wondering if the problem is that MCBE does not allow plugins?

  4. Avatar for Maka

    Hi,

    Everything works fine during process until that error :

    dpkg: error: cannot access archive 'qemu-user*.deb' no such file or directory
    QEMU-x86_64-static did not install successfully

    Could you please help me ?

    Thx

  5. Avatar for Daniel

    Hi James,
    Thank you for your amazing script, It was very simple to install, and run the server. Everything works perfectly, but I have a question. Is there any way to log user logins? I would be happy to implement this to my server, and so far what I’ve seen is that I get a Dedicated_server.txt in the root folder. When I enter the screen then the output is saved to it, but if I don’t then this file will be empty after the server restarted. Also I see a text in it:
    “Content logging enabled. Writing log to: ContentLog__Monday__2020_January_27__07_55_06”
    I really have no idea where should I find it, I tried to use google, but found no help.
    Do you have any idea what could I do to make a simple logging?

    Thank you in advance,
    Regards,
    Daniel

  6. Avatar for P L

    Hi James, thanks for creating this. I see the daily restart cron in crontab, but I’m having trouble with autostart.

    I didn’t see a terminal prompt, so checked to see if it was running:

    loomcraft@loomcraft:~/minecraftbe/loomcraft$ sudo systemctl start loomcraft.service

    Job for loomcraft.service failed because the control process exited with error code.
    See "systemctl status loomcraft.service" and "journalctl -xe" for details.

    So I followed the prompt:

    loomcraft@loomcraft:~/minecraftbe/loomcraft$ systemctl status loomcraft.service
    loomcraft.service - loomcraft minecraft server
    Loaded: loaded (/etc/systemd/system/loomcraft.service; enabled; vendor preset: enabled
    Active: failed (Result: exit-code) since Mon 2020-01-27 11:57:08 PST; 13s ago
    Process: 2802 ExecStart=/bin/bash /home/loomcraft/minecraftbe/loomcraft/start.sh (code=

    Jan 27 11:57:08 loomcraft systemd[1]: Starting loomcraft minecraft server...
    Jan 27 11:57:08 loomcraft bash[2802]: Server is already started! Press screen -r loomcra
    Jan 27 11:57:08 loomcraft systemd[1]: loomcraft.service: Control process exited, code=exi
    Jan 27 11:57:08 loomcraft systemd[1]: loomcraft.service: Failed with result 'exit-code'.
    Jan 27 11:57:08 loomcraft systemd[1]: Failed to start loomcraft minecraft server.

    So I tried to bring up the screen, but:

    loomcraft@loomcraft:~/minecraftbe/loomcraft$ screen -r loomcraft
    There is no screen to be resumed matching loomcraft.

    Then I tried to stop and restart the server, but ran into the same issue:

    loomcraft@loomcraft:~/minecraftbe/loomcraft$ ./stop.sh
    Stopping Minecraft server ...
    No screen session found.
    No screen session found.
    ^C
    loomcraft@loomcraft:~/minecraftbe/loomcraft$ ./restart.sh
    Sending restart notifications to server...
    No screen session found.
    ^C
    loomcraft@loomcraft:~/minecraftbe/loomcraft$ ./start.sh
    Server is already started! Press screen -r loomcraft to open it

    Any idea of what’s going on?

    Thanks.

Leave a Comment

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

Type here..

Exit mobile version