Geyser Not Working? Fix Bedrock Players Who Can't Join

If Geyser is not working, first check that Java players can join. Then check that Geyser's port differs from the Java port and is open for TCP and UDP, that transport is nethernet, and that Floodgate is installed with auth-type set to floodgate. Run geyser connectiontest to see what Geyser suggests.

The quick checks

1. Check that Java players can join

The Geyser wiki says an "unable to connect to world" error usually comes from an improper Geyser configuration or from network issues, and that if Java players cannot join either, it should not be a Geyser problem. Test with a Java account first. If that fails too, the server is offline, the Java port is blocked or a plugin is broken. Check the server is reachable from outside with a status checker such as mcsrvstat.us. With a host, contact them. Once Java works, move on.

2. Run the connection test

Geyser has a built-in test. Run it from the server console with the Geyser port you use:

geyser connectiontest YOUR-ADDRESS 19132

The Geyser wiki says the command checks whether your server is theoretically reachable by Bedrock Edition and tells you what to try next. Read its answer before you change anything else.

3. Use the Java address with the Bedrock port

Bedrock players need your server's address and the Bedrock port from Geyser's config, which is 19132 by default. They must not use the Java port. The two must be different numbers. If a player's old entry still points at a changed address or port, delete it and add the server again. How to add a server in Minecraft Bedrock shows the fields.

4. Port, transport and firewall

Open plugins/Geyser-Spigot/config.yml and look at the bedrock: section. As of November 2026, the Geyser setup page says to set the port and turn on NetherNet:

bedrock:
  port: 19132
  transport: nethernet

• Open TCP and UDP. With NetherNet, Geyser uses the same port over both. The wiki page on this error is older: it says forwarding only TCP will not work and that UDP is required. With NetherNet you need both.
• Keep the port off the Java port, and do not let another program use it. Historically very low port numbers caused problems; the wiki says 10000 or above seems safe.
• On a hosting panel, the host assigns ports. The wiki notes that Pterodactyl users may need a port other than 19132, so use the number you were given.
• Leave address alone unless you know why you need it. NetherNet does not work if it is set to 127.0.0.1. On a Windows machine with several network adapters, set it to the local IP of the adapter you use.
• Check the firewall. If connections only work from the same machine, add an exception for Java and for the Geyser port.

Keep a few more details in mind. Geyser's clone-remote-port setting does not work with the built-in sign-in handshake, because Java already uses that TCP port, so give Geyser its own port. And if Bedrock players see a "trust on first use" prompt, that is not a failure: built-in signaling is plain HTTP by default, and Geyser has an HTTPS option.

5. Floodgate and auth-type

If Bedrock players are asked for a Java account, Floodgate is missing or Geyser is not set to use it. Fix both:

1. Check that Floodgate-Spigot.jar is in the plugins folder.
2. In Geyser's config.yml, find auth-type and make sure its value is floodgate.
3. Restart the server, not just reload it.
4. If you use a whitelist, add Bedrock players with fwhitelist add and their Bedrock name.

On a proxy such as Velocity or BungeeCord, install Geyser on the proxy. If you also use Floodgate on the backend servers, turn on send-floodgate-data in the proxy's Floodgate config and copy the proxy's key.pem to each backend's Floodgate folder. Never share that key: it lets accounts skip Java authentication.

6. Update Geyser and match the versions

Geyser has to follow Minecraft. As of November 2026, its wiki says Geyser supports Minecraft Bedrock 26.40 to 26.62 and Minecraft Java 26.3. Two things follow from that:

• After a Bedrock update, update Geyser. Stop the server, replace the JAR in plugins with the newest build from the GeyserMC download page, then start it. The wiki's advice is to shut the server down, swap the JAR and only then start it.
• The Java server must accept a 26.3 player. If it runs another version, install ViaVersion. Geyser on Paper or Spigot needs 1.20.5 or newer and Java 21 or newer.

The full setup, with each step, is in how to set up Geyser and Floodgate. If your friends are on consoles and cannot type an address, see how to join a Bedrock server on Xbox, PlayStation and Switch.

Fix and run Geyser on TheGameHosting

The checks are the same on our panel, and most of them are quicker there because you edit files in the browser.

1. Open your server on Minecraft Java server hosting. The plans page lists all nine plans, from 2 GB to 64 GB.
2. In Files, open plugins/Geyser-Spigot/config.yml and edit the port, transport and auth-type.
3. Replace the Geyser JAR in Files after each Bedrock update.
4. Restart from the panel, then watch the Console while the plugins load.

Crossplay is available on every plan, and our support team can look at the console with you through live chat or a ticket. If you want to understand the whole idea first, read can Java and Bedrock play together. If you want a server for Bedrock players only, see Minecraft Bedrock server not showing up.

FAQ

Hosting for these games

• Minecraft Bedrock hostingPhones, consoles and Windows
• Minecraft Java hostingPaper, Purpur, Fabric, Forge and more