Direct answer

A Bedrock Unable to connect to world error through Geyser often means the client cannot reach Geyser’s UDP listener, or the Geyser-to-Java/authentication bridge cannot complete login. Start by separating transport from login errors.

What it means

Java Edition normally connects over TCP; Bedrock joins Geyser over UDP. A green Java server-list entry cannot prove the Bedrock port works.

Practical example: Example: port scanners for TCP 25565 may report Java as reachable while Bedrock UDP 19132 is filtered by a provider firewall. That is a transport issue, not a Geyser version mismatch. If UDP reaches Geyser and its log displays a downstream authentication refusal, move to Floodgate and Java protocol diagnostics.

If you are a player

  • Confirm the Bedrock address and port supplied by staff, rather than assuming it is the Java 25565 port.
  • Try another network and update Bedrock to a protocol version supported by the installed Geyser release.
  • Report whether the error happens immediately or after the joining screen.

If you run the server

  1. Read the Geyser startup log for its UDP bind address and port.
  2. Check inbound UDP permission in the router, host and provider firewalls.
  3. Use Geyser’s documented connection test for the external address and port.
  4. If UDP connects but login fails, inspect Floodgate placement, auth mode and Java protocol compatibility.
  5. Verify a normal Java client can still join and a Bedrock client can interact after login.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000