Share a Minecraft Java server without port forwarding
Let friends reach a Minecraft Java server running behind your home router through a TCP tunnel. Each player runs Tubu; no VPN, public IP, or port forwarding required.
You need Node.js 26.7 or later and a Tubu API key on the publisher machine. Follow the Quick start to get your key. Replace YOUR_API_KEY and choose an available Tubu domain in the examples. The publisher must reach the target service and connect outward to Tubu. Keep it running while access is needed.
Friends cannot reach the server on your home network
Your server works locally, but your router or ISP uses NAT and you cannot open an incoming port. Tubu can carry a TCP game connection through its relay. This recipe targets Minecraft Java Edition; games that require UDP need a different transport. Tubu does not supply the game server or its compute resources.
Start your Java server and publish its TCP port
Set up the official Minecraft Java server and verify that it accepts local connections on port 25565. Keep player authentication enabled. Then run Tubu on the same machine:
npx tubu-cli tcp 25565 --domain my-minecraft.tubu.dev --authtoken YOUR_API_KEYWait for Tunnel ready. Keep the game server and publisher running. If the server runs on another LAN machine, use its private IP in a target such as tcp://192.168.1.70:25565.
Each player starts a local Tubu listener
Each player needs Node.js 26.7 or later and runs this on their own computer:
npx tubu-cli forward 25565 --domain my-minecraft.tubu.devAfter Listening, open Minecraft Java’s Direct Connection and enter:
127.0.0.1:25565Players do not need your Tubu API key. They cannot enter my-minecraft.tubu.dev directly in the game; the listener bridges the game’s TCP connection into Tubu’s WebSocket transport. If port 25565 is already in use, choose another listener port and use that same port in the game.
Verify a real multiplayer session
Expect to join the hosted world and see the player in the server logs. Test joining, world loading, and sustained play with your server version before inviting a larger group. This recipe is based on TCP transport and is not a game compatibility or latency guarantee.
The relay adds a network hop, and game traffic counts toward your Tubu traffic allowance. Keep each player’s listener running. Check the local server first if joining fails. Stop the publisher when the session ends. This recipe does not cover Minecraft Bedrock Edition or console clients.