This works without router changes, a static IP or dynamic DNS, and it works when your ISP has you behind CGNAT. Raw TCP tunnels for Java are on every plan, including Free. Bedrock uses UDP, so it needs a UDP tunnel; advanced UDP for game servers is on Pro and above.
Why doesn't port forwarding work?
Many home connections sit behind the ISP's shared NAT (CGNAT). Forwarding 25565 on your router then does nothing, because inbound connections stop at the ISP. Our CGNAT guide shows how to check. A tunnel avoids the problem: your PC connects outbound to the Zorven server, and players connect to the Zorven server too.
Which port and protocol do Java and Bedrock use?
Java Edition uses TCP and Bedrock uses UDP, which decides the tunnel type:
| Item | Java Edition | Bedrock Edition |
|---|---|---|
| Protocol | TCP | UDP |
Default port (server-port) | 25565 | 19132 (19133 for IPv6) |
| Zorven tunnel type | Raw TCP, target tcp://127.0.0.1:25565 | UDP, target udp://127.0.0.1:19132 |
| Plan | All plans (Free included) | Advanced UDP on Pro and above |
| What players do | Multiplayer > Add Server, zorven.app:PORT | Servers > Add Server, address zorven.app, PORT in the port field |
Step 1: Run the server on your PC
Start the Java server (server.jar) or Bedrock Dedicated Server as usual and confirm you can join from the same PC via localhost. If you changed the port, note the server-port value in server.properties.
Step 2: Install the Zorven client
Create a free account at panel.zorven.app, add a client and copy its token. On Windows use the installer from the download page; on Linux and macOS:
curl -fsSL https://zorven.app/install.sh | sudo bash -s -- --token zrv_live_...
The installer runs the client as a background service, so the tunnel comes back after a reboot.
Step 3: Create the tunnel in the dashboard
- Click "New tunnel" and pick the computer running the server as the client.
- For Java choose raw TCP with target
tcp://127.0.0.1:25565. For Bedrock choose UDP with targetudp://127.0.0.1:19132. - In reserved-port mode the dashboard shows the tunnel's connection address,
zorven.app:PORT. Copy it.
The docs cover tunnel settings and every CLI command.
Step 4: How do friends connect?
On Java, a friend opens Multiplayer > Add Server and enters zorven.app:PORT. On Bedrock, they open the Servers tab, choose Add Server, put zorven.app as the address and the number from the dashboard as the port. Nobody installs anything.
How is this different from Hamachi?
Hamachi builds a virtual LAN that every player joins, and its official page says the free version covers up to 5 computers per network. With a Zorven reserved-port tunnel, players install nothing and connect from inside the game. If you would rather share the server only with specific people and keep it off the public internet, there is a Hamachi-like option as well: zorven share shares a port end-to-end encrypted (WireGuard) with the people you choose, on every plan; each of them runs the Zorven client.
zorven share 25565 --to friend@example.com --name mc
# on your friend's computer:
zorven access mc --local 25565
Add --udp to the share for Bedrock. Your friend then joins 127.0.0.1:25565 in the game.
Performance: what about latency and traffic?
Traffic is relayed through the Zorven server rather than going direct: player → Zorven server in Istanbul → your PC. Latency is therefore roughly the player's distance to Istanbul plus yours. Players in or near Türkiye usually notice little difference; players far away can see a higher ping than a direct connection would give. The dashboard's "UDP and Game" tab measures latency and packet loss between the server and your client.
Traffic counts toward the plan quota: 5 GB per month at 10 Mbps on Free, 20 GB on Hobby, 100 GB on Pro. When the quota runs out the connection is throttled (1 Mbps on Free), not cut. The Minecraft status panel (online state, player count, MOTD) is on Pro and above. Compare plans on the pricing page.
Security: what changes with no open ports?
- No port is opened on your router, and players see the Zorven server's address, not your home IP.
- The tunnel's port is reachable by anyone who knows it. Use
white-list=true(Java) orallow-list=true(Bedrock) inserver.propertiesand keeponline-mode=true. - On Pro and above, IP allowlists, country (Geo) rules and web door access let you open the port only to friends who sign in.
For other home-server use cases see Zorven for individuals; to receive webhooks on localhost, read test webhooks locally. All guides are listed under guides.
Start free Download the client
When should you use something else?
- A large public server is better on rented game hosting or a VPS; your PC has to stay on and your home upload speed becomes the limit.
- If your ISP gives you a public IP and your players are far from Türkiye, direct port forwarding gives the lowest latency.
- Free Bedrock hosting: be aware that advanced UDP for game servers is a Pro feature (with a 7-day free trial).
Frequently asked questions
Sources
- Minecraft Wiki: server.properties (server-port, white-list, allow-list, online-mode) (accessed: 2026-11-08)
- Minecraft Wiki: Setting up a Bedrock Edition server (UDP 19132) (accessed: 2026-11-08)
- LogMeIn Hamachi official page (free for up to 5 computers) (accessed: 2026-11-08)
- Zorven docs: tunnels, zorven share and access (accessed: 2026-11-08)
- Zorven pricing and plan limits (accessed: 2026-11-08)