How to join your Connect Server

Joining your Server

Every server has a unique configurable Endpoint name that directly reflects the domain players can join the server with. If you leave this field empty, Connect will use a temporary random endpoint name for your server provided by the Random Name Service.

You can always update that endpoint name in the config:

plugins/connect/config.yml

endpoint: your-server-name

Gate config.yml

connect:
  name: your-server-name

The environment variable CONNECT_ENDPOINT takes precedence over the configuration file.

Joining with free provided Public Domain

After installing Connect plugin and starting your server you will see the free public domain for your server that looks like <endpoint>.play.minekube.net.

Server Console

[connect] Enabling connect vX.Y.Z
[connect] Enpoint name: live-beru
[connect] Your public address: live-beru.play.minekube.net

Use that same endpoint hostname in either edition:

Client	Server address	Port
Java Edition	<endpoint>.play.minekube.net	25565 (normally omitted)
Bedrock Edition	<endpoint>.play.minekube.net	19132

Verified custom domains work the same way: Java and Bedrock use the same hostname and their edition's normal port.

Ping requests are also mirrored to the endpoint server.

Joining from Browser Hub

Players can also discover your server from the in-game Browser Hub at minekube.net and can join with the in-game UIs or with the /browser join <your-server-name> command. Offline/cracked Java players use cracked.minekube.net or cracked.minekube.com instead and can only enter endpoints that explicitly allow them.

See Who Can Join for the Java, Bedrock, account-linking, and offline-mode identity matrix.

Who Can Join

This matrix applies when players use a Connect address and the server owner runs a normal Connect plugin or standard Gate connector:

Player identity	Accepted by default	Identity used by the endpoint	Server-owner action
Java client authenticated with a Java Edition account	Yes	Verified Java UUID and profile	None beyond the normal Connect setup
Bedrock client authenticated with Microsoft/Xbox and authoritatively linked to Java	Yes	Linked Java UUID and profile	None
Bedrock client authenticated with Microsoft/Xbox but not linked to Java	Yes	Stable native Bedrock/XUID-derived profile	None
Offline/cracked Java client	No	Self-asserted offline Java name and UUID	Explicitly allow offline-mode players
Bedrock client without valid Microsoft/Xbox authentication	No	None; Connect rejects the session	Unsupported on Connect-managed Bedrock

Account linking is optional for Connect-managed Bedrock. When Connect can verify an authoritative Java link, it preserves that Java identity; otherwise, the player's verified Xbox identity is enough. A backend plugin that is specifically written to require a premium Java UUID can still reject a native Bedrock profile, so diagnose that plugin rather than enabling offline mode or installing another Geyser instance.

What the Server Owner Configures

For authenticated Java and Microsoft/Xbox-authenticated Bedrock players, configure only the normal Connect connector. Connect handles Bedrock translation at the edge. Do not install backend Geyser or Floodgate, open a backend UDP port, or set Gate bedrock: true for Connect-routed players.

Offline/cracked Java is a separate, explicit opt-in. The Offline Mode guide shows the setting for both the Connect Java Plugin and Gate.