Minecraft Bedrock
This guide walks you through the process of deploying, managing, and connecting to a Minecraft Bedrock Edition Game Server using FluxCloud. Bedrock Edition is the version of Minecraft that runs on phones, tablets, consoles, and Windows 10/11 β it is not cross-compatible with Minecraft Java Edition servers.
The FluxCloud Minecraft Bedrock template is built on the popular itzg/minecraft-bedrock-server image, which wraps the official Mojang Bedrock dedicated server and keeps it up to date on every restart.
For more information on Minecraft visit: https://www.minecraft.net. For the server image documentation, see: https://github.com/itzg/docker-minecraft-bedrock-server.
π‘ Looking for Java Edition? If your players are on desktop (Java), you want the Minecraft Java guide instead.
π Dedicated Minecraft hosting portal: Minecraft on Flux β including Bedrock Edition β now has its own purpose-built site at minecraft.runonflux.com. It gives you a streamlined checkout (pay by card or subscription via Stripe, or with FLUX crypto) and a dedicated management dashboard β live CPU/RAM/disk stats, an in-browser terminal and file manager, one-click backups, billing and renewal controls, and a global server-location map. Clicking the Minecraft Bedrock tile in the FluxCloud Marketplace now redirects you there automatically. The Marketplace walkthrough below still applies β the configuration options are the same, and your server runs as a standard Flux app you can also manage from cloud.runonflux.com.
How To Install a Minecraft Bedrock Serverβ
Stepsβ
- Access FluxCloud
- Visit minecraft.runonflux.com β the dedicated Minecraft Bedrock hosting portal β and sign in or create an account. (Going through cloud.runonflux.com works too: clicking the Minecraft Bedrock tile in the Marketplace redirects you there automatically.)
- Find the Minecraft Bedrock Server
- Navigate to the Marketplace β Games tab, then locate the Minecraft Bedrock tile and click View Details.
- Select Server Configuration
- Choose your preferred configuration, and click Install Now to continue.
- Choose Subscription
- Select your desired subscription duration.
- Agree to the Terms of Use and Privacy Policy, and click the blue Continue arrow at the bottom.
- Deployment Location
- Configure whether you want your Minecraft Bedrock server to deploy in specific geographic regions:
- Global (Recommended): No geographic restrictions for best availability.
- Custom: Restrict by continent or country.
- Click the blue Continue arrow to proceed.
- Email Notifications
- Optionally enter your email address to receive notifications about your game server, including:
- When your application finishes launching.
- When the primary server changes.
- When your app expiration date is approaching.
- Launching the Application
- Your application must be signed and registered on the Flux network.
- Click Sign and Register.
- Sign the message using the pop-up.
- If you logged in via Google or Email, this step is completed automatically.
- Complete Payment
- Choose your payment method:
- Fiat: Stripe or PayPal
- Crypto: FLUX coin (5% discount)
- Payment is monitored automatically. Once confirmed, your application will be deployed, and a blue Manage button will appearβdirecting you to your applicationβs management panel.
β οΈ Important: FLUX Payments
FLUX payments are only accepted via the FLUX Mainnet, not through any of our EVM tokens.
We ALSO strongly recommend not sending FLUX payments from exchanges, as:
- Transactions or withdrawals may not complete within the required 30-minute window.
- Many exchanges do not support adding a MEMO, which is required for proper payment processing.
Finding the IP of Your Game Serverβ
Flux runs on a decentralized network, meaning your application is deployed across three instances.
For game servers, a Primary/Standby setup is used β your game runs on the primary instance, while others are on standby for redundancy.
To find your serverβs primary IP address:
- Visit cloud.runonflux.com and log in.
- Go to Applications β Management.
- Click the Settings icon on your Minecraft Bedrock Server.
- Open the Instances tab.
- The Primary IP address is shown here.
- You can also view geolocation details for all instances.
To connect to your server from a Bedrock client (mobile, console, or Windows 10/11):
- Launch Minecraft and tap/click Play β Servers.
- Scroll to the bottom of the server list and choose Add Server.
- Fill in the fields:
- Server Name: any label you like (e.g.
Flux Bedrock). - Server Address: your Primary IP address.
- Port:
19132.
- Server Name: any label you like (e.g.
- Save and then tap/click the server to connect.
π‘ Tip: Bedrock uses UDP port
19132. If your client has a separate Port field, enter19132there β do not append it to the address field.
Connecting via Domain Instead of IPβ
Every FluxCloud Marketplace game server is also reachable through its application domain. Flux's load balancer forwards traffic over DNS and is already configured with the correct game port, so you keep a stable address even when the primary instance changes due to failover.
-
Find your app domain under Applications β Management β Information.
-
In the Bedrock Add Server dialog, enter the domain in the Server Address field. Bedrock's Port field already defaults to
19132, and the domain's DNS routing targets that same port:your-app-domain.app.runonflux.io
Using the domain means your saved server entry continues to work automatically after any primary switch.
Adjusting Server Settingsβ
Bedrock server settings (level name, game mode, difficulty, max players, whitelist) live in a single config file on the persistent volume.
-
Open Applications β Management on cloud.runonflux.com, select your Minecraft Bedrock app, click the Settings icon and open the Secure Shell tab.
-
Scroll to the Volume Browser and locate:
/data/server.properties -
Edit the values you want to change (for example
server-name,gamemode,difficulty,max-players,allow-cheats), then save. -
Open the Control tab, select Local, and click Restart Application so the new settings take effect.
β οΈ Important: Invalid configuration values can prevent the server from starting. Back up the file before editing and revert if the server fails to boot.
Managing World Filesβ
Bedrock worlds live on the persistent volume at:
/data/worlds/
Each world is a directory.
Download a backupβ
Use the Volume Browser to download world directories before risky changes or major game updates. Saved directories can be re-uploaded later using the procedure below.
Roll back to a previous backupβ
Replace the current world directory in /data/worlds/ with your backup, then restart the application from Control β Local β Restart Application.
Upload an existing world (from a single-player game or another server)β
Simply dropping a new world directory onto a running server is unreliable: the server holds its current world files open and writes autosaves on a timer, so a copy that overlaps with an autosave can leave the directory in a half-written state. The procedure below pauses the container while you swap files in, then points the server at the new world on the next start.
-
Open Applications β Management, select your Minecraft Bedrock app, and switch to Control β Local β Pause Container. Pausing stops the server from writing to the current world while you upload.
-
Open the Volume Browser and upload your world directory into:
/data/worlds/ -
In the same Volume Browser, edit
server.propertiesand setlevel-nameto exactly match your uploaded directory's name (case-sensitive, no trailing slash). -
Return to Control β Local β Restart Container. The server starts with your uploaded world.
π‘ Tip:
level-namemust match the directory name exactly β including case. If your folder isMyOldWorld, setlevel-name=MyOldWorld, notmyoldworld.
Frequently Asked Questionsβ
What ports does Minecraft Bedrock use?β
The Bedrock dedicated server listens on UDP port 19132 (IPv4). FluxCloud exposes this port automatically. In the in-game Add Server dialog, enter your serverβs IP or app domain in Server Address and 19132 in Port.
Can Java and Bedrock players join the same server?β
No β Java and Bedrock use different protocols and are not natively cross-compatible. If you need cross-play, deploy the Java server and install a community bridge plugin (e.g. Geyser + Floodgate) on it. The FluxCloud Bedrock template runs the vanilla Bedrock server and only accepts Bedrock clients.
What happens if the primary server goes down?β
If your current primary server becomes unavailable or experiences downtime, one of the standby instances automatically takes over as the new primary after a short delay. Your worlds and configuration are preserved on the persistent volume, so the game resumes where you left off once the switch is complete. You can check which instance is currently the primary from your applicationβs management panel under the Instances tab.
π‘ Tip: If you connect via the app domain (
your-app-domain.app.runonflux.io) with port19132instead of the raw IP, your client will keep reaching the correct primary automatically after a failover.
Can I use my own world file?β
Yes β for example a backup from a single-player save or another server. Because a running server keeps its world files open and writes autosaves on a timer, follow the Upload an existing world procedure under Managing World Files: pause the container, upload the world directory, set level-name in server.properties to match, then restart.
How can I update my game server to the latest version?β
The itzg/minecraft-bedrock-server image pulls the latest official Bedrock dedicated server build on every startup. To update immediately, open Applications β Management, select your Minecraft Bedrock server, go to the Control tab, choose Local, and click Restart Application.
Can I change my server's hardware specifications after deployment?β
Yes. At any time β if you feel the hardware specifications no longer reflect your needs β you can adjust them from Applications β Management β Update App Specifications on the Components tab. Your world saves, settings, and data are preserved across the change, and you are billed according to the new specifications.