Quick Start
This page explains the steps to use Connect with your Minecraft server or network.
Prerequisites
- You have a Minecraft server running anywhere (locally or remote).
- You have a Java client, a Bedrock client signed in to Microsoft/Xbox, or an offline Java client for testing an endpoint that explicitly allows offline players.
Go to the Connect Dashboard! Optional
Proceed the Quick Start from there:
If you want to use the Connect Dashboard after the set-up, follow the steps below. You can later import your Minecraft Endpoints to the dashboard to manage them.
Step 1: Choose a Connector
Connectors are the link between your Minecraft Endpoints and the Connect Network.
Step 2: Launch your Connector
Follow the guide of the Connector you chose to install and launch it. The first time the Connector is launched, the Endpoint will be protected with a token, that you can reset in the Dashboard at any time.
-> If you face serious issues get help in the Discord.
Done!
Your Minecraft server is now protected by the Connect Network and players can join it at <endpoint>.play.minekube.net!
Java and Bedrock players use the same endpoint address. Bedrock support is handled by the Connect edge for Connect-routed players, so Paper/Spigot, Velocity, and BungeeCord plugin users do not need to install Geyser or change Gate Bedrock settings.
What works with the normal setup
- Authenticated Java players can join.
- Microsoft/Xbox-authenticated Bedrock players can join with or without a linked Java account.
- Offline/cracked Java players require the endpoint owner to opt in.
- Bedrock players without valid Microsoft/Xbox authentication cannot join the managed Bedrock path.
See Joining Servers for the complete address, port, identity, and configuration matrix.
Next Steps: Consider to import your Endpoints to the Connect Dashboard.
Getting Help
If you need help, join the Minekube Community Discord and post a support request in the #support forum.
-> https://minekube.com/discord
Endpoint Token
If you get an authentication error from the Watch service, check that the token your Connector uses still matches the token stored for this endpoint in the Dashboard. Resetting the token in the Dashboard invalidates the previous token immediately, so a Connector that keeps using the old one keeps failing with the same error until you place the new token and restart it.
The token belongs in the Connector's token file, never in the Connector config that holds the endpoint name: the Gate connector reads connect.json next to its config, the Java Plugin reads token.json in its data directory, and both accept the CONNECT_TOKEN environment variable, which takes precedence over the file. Copy the token byte-for-byte: a trailing space or newline is a different token.
If the endpoint name belongs to an organization, the token must have been created for this endpoint name inside that organization. A token from another organization, or for a different endpoint name, is rejected with the same error and cannot take the name over; if the name is not yours, choose a different endpoint name.