cloudhider.Connect Minecraft Java
Minecraft Java is a separate team resource. HTTP proxying and browser challenges are not used for game traffic.
Choose a workspace and add a server
Open a team workspace → Game servers → Add game server. From the platform overview, choose a workspace directly on the page first. Enter a name, game node, public origin IPv4 and Minecraft TCP port. Management requires an owner or administrator with the necessary permissions.
Set connection limits
Configure concurrent connections, per-IP connections and new attempt limits. Players sharing a public IP share limits. The first handshake is checked before connecting to origin; this is not authenticated-account verification or anti-cheat.
Connect players and DNS
First test the assigned IP:port in Minecraft Java. For your hostname, create a DNS-only A record pointing to the game node IP. Add the _minecraft._tcp SRV record shown in server details to omit the port. After testing, restrict the origin game port to the node IP while preserving SSH access.
Check readiness
Wait for the saved revision to be acknowledged and a Minecraft status response. With enable-status=false, players may connect even if status diagnostics are unavailable. Changing settings disconnects current connections. Enable PROXY v2 only after configuring backend support; keep Minecraft account authentication enabled.
Beta limits
Up to five servers per workspace and 200 connections per server. Minecraft Java TCP on DE is supported. Bedrock, UDP, regional failover and network-saturation mitigation are not included. Counters reset on process restart or endpoint configuration changes.