Minecraft Java proxy · Docker
Create a proxy Compose file
Choose the proxy runtime, downloads, plugins, and operational settings. The generated Compose file remains importable and ready to extend.
Proxy runbooks
Build the complete network
Continue from the generated Compose file to forwarding, backend isolation, troubleshooting, and Bedrock crossplay.
Set Up a Velocity Proxy with Docker Compose and itzg/mc-proxy
Run Velocity and Paper together with Docker Compose, route players through the proxy, keep backend ports private, and validate the complete connection path.
Configure Velocity Modern Forwarding with Paper in Docker
Match Velocity and Paper forwarding settings, protect the forwarding secret, block direct backend access, and verify that player identity reaches Paper safely.
Velocity Proxy Cannot Connect to a Backend in Docker: A Runbook
Fix Velocity backend connection failures by checking container state, Docker networks, service-name DNS, the container port, Paper readiness, and forwarding separately.
Run Geyser and Floodgate on a Velocity Proxy with Docker
Add Bedrock crossplay at the Velocity edge, publish UDP 19132 correctly, configure Floodgate authentication, and keep Geyser off the individual backends.
What do I do with the generated file? +
- 1Configure every backend server first, including offline mode, player forwarding, and firewall isolation.
- 2Save the generated file as compose.yml in a new folder.
- 3Keep /server persistent and add your proxy configuration through a bind mount to /config when the generated defaults are not sufficient.
- 4Allow 25565/tcp through Docker, the host firewall, and your provider firewall. Do not publish backend ports to the internet.
- 5Start the proxy with docker compose up -d and inspect startup, downloads, config sync, and the healthcheck with docker compose logs -f.
Connect the proxy and Minecraft servers securely
The proxy accepts player connections and sends them to your Minecraft servers. Configure the same forwarding method in the proxy and on the destination servers.
Players must not be able to reach the destination servers directly from the internet. Allow their ports only from the proxy, for example through a private Docker network and firewall rules.
Define which hostname and port lead to each server in config.yml or velocity.toml. The Docker image handles installing and starting the proxy.