Comprehensive Guide To Updating Your Minecraft Bedrock Dedicated Server

Comprehensive Guide To Updating Your Minecraft Bedrock Dedicated Server

How To Make A Server In Minecraft Bedrock For Free 2021 at Nate Piquet blog

Updating a Minecraft Bedrock Dedicated Server involves a systematic replacement of core binary files while preserving configuration and world data to ensure seamless transition between version protocols. Administrators must synchronize the server's version with the latest client release to prevent protocol mismatch errors, typically requiring a full backup of the worlds directory followed by an overwrite of the executable and library files.


Technical Preparation and Server Maintenance Planning

Before initiating a version migration, a server administrator must understand that Minecraft Bedrock Edition does not feature an automatic update mechanism for dedicated server software. Unlike the Windows Store or mobile app versions which update via a package manager, the Bedrock Dedicated Server (BDS) is a standalone binary distribution. Maintaining parity between the server and the players' clients is mandatory because Bedrock Edition does not support cross-version play; if a player’s console or phone updates to version 1.21.20, they cannot connect to a server running 1.21.10.



Mandatory Pre-Update Checklist



  • Current Server Software Version: Identify your existing build by looking at the terminal output upon startup.
  • System Administrative Access: You must have full read/write permissions for the directory where the server files are hosted, whether on Windows or Linux (Ubuntu/Debian).
  • Backup Storage: Sufficient disk space to clone the entire worlds folder, which contains the LevelDB database and player data.
  • Dependency Verification: For Windows hosts, ensure the latest Visual C++ Redistributable packages are installed. For Linux hosts, ensure libcurl4 and openssl are updated.
  • Standard Maintenance Window: Expect a downtime of 10 to 15 minutes for a standard update, or longer if a world conversion is triggered by a major content update.

Systematic Execution for Bedrock Server Version Migration

Updating the server software requires a surgical approach to file management. The goal is to replace the engine while leaving the soul of the server—the settings and the world—untouched. Following these steps ensures that you do not accidentally reset your world or lose your player permissions.



Step 1: Execute a Graceful Shutdown

Never update a server while it is running. Files are locked by the operating system during execution, and stopping the process abruptly can lead to corruption in the LevelDB files within the worlds folder.



  1. Access the server console or terminal.
  2. Issue the stop command and press enter.
  3. Wait for the terminal to confirm that the server has fully exited and saved all chunks.
  4. Verify in your Task Manager or process list (using the top or htop command on Linux) that the bedrock_server process is no longer active.


Step 2: Comprehensive Data Redundancy (Backup)

The most common failure point in a server update is the accidental overwriting of the worlds folder or the server.properties file.



  1. Navigate to your main server root directory.
  2. Locate the folder named worlds.
  3. Copy this folder to a secure location outside of the Minecraft directory tree.
  4. Locate and copy the server.properties file, the allowlist.json (or whitelist.json in older versions), and the permissions.json file.
  5. Create a compressed archive of these files, labeling it with the date and the version number you are moving away from.


Step 3: Acquiring the Latest Binary Distribution

The latest software must be sourced directly from the official Minecraft website to ensure security and integrity.



  1. Navigate to the official Minecraft Bedrock Dedicated Server download page.
  2. Agree to the End User License Agreement (EULA) and Privacy Policy.
  3. Download the ZIP file for Windows or the ZIP/TAR for Linux.
  4. Check the version number in the filename to ensure it matches the current client version available on the retail stores.


Step 4: Selective File Extraction and Overwriting

This is the most technical phase of the process. You must not simply delete the old folder and paste the new one, as this would delete your world data.



  1. Open the newly downloaded archive.
  2. Extract all files into a temporary folder.
  3. Select the core executable (bedrock_server.exe on Windows or bedrock_server on Linux) and all associated .dll or .so library files.
  4. Copy these selected files and paste them into your active server directory, choosing Replace when prompted by the operating system.
  5. Warning: Do not overwrite your existing server.properties, allowlist.json, or permissions.json unless the new version introduces a mandatory new setting that you wish to configure manually later. Usually, the server will function correctly with the old configuration files.


Step 5: Permission Management and Execution (Linux Specific)

On Linux systems, the extraction process often strips the execution bit from the binary file.



  1. Open your terminal in the server directory.
  2. Run the command: chmod +x bedrock_server to restore executable permissions.
  3. Ensure the user running the server has ownership of the newly replaced files by using the chown command if necessary.
  4. If you are using a startup script, check if the LD_LIBRARY_PATH environment variable is still correctly pointing to the current directory so the server can find its library files.


Step 6: Verification and Post-Update Audit

Once the files are in place, the server must be validated.



  1. Launch the server using your standard startup script or by executing the binary.
  2. Monitor the console output for any lines indicating Version Mismatch or Missing Dependency.
  3. Observe the log for a message stating Server started on port 19132.
  4. Open the Minecraft client on your own device and attempt to connect to the server.
  5. If successful, check that player inventories, world structures, and permissions remain intact.

