How do I set up GeyserMC so Bedrock players can join?

GeyserMC translates the Bedrock protocol to Java, so players on phones, tablets, consoles and the Windows version of Minecraft can join your Java server.

Want your own Minecraft server? At HostValues from €2.80 per month, online within minutes. View plans →

1. Make sure your server runs on Paper. You can set this in the Versions tab.
2. Download the Geyser plugin (Geyser-Spigot) from the official GeyserMC website and upload the .jar file to the plugins folder.
3. Restart the server so Geyser creates its configuration file.
4. Geyser needs its own port, for TCP and UDP, not the port of your Java server. If the Network tab in the game panel shows only one port, open a support ticket and we will set up an extra port for you.
5. Open plugins/Geyser-Spigot/config.yml and, under bedrock, set the port value to that extra port.
6. Restart the server once more.

Bedrock players add the server with the IP address of your server and the port from step 5.

NetherNet and Bedrock 26.60 (27 October 2026)

Bedrock 26.60 is planned for 27 October 2026. After that, Bedrock players no longer connect over RakNet. They use NetherNet instead. So switch Geyser to NetherNet now:

1. Download Geyser-Spigot and Floodgate-Spigot from geysermc.org/download. Build 1237 is the minimum. Take the latest build.
2. Check in the Network tab how many ports your server has.
3. Does Geyser have its own port? Then set these values under bedrock: in plugins/Geyser-Spigot/config.yml:

   bedrock:
     port: <your Geyser port>
     clone-remote-port: false
     transport: nethernet

   That is all. The panel already opens every port for TCP and UDP. Your players keep their address.
4. Is Geyser on the port of your Java server (clone-remote-port: true)? Then ask for an extra port through a support ticket. After that, set port to the new port, clone-remote-port to false and transport to nethernet. Your players then use the new port number.
5. No extra port possible? Leave clone-remote-port: true as it is and set transport: nethernet. Geyser then uses Warden. Players connect to the address that the console shows.
6. Restart the server. The console should no longer show the message "NetherNet support is NOT enabled".
7. Update Geyser once more after the 26.60 release. Geyser only knows 26.60 after the release.

Do players get a timeout when they connect? Add the line advertise-addresses: ["<IP of your server>"] under signaling: and restart. The first time, Bedrock asks players whether they trust the server. That is normal. Choose to trust it.

On Fabric or NeoForge, put the jar in mods/. The config is then in config/Geyser-Fabric/ or config/Geyser-NeoForge/. This only works on 26.3. Fabric also needs Fabric API. Using Velocity? Put Geyser on the proxy only and follow the same steps in plugins/Geyser-Velocity/config.yml.

Do friends play on Xbox, PlayStation or Switch? BedrockConnect does not work with NetherNet yet. So we cannot promise anything about consoles.

Do you have a Bedrock server without Geyser? It does not update itself. Reinstall it after the release of Bedrock server 26.60 through Settings, Reinstall Server. Your world, allowlist and permissions stay. Then check that server.properties contains transport=nethernet. The server needs a UDP port per player, and server-udp-ports must list those extra ports. Ask for extra ports through a support ticket.

Never set transport to raknet again. It stops working after 26.60.

Floodgate

By default, Bedrock players also need a paid Java account. If you do not want that, additionally install the Floodgate plugin by the same developers. Bedrock players can then join with just their Microsoft account. In that case, set the auth-type value in the Geyser config to floodgate.

Keep in mind that some plugins do not work fully for Bedrock players, because their client displays certain features such as custom menus differently.