How to Fix Common Geyser Connection and Login Errors

"Unable to Connect to World" on Bedrock

This usually means the Bedrock client can't reach the UDP port. Confirm the port in Geyser's config.yml matches what you typed into the Bedrock server entry, and that the port is open in your firewall and router. If your host only exposes one port, enable clone-remote-port so Geyser shares the Java port. Also make sure you're using the server's public IP, not localhost, when connecting from another device.

Login or Authentication Failures

If Bedrock players get kicked during login, check auth-type. Use online for authenticated Java servers, or floodgate if Floodgate is installed. A mismatch here is a very common cause of login errors. If you use a proxy, ensure Geyser is configured to forward to the correct backend and that the proxy's player-info-forwarding (modern forwarding) is set up consistently with your proxy type.

Version and Resource Pack Issues

Geyser supports a range of Bedrock and Java versions, but very new or very old clients may be unsupported. Update Geyser and Floodgate to current builds. If custom Java resource packs cause Bedrock clients to disconnect, try disabling resource pack sending in the config or converting packs for Bedrock compatibility. Check the server console for Geyser error messages — they usually name the exact cause, such as an unreachable remote address or a blocked port.