How to Download Minecraft Bedrock 1.21.120.23 Beta and Preview

How to Download Minecraft Bedrock 1.21.120.23 Beta and Preview

Server File Architecture and Functionality Specifications

The following table outlines the critical files within the Bedrock Dedicated Server directory and how they should be handled during an update cycle. Understanding the role of each file prevents the accidental deletion of vital server metadata.



File or Folder Name Technical Function Update Action
bedrock_server.exe The primary server binary/executable engine. Always Replace with new version.
bedrock_server.pdb Debug symbols for the Windows executable. Replace with new version.
worlds/ Directory containing the LevelDB world database. NEVER OVERWRITE; always backup.
server.properties Main configuration file (port, seeds, difficulty). Keep existing; check for new flags.
permissions.json Defines player roles (operator, member, visitor). Keep existing.
allowlist.json The access control list for private servers. Keep existing.
behavior_packs/ Contains server-side add-ons and logic changes. Keep; update packs individually if needed.
resource_packs/ Contains textures and client-side visual data. Keep; update packs individually if needed.
*.dll (Windows) Dynamic Link Libraries required for execution. Always Replace with new versions.
*.so (Linux) Shared Object files (Linux equivalent of DLLs). Always Replace with new versions.

Common Update Failures and Corrective Remedies

Even seasoned administrators encounter issues when migrating versions. Most problems stem from OS-level restrictions or incomplete file transfers.



  • Failure Scenario: The server crashes immediately with a "Missing DLL" or "Library Not Found" error.



    • Root Cause: This is typically caused by a failure to install the required Visual C++ Redistributable on Windows or a missing libcurl dependency on Linux.
    • Actionable Fix: On Windows, download the latest X64 Redistributable from Microsoft's official site. On Linux, run the package manager command to install libcurl4 and ensure the LD_LIBRARY_PATH is set to the current directory when running the server.
  • Failure Scenario: Players receive a "Could not connect: Outdated Server" message.



    • Root Cause: The server binary was not successfully replaced, or the server was restarted using the old executable in a different folder.
    • Actionable Fix: Verify the version number in the server console output. If it shows the old version, re-run the extraction process and ensure you are overwriting the files in the correct directory that your startup script points to.
  • Failure Scenario: The world is reset to a new seed or player progress is gone.



    • Root Cause: The server.properties file was overwritten by the default version, or the level-name variable was changed, causing the server to look for a different world folder.
    • Actionable Fix: Stop the server immediately. Restore your backup of server.properties and the worlds folder. Ensure the level-name in server.properties matches the folder name of your original world.
  • Failure Scenario: Linux server fails to start with "Permission Denied".



    • Root Cause: The newly downloaded bedrock_server file does not have the executable bit set.
    • Actionable Fix: Run the command chmod plus x followed by the filename in the terminal to grant the necessary execution rights to the system user.

Frequently Asked Questions



Does updating my Minecraft Bedrock server delete my world?

No, updating the server software does not delete your world as long as you do not delete or overwrite the worlds folder. The world data is stored separately from the executable binaries, but a backup is always recommended as major updates may modify the world's database structure.



Can I downgrade my Bedrock server if an update breaks my add-ons?

Downgrading is extremely difficult because once a world is opened in a newer version of Minecraft, the LevelDB database is often upgraded to a newer format. If you attempt to run that world on an older version of the server, it will likely fail to load or become corrupted, which is why keeping a pre-update backup is vital.



Why is my Linux server not finding the library files after an update?

Linux requires the system to know where to look for shared object files. If you are running the server manually, you must prepend the execution command with the library path variable, ensuring the system looks in the local directory for the necessary files bundled with the server download.



How do I update a Bedrock server running in a Docker container?

To update a Docker-based server, you generally pull the latest image from your provider and restart the container. Since the world data and configuration files are usually mounted as external volumes, the container update replaces the binaries while the persistent data remains untouched in the host's file system.



What should I do if the official download link is not updated yet?

Occasionally, the client update rolls out to consoles and mobile devices before the dedicated server binaries are posted. In this case, there is no manual fix; you must wait for Mojang to publish the corresponding BDS version to ensure protocol compatibility between the server and the updated clients.

Professional Server Management Solutions

Maintaining a manual server requires diligence and technical precision to ensure a high-quality experience for your player base. For those seeking to scale their community without the overhead of manual binary management, exploring automated hosting solutions can provide a more streamlined administrative workflow.


Minecraft [Bedrock Edition] - UI หน้า Server ใหม่ของ OreUI ...

Minecraft [Bedrock Edition] - UI หน้า Server ใหม่ของ OreUI ...

Read also: Remembering Christopher William Burn: Obituary and Legacy