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
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
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!
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 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!
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.
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:
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.
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:
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.
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
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:
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:
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.
Absolutely not. The script uses a sudoers file and a whole bunch of other configuration. I’ve covered if you want to install to a different directory. It’s this simple:
curl https://raw.githubusercontent.com/TheRemote/MinecraftBedrockServer/master/SetupMinecraft.sh | sed 's+DirName=$(readlink -e ~)+DirName=/mnt/yourdirectory+g' | bash
Yes, absolutely! So for removal it is that simple. You can also remove the /etc/sudoers.d/minecraftbe file but basically a sudo rm will completely remove it other than that file.
In other words although installation has a support file that makes simply moving the folder impossible (without knowing the right places to update to take that into account) it is that simple to remove fortunately. If you left the old sudoers file in place it would do nothing as the commands in the sudoers file are extremely specific down to the original parameters so it won’t hurt anything to not remove it but for completion remove /etc/sudoers.d/minecraftbe as well.
Como puedo cambiar la carpeta de instalacion? deseo que se instale en otro disco duro donde tengo mas espacio, en el tutorial dice que la primera pregunta es para indicar la ruta de instalacion pero a mi solamente me pregunta el nombre del servidor
curl https://raw.githubusercontent.com/TheRemote/MinecraftBedrockServer/master/SetupMinecraft.sh | sed 's+DirName=$(readlink -e ~)+DirName=/mnt/yourdirectory+g' | bash
This would be for an example of /mnt/yourdirectory. This will basically change the installation directory when you run the script that way. Hopefully that helps!
when I try to start it it does this knoalex@ubuntu:~/minecraftbe/KillOrBeKilled$ ./start.sh
Backing up server (to minecraftbe/KillOrBeKilled/backups folder)
Backing up server (multiple cores) to minecraftbe/KillOrBeKilled/backups folder
worlds/
worlds/Bedrock level/
worlds/Bedrock level/db/
worlds/Bedrock level/db/CURRENT
worlds/Bedrock level/db/000011.log
worlds/Bedrock level/db/MANIFEST-000010
worlds/Kill or be Killed/
worlds/Kill or be Killed/db/
worlds/Kill or be Killed/db/000003.log
worlds/Kill or be Killed/db/CURRENT
worlds/Kill or be Killed/db/MANIFEST-000002
Checking for the latest version of Minecraft Bedrock server ...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 313k 0 313k 0 0 653k 0 --:--:-- --:--:-- --:--:-- 651k
Latest version online is bedrock-server-1.19.41.01.zip
Current install is: bedrock-server-1.19.41.01.zip
Latest version bedrock-server-1.19.41.01.zip is already installed
Starting Minecraft server. To view window type screen -r KillOrBeKilled
To minimize the window and let the server run in the background, press Ctrl+A then Ctrl+D
knoalex@ubuntu:~/minecraftbe/KillOrBeKilled$ screen -r KillOrBeKilled
There is no screen to be resumed matching KillOrBeKilled.
It says the port you are trying to run it on is already occupied / in use. I’d try restarting the machine (in case there’s something running in the background somewhere) or changing the ports as it looks like it’s having a conflict with something!
A lot of the time a restart will clear up whatever background process is stuck using the port. Maybe there’s a zombie process of the server somewhere in the background. I’d try a restart first though as if it has been working then nothing else should be sharing the port theoretically!
No problem at all! If you do end up changing the port the easiest way is just to run SetupMinecraft.sh again. This will give you the original install questions again and if you give the same answers as last time (other than the ports) it will just update your configuration for you with those.
i just did a fresh install and i am getting the version is outdated. I checked the version_installed.txt and it shows bedrock-server-1.19.40.02.zip
not sure what is going on here
Welcome! So to be clear the version is whatever is on Microsoft’s web site. If you click the “I Agree” checkbox and hover over the download button we can see that the version they are releasing right now is:
Every time you restart the server it checks that download page. If it’s different it downloads Microsoft’s latest official version. It looks right to me. If it doesn’t match the Bedrock client then people probably either have the beta version installed (remove it if you do, it’s just a beta client, they rarely ship the beta dedicated server and if they happen to have one up right now this isn’t set up to download it) or Microsoft has them out of sync right now (happens but usually not for long).
Hello James,
i have two server both of them tell me that they are running the latest version of minecraft. but if i try to join both one of them told me the version is outdated.
the newer one is on 1.19.40 the older one 1.19.31 but in the console the server says it it also updated ….any idea?
haaa i found a solution. i modifyed the version.txt and deleted the last dl version in downlooads stoped the server and rerun it… he installed it again and it works
I’m getting two bugs (MCPE-39439 and MCPE-157192) with the last two versions, causing black areas/shadows on terrain and crashes when using portals. I am hoping it will be patched in the next update. Anyone else seeing this?
That almost sounds like a regression (a bug that has been fixed in the past but reappears in newer versions). I’d imagine that this will in fact disappear in the next update or two!
The Ubuntu guest with Hyper-V can be fixed without running a Generation 1 VM.
This has been tested with an updated Ubuntu 20.04 Server under Hyper-V 2019. Experience in editing yaml files is highly recommended. If not comfortable, stay with gen 1 VM.
The following command will fix the issue until reboot, after reboot it reverts. Your eth0 name might be different, verify before copying commands. sudo ethtool -K eth0 tx off
You can make the fix permanent by editing your netplan configuration file. On my system this is located at: /etc/netplan/00-installer-config.yaml
Your netplan configuration file name might be different, verify before copying these commands. Also be careful when editing this file. It is a yaml file and spacing is important.
Command to edit: sudo nano /etc/netplan/00-installer-config.yaml
Add the following line under eth0: (your ethernet name might be different). This MUST line up with the addresses entry below. Spacing is important. transmit-checksum-offload: false
Here is an example of what mine looks like, do NOT copy this into your netplan file. This is just an example: network:
ethernets:
eth0:
transmit-checksum-offload: false
addresses:
- 10.88.0.30/24
gateway4: 10.88.0.1
nameservers:
addresses:
- 10.88.0.10
version: 2
Reboot and you should be good. AGAIN correct spacing is important in yaml files. If you get the spacing wrong, after reboot you will lose connectivity. Do this fix under your own discretion!
Thanks for sharing this! I just added this to the official documentation a couple of days ago (but only on GitHub, the articles need the updated sections added still which is on my to-do list). bpsimons shared this with me for the Docker containerized version (is impacted the exact same as this standalone version).
I definitely like that you’ve shared the Ubuntu netplan version as that is different than what I added to the documentation (which is using straight /etc/network/interfaces). Typically Ubuntu Server won’t have netplan but Ubuntu Desktop will (at least for 22.04). Given that Ubuntu is the main recommended OS by Microsoft to run the Bedrock server on Linux I think having the netplan steps is valuable.
Given that most people are using Ubuntu I think this is valuable. I’ll add a link to your comment as one of the references in the new documentation related to Hyper-V. Thanks!
Unable to edit my original comment. My netplan example has the spacing wrong. The formatting went away after submitting the comment.
Just pay attention to how your netplan config file looks and don’t mess it up. The transmit-checksum-offload entry should start at the same point as addresses does, 2 spaces forward from eth0. If you have any concerns there is an example located at: /usr/share/doc/netplan/examples/static.yaml
Or just google netplan yaml spacing. Good luck! Don’t break anything!
Yes, the netplan files are an absolute nightmare. I honestly hate netplan because it’s so hard for end-users to deal with but it is the “Ubuntu way”. I’d rate netplan as the biggest downside of Ubuntu but fortunately the server version doesn’t use it (at least by default). I’m using Ubuntu 22.04.1 as my main desktop OS though so I still have to deal with it from time to time on the desktop version.
I definitely have a suggestion for anyone trying to do this. Paste your config file into a YAML validator like here. This will completely check and validate your file. If it passes it’s ready to be put into netplan! If it doesn’t it will tell / show you where you made a spacing or other mistake.
For the longest time I was just using the ethtool command to sort it. But this would always revert after reboot, so I decided to finally look into how to sort this in netplan.
Interesting on the netplan for server comment. I run a few different Ubuntu 20.04 server VM’s on my Hyper-V server. I never did anything different than assigning a static IP during install, and it always created and used /etc/netplan/00-installer-config.yaml for the networking.
That said I have been a Windows admin for a long time now. Don’t have the same knowledge of Ubuntu as I do Windows. Fun to learn and fix new things though.
Thanks for the YAML validator link and thanks for all your work on the Bedrock / Ubuntu server!
Oh wow, you had found the ethtool trick before I had even heard about it! This was honestly the strangest issue to diagnose when we were originally trying to do it. We had to go all the way to Wireshark traces to even be able to detect there was a problem (as the Minecraft server would give no indication anything was really wrong).
I could be wrong about the default Ubuntu server for x86_64 as most of my work has been on ARM SBCs for all of my reviews I’ve been doing lately. Those flavors have all been coming without netplan but since they are images for specific SBCs they may be customizing it like that. If you’ve done some server images lately that were Ubuntu defaults and were not configured this way then these must all be vendor customizations. None of these even come with cloud-init installed anymore but the base Ubuntu server download may very well still come with it. It wouldn’t surprise me if most vendors are switching this to avoid having to support netplan and instead shipping it with the more familiar /etc/network/interfaces system.
It’s possible to switch between the two but I don’t like to especially on Desktop as things get janky really quick. They definitely say it’s the “Ubuntu way” for a reason as that is how the OS is designed and things get janky/weird when you try to deviate from it (but if netplan is an absolute dealbreaker for someone it can be done).
Thanks for sharing all your help! I’ll definitely be updating the documentation over the next couple of days here and will link to here as well as mention netplan since I think a lot of people will run into that. Take care!
The script did not prompt for a location to install the server, can i just sudo mv?
Hey Jonathan,
Absolutely not. The script uses a sudoers file and a whole bunch of other configuration. I’ve covered if you want to install to a different directory. It’s this simple:
curl https://raw.githubusercontent.com/TheRemote/MinecraftBedrockServer/master/SetupMinecraft.sh | sed 's+DirName=$(readlink -e ~)+DirName=/mnt/yourdirectory+g' | bashHopefully that helps!
Thanks, to remove it… can i simple sudo rm?
Hey Jonathan,
Yes, absolutely! So for removal it is that simple. You can also remove the /etc/sudoers.d/minecraftbe file but basically a sudo rm will completely remove it other than that file.
In other words although installation has a support file that makes simply moving the folder impossible (without knowing the right places to update to take that into account) it is that simple to remove fortunately. If you left the old sudoers file in place it would do nothing as the commands in the sudoers file are extremely specific down to the original parameters so it won’t hurt anything to not remove it but for completion remove /etc/sudoers.d/minecraftbe as well.
Hopefully that helps!
Como puedo cambiar la carpeta de instalacion? deseo que se instale en otro disco duro donde tengo mas espacio, en el tutorial dice que la primera pregunta es para indicar la ruta de instalacion pero a mi solamente me pregunta el nombre del servidor
Hey Javier,
Go ahead and try:
curl https://raw.githubusercontent.com/TheRemote/MinecraftBedrockServer/master/SetupMinecraft.sh | sed 's+DirName=$(readlink -e ~)+DirName=/mnt/yourdirectory+g' | bashThis would be for an example of /mnt/yourdirectory. This will basically change the installation directory when you run the script that way. Hopefully that helps!
Gracias, funciono
No problem, enjoy and have fun!
when I try to start it it does this
knoalex@ubuntu:~/minecraftbe/KillOrBeKilled$ ./start.shBacking up server (to minecraftbe/KillOrBeKilled/backups folder)
Backing up server (multiple cores) to minecraftbe/KillOrBeKilled/backups folder
worlds/
worlds/Bedrock level/
worlds/Bedrock level/db/
worlds/Bedrock level/db/CURRENT
worlds/Bedrock level/db/000011.log
worlds/Bedrock level/db/MANIFEST-000010
worlds/Kill or be Killed/
worlds/Kill or be Killed/db/
worlds/Kill or be Killed/db/000003.log
worlds/Kill or be Killed/db/CURRENT
worlds/Kill or be Killed/db/MANIFEST-000002
Checking for the latest version of Minecraft Bedrock server ...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 313k 0 313k 0 0 653k 0 --:--:-- --:--:-- --:--:-- 651k
Latest version online is bedrock-server-1.19.41.01.zip
Current install is: bedrock-server-1.19.41.01.zip
Latest version bedrock-server-1.19.41.01.zip is already installed
Starting Minecraft server. To view window type screen -r KillOrBeKilled
To minimize the window and let the server run in the background, press Ctrl+A then Ctrl+D
knoalex@ubuntu:~/minecraftbe/KillOrBeKilled$ screen -r KillOrBeKilled
There is no screen to be resumed matching KillOrBeKilled.
Hey knoalex,
We need to see the server log files. There’s nothing going wrong in the script here. It looks like your server is probably crashing.
If you go to the “logs” folder it should have some log files that will tell us what is going on here and that should help!
Ok I will check it out
here are the latest logs
[2022-11-09 21:24:27] NO LOG FILE! - setting up server logging...[2022-11-09 21:24:27] [2022-11-09 21:24:27:540 INFO] Starting Server
[2022-11-09 21:24:27] [2022-11-09 21:24:27:540 INFO] Version 1.19.41.01
[2022-11-09 21:24:27] [2022-11-09 21:24:27:540 INFO] Session ID 702e839f-c8df-47a6-98a0-84806bc743fb
[2022-11-09 21:24:27] [2022-11-09 21:24:27:540 INFO] Level Name: Kill or be Killed
[2022-11-09 21:24:27] [2022-11-09 21:24:27:575 INFO] Game mode: 0 Survival
[2022-11-09 21:24:27] [2022-11-09 21:24:27:575 INFO] Difficulty: 3 HARD
[2022-11-09 21:24:28] [2022-11-09 21:24:28:671 INFO] opening worlds/Kill or be Killed/db
terminate called without an active exception
[2022-11-09 21:24:29] [2022-11-09 21:24:29:860 ERROR] Network port occupied, can't start server.
[2022-11-09 21:24:29] [2022-11-09 21:24:29:860 INFO] Server stop requested.
[2022-11-09 21:24:29] [2022-11-09 21:24:29:925 INFO] Package: com.mojang.minecraft.dedicatedserver
[2022-11-09 21:24:29] Version: 1.19.41.01
[2022-11-09 21:24:29] OS: Linux
[2022-11-09 21:24:29] Server start: 2022-11-09 21:24:27 UTC
[2022-11-09 21:24:29] Dmp timestamp: 2022-11-09 21:24:29 UTC
[2022-11-09 21:24:29] Upload Date: 2022-11-09 21:24:29 UTC
[2022-11-09 21:24:29] Session ID: 702e839f-c8df-47a6-98a0-84806bc743fb
[2022-11-09 21:24:29] Commit hash: 3b5a03f6df73300ed21a4a5ac0deaef133faecb9
[2022-11-09 21:24:29] Build id: 12342456
[2022-11-09 21:24:29] CrashReporter Key: 609111ac-c9a0-3307-9dc8-c2dea267a689
[2022-11-09 21:24:29]
[2022-11-09 21:24:29] Crash
[2022-11-09 21:24:29] [2022-11-09 21:24:29:925 INFO] at gsignal (UnknownFile:?)
[2022-11-09 21:24:29] at abort (UnknownFile:?)
[2022-11-09 21:24:29] at __libc_start_main (UnknownFile:?)
[2022-11-09 21:24:29] f98e7ba0-88e1-421c-85ec-ff0e7c02be23
Hey knoalex,
It says the port you are trying to run it on is already occupied / in use. I’d try restarting the machine (in case there’s something running in the background somewhere) or changing the ports as it looks like it’s having a conflict with something!
A lot of the time a restart will clear up whatever background process is stuck using the port. Maybe there’s a zombie process of the server somewhere in the background. I’d try a restart first though as if it has been working then nothing else should be sharing the port theoretically!
Ok thank you
No problem at all! If you do end up changing the port the easiest way is just to run SetupMinecraft.sh again. This will give you the original install questions again and if you give the same answers as last time (other than the ports) it will just update your configuration for you with those.
Let me know if I can help further!
It worked thanks alot!!!
No problem, enjoy and have fun!!!
i just did a fresh install and i am getting the version is outdated. I checked the version_installed.txt and it shows bedrock-server-1.19.40.02.zip
not sure what is going on here
Hey hlprime,
Welcome! So to be clear the version is whatever is on Microsoft’s web site. If you click the “I Agree” checkbox and hover over the download button we can see that the version they are releasing right now is:
https://minecraft.azureedge.net/bin-linux/bedrock-server-1.19.40.02.zipEvery time you restart the server it checks that download page. If it’s different it downloads Microsoft’s latest official version. It looks right to me. If it doesn’t match the Bedrock client then people probably either have the beta version installed (remove it if you do, it’s just a beta client, they rarely ship the beta dedicated server and if they happen to have one up right now this isn’t set up to download it) or Microsoft has them out of sync right now (happens but usually not for long).
Hopefully that helps!
Hello James,
i have two server both of them tell me that they are running the latest version of minecraft. but if i try to join both one of them told me the version is outdated.
the newer one is on 1.19.40 the older one 1.19.31 but in the console the server says it it also updated ….any idea?
thanks eike
haaa i found a solution. i modifyed the version.txt and deleted the last dl version in downlooads stoped the server and rerun it… he installed it again and it works
Hey Eike,
Excellent, I’m glad you got it going!
I’m getting two bugs (MCPE-39439 and MCPE-157192) with the last two versions, causing black areas/shadows on terrain and crashes when using portals. I am hoping it will be patched in the next update. Anyone else seeing this?
Hey Will,
That almost sounds like a regression (a bug that has been fixed in the past but reappears in newer versions). I’d imagine that this will in fact disappear in the next update or two!
The Ubuntu guest with Hyper-V can be fixed without running a Generation 1 VM.
This has been tested with an updated Ubuntu 20.04 Server under Hyper-V 2019. Experience in editing yaml files is highly recommended. If not comfortable, stay with gen 1 VM.
The following command will fix the issue until reboot, after reboot it reverts. Your eth0 name might be different, verify before copying commands.
sudo ethtool -K eth0 tx offYou can make the fix permanent by editing your netplan configuration file. On my system this is located at: /etc/netplan/00-installer-config.yaml
Your netplan configuration file name might be different, verify before copying these commands. Also be careful when editing this file. It is a yaml file and spacing is important.
Command to edit:
sudo nano /etc/netplan/00-installer-config.yamlAdd the following line under eth0: (your ethernet name might be different). This MUST line up with the addresses entry below. Spacing is important.
transmit-checksum-offload: falseHere is an example of what mine looks like, do NOT copy this into your netplan file. This is just an example:
network:ethernets:
eth0:
transmit-checksum-offload: false
addresses:
- 10.88.0.30/24
gateway4: 10.88.0.1
nameservers:
addresses:
- 10.88.0.10
version: 2
Reboot and you should be good. AGAIN correct spacing is important in yaml files. If you get the spacing wrong, after reboot you will lose connectivity. Do this fix under your own discretion!
Hey Chad,
Thanks for sharing this! I just added this to the official documentation a couple of days ago (but only on GitHub, the articles need the updated sections added still which is on my to-do list). bpsimons shared this with me for the Docker containerized version (is impacted the exact same as this standalone version).
I definitely like that you’ve shared the Ubuntu netplan version as that is different than what I added to the documentation (which is using straight /etc/network/interfaces). Typically Ubuntu Server won’t have netplan but Ubuntu Desktop will (at least for 22.04). Given that Ubuntu is the main recommended OS by Microsoft to run the Bedrock server on Linux I think having the netplan steps is valuable.
Given that most people are using Ubuntu I think this is valuable. I’ll add a link to your comment as one of the references in the new documentation related to Hyper-V. Thanks!
Unable to edit my original comment. My netplan example has the spacing wrong. The formatting went away after submitting the comment.
Just pay attention to how your netplan config file looks and don’t mess it up. The transmit-checksum-offload entry should start at the same point as addresses does, 2 spaces forward from eth0. If you have any concerns there is an example located at: /usr/share/doc/netplan/examples/static.yaml
Or just google netplan yaml spacing. Good luck! Don’t break anything!
Hey Chad,
Yes, the netplan files are an absolute nightmare. I honestly hate netplan because it’s so hard for end-users to deal with but it is the “Ubuntu way”. I’d rate netplan as the biggest downside of Ubuntu but fortunately the server version doesn’t use it (at least by default). I’m using Ubuntu 22.04.1 as my main desktop OS though so I still have to deal with it from time to time on the desktop version.
I definitely have a suggestion for anyone trying to do this. Paste your config file into a YAML validator like here. This will completely check and validate your file. If it passes it’s ready to be put into netplan! If it doesn’t it will tell / show you where you made a spacing or other mistake.
Happy to help!
For the longest time I was just using the ethtool command to sort it. But this would always revert after reboot, so I decided to finally look into how to sort this in netplan.
Interesting on the netplan for server comment. I run a few different Ubuntu 20.04 server VM’s on my Hyper-V server. I never did anything different than assigning a static IP during install, and it always created and used /etc/netplan/00-installer-config.yaml for the networking.
That said I have been a Windows admin for a long time now. Don’t have the same knowledge of Ubuntu as I do Windows. Fun to learn and fix new things though.
Thanks for the YAML validator link and thanks for all your work on the Bedrock / Ubuntu server!
Hey Chad,
Oh wow, you had found the ethtool trick before I had even heard about it! This was honestly the strangest issue to diagnose when we were originally trying to do it. We had to go all the way to Wireshark traces to even be able to detect there was a problem (as the Minecraft server would give no indication anything was really wrong).
I could be wrong about the default Ubuntu server for x86_64 as most of my work has been on ARM SBCs for all of my reviews I’ve been doing lately. Those flavors have all been coming without netplan but since they are images for specific SBCs they may be customizing it like that. If you’ve done some server images lately that were Ubuntu defaults and were not configured this way then these must all be vendor customizations. None of these even come with cloud-init installed anymore but the base Ubuntu server download may very well still come with it. It wouldn’t surprise me if most vendors are switching this to avoid having to support netplan and instead shipping it with the more familiar /etc/network/interfaces system.
It’s possible to switch between the two but I don’t like to especially on Desktop as things get janky really quick. They definitely say it’s the “Ubuntu way” for a reason as that is how the OS is designed and things get janky/weird when you try to deviate from it (but if netplan is an absolute dealbreaker for someone it can be done).
Thanks for sharing all your help! I’ll definitely be updating the documentation over the next couple of days here and will link to here as well as mention netplan since I think a lot of people will run into that. Take care!