VPS Tutorials
Minecraft Bedrock on VPS: Docker, UDP, Access and Backups (2026)
Deploy BDS with Docker, configure UDP and allowlists, check console connection limits, register packs correctly and back up worlds before upgrades.

A Minecraft server must match the players’ edition, not simply their device. Java and Bedrock do not connect directly to each other by default. Windows can run Bedrock too, while console clients have different external-server restrictions from mobile and desktop clients.
The Java/Paper guide covers the Java ecosystem. This guide deploys the official Bedrock Dedicated Server software through a community Docker image, then configures UDP, player access, worlds and maintenance.
| Aspect | Java | Bedrock |
|---|---|---|
| Server software | Paper, Purpur, Fabric and others | Official BDS; other implementations have different compatibility |
| Clients | Java Edition desktop clients | Compatible Bedrock clients on Windows/mobile/consoles, subject to platform connection rules |
| Typical default port | TCP 25565 | UDP 19132; IPv6 commonly 19133 |
| Extensions | Large plugin/mod ecosystem | Behavior/resource packs; not Java plugins |
| Original rough memory estimate | 100–150 MB/player | 50–80 MB/player |
| Original startup example | 15–60 seconds | 5–15 seconds |
| Host support | Depends on runtime/server | Verify BDS supported Linux release; Docker does not remove kernel/architecture requirements |
Memory/startup figures are illustrations, not measured guarantees; worlds, entities and add-ons dominate. The original's “half the memory” claim is not reliable for every workload.
- Java clients needing Java plugins/mods: choose an appropriate Java server.
- Bedrock-only clients: BDS may fit if their devices can reach your chosen server.
- Mixed Java/Bedrock: evaluate Java plus Geyser, including bridge limitations, version support and authentication setup.
Geyser can run as a plugin or separate bridge. Do not infer that every PC player owns Java, or that mobile support always requires abandoning Java plugins.
Check current official BDS requirements; the original cites 4 GB RAM. Smaller deployments below that are experiments, not a replacement minimum or a promise of ten players on 1 GB:
| Vanilla workload example | Original planning budget | CPU |
|---|---|---|
| 2–4 players | 2 GB for a monitored small trial | About 1 capable core |
| 5–10 players | 2–4 GB, with headroom and actual testing | About 2 cores |
| 10–20 players | 4–8 GB, workload-dependent | 2–4 cores with good per-core performance |
Prefer available single-thread performance and SSD/NVMe for chunk loads. Many entities, redstone machines and exploration can overwhelm a small instance despite enough RAM. The original's 2–3 Mbps for ordinary small-group play is only a starting example; measure peaks and transfer limits.
Test from the players’ actual locations. The source's mainland-China-to-overseas 100–200 ms example is region-specific, not an expected delay for all readers. See game server selection.
The native bedrock_server binary is also a legitimate route, with your own updates, service management and supported OS. itzg/minecraft-bedrock-server automates some of that work; review and pin the image and game version before production.
Create docker-compose.yml, replacing example server names and confirming the EULA yourself:
services:
bedrock:
image: itzg/minecraft-bedrock-server
container_name: minecraft-bedrock
restart: unless-stopped
environment:
EULA: "TRUE"
SERVER_NAME: "周末生存服"
GAMEMODE: survival
DIFFICULTY: normal
MAX_PLAYERS: 10
ONLINE_MODE: "true"
ALLOW_LIST: "true"
VIEW_DISTANCE: 16
TICK_DISTANCE: 4
VERSION: LATEST
ports:
- "19132:19132/udp"
- "19133:19133/udp"
volumes:
- ./data:/data
tty: true
stdin_open: true
/udp matters: 19132:19132 defaults to TCP and will not publish Bedrock's UDP service. EULA: "TRUE" records acceptance required for startup; do not set it without agreeing to the license.
19133 is the demonstrated IPv6 port. Actual IPv6 reachability requires host, Docker networking and firewall support; publishing a second port alone does not create it. Retain tty and stdin_open for console interaction.
docker compose up -d
docker compose logs -f
Server started. indicates startup, but verify a compatible client can join. Persist data and check directory ownership.
The image maps environment settings to ./data/server.properties. Direct edits may be overwritten by environment values at restart, so keep one clear source of configuration and check the generated file.
| Setting | Original example/default | Meaning |
|---|---|---|
server-name | Dedicated Server | Display name |
gamemode | survival | New-player mode: survival/creative/adventure |
difficulty | easy | peaceful/easy/normal/hard |
allow-cheats | false | Enables cheat commands such as /gamemode, still subject to permission |
max-players | 10 | Player cap, not capacity guarantee |
online-mode | true | Account authentication |
allow-list | false | Allowlist access; enable for a private server |
view-distance | 32 | View distance in chunks |
tick-distance | 4 | Simulation radius; original range 4–12 |
player-idle-timeout | 30 | Idle-kick minutes; 0 disables |
Verify defaults against the installed release. Reducing view-distance from 32 to 16 can lower chunk work at the cost of distant visibility. Keep online-mode enabled for public access to avoid impersonation risks. Increasing tick-distance toward 12 keeps more entities/redstone/crops active and may greatly increase load; benchmark before changing it.
Enable ALLOW_LIST: "true" so eligible players in allowlist.json can enter. Avoid editing allowlist.json while running: use console commands so active state and file contents stay aligned.
allowlist add 玩家名
allowlist remove 玩家名
allowlist reload
op 玩家名
deop 玩家名
Attach to the local container console:
docker attach minecraft-bedrock
Type commands and detach with Ctrl+P followed by Ctrl+Q. Ctrl+C is not the detach sequence; Ctrl+C can stop the server and disconnect players. Quote names containing spaces, as in allowlist add "Some Player".
permissions.json defines visitor/member/operator roles. Grant op only to trusted administrators; commands such as stop, kill and rule changes can affect everybody.
The original address placeholder is 你的公网IP:19132. On supported mobile/Windows clients, enter server name, IP/domain and port 19132 under Add Server. Retail Xbox, PlayStation and Switch clients generally lack the same arbitrary-server entry UI; verify supported platform access before renting. Do not promise direct console joining merely because the protocol is Bedrock.
Use an A record for IPv4, or a suitable AAAA record where IPv6/client support is available. Do not assume Java-style SRV discovery works for Bedrock clients. See DNS setup. A normal HTTP/CDN proxy does not forward game UDP.
BDS gameplay itself needs neither a website nor HTTPS. Web administration or maps are separate services requiring their own security and protocols.
Worlds live under ./data/worlds/. Copying active database files can produce an inconsistent restore. For a small service, announce downtime, stop, archive and restart:
cd ~/minecraft
docker compose stop bedrock
tar czf ~/mc-backup-$(date +%F).tar.gz data/worlds data/server.properties data/allowlist.json data/permissions.json
docker compose start bedrock
Verify archive success and service recovery even after errors. The sample includes worlds/properties/allowlist/permissions; include Compose settings, custom packs and other required data too. Choose frequency for acceptable lost progress, not an automatic weekly guarantee, and retain copies off the VPS.
For a reviewed online-backup workflow, save hold pauses saving; issue save hold, poll save query for readiness and required file lengths, copy consistently, then always issue save resume. Ensure save resume runs on failures too. Use the authorized server console and the installed BDS documentation; simply copying at an arbitrary point during hold is insufficient.
World growth depends on explored chunks, entities and play time. Tens to hundreds of MB are only small-world examples; monitor real disk space.
./data/resource_packs/holds resource packs for textures, audio and interface../data/behavior_packs/holds behavior packs for supported entity/game changes.
The world registrations world_resource_packs.json and world_behavior_packs.json must match each pack's manifest UUID and version. Do not invent unrelated random UUIDs for an existing pack; separate pack identities should remain distinct. Review dependencies and experimental features.
Whether clients must accept a resource pack depends on the corresponding server settings. Large downloads, including tens of MB, can delay joins; behavior/resource packs do not supply the complete Java mod ecosystem.
Clients and servers need compatible versions. Console/mobile update behavior varies; do not assume every client update is controllable. VERSION: LATEST can select the latest server through the image's startup logic, but verify the publisher's actual behavior. An image update and a game version update are separate changes.
Pin VERSION when appropriate. Back up before changes such as the original 1.21 → 1.22 example: world formats and add-on compatibility can change, and older servers may not read an upgraded world.
cd ~/minecraft
docker compose pull
docker compose up -d
pull fetches images and up -d recreates containers. ./data preserves mounted files, but persistence alone is not rollback. Keep data, old image/version information and a pre-upgrade world backup.
Cannot connect: check UDP first, then sudo ufw allow 19132/udp, cloud security group and actual Docker exposure. See UFW. Test the advertised address from the player's network.
Version mismatch: verify client and server builds. With VERSION: LATEST, confirm startup actually obtained the intended version; otherwise pin a compatible version.
Container exits: read docker compose logs, verify EULA acceptance and data permissions.
Lag increases: inspect entities, dropped items, farms, CPU contention and view-distance. Measure before buying more RAM.
World corruption: investigate active-file copies, disk exhaustion and storage faults; restore a verified matching-version backup.
Mobile fails while desktop works: check actual IPv4/IPv6 routes and UDP filtering. IPv6 service on 19133 is useful only with end-to-end support; a mobile IPv6 address does not automatically exclude IPv4 access.
Choose based on players' actual editions and connection options, then size for their world and workload. A monitored small trial can establish a useful baseline; verified CPU/storage performance is more useful than an unsupported player-count promise.