Direct answer

Verify the actual Bedrock port in Geyser, then allow/forward that port as UDP. The default is 19132, but hosts and `clone-remote-port` can change it. In Docker the mapping needs `/udp`; in Pterodactyl the UDP port must be assigned to the server.

What it means

Bedrock uses UDP. Exposing only TCP on the Geyser port is a common reason Java players can join while Bedrock players cannot.

If you are a player

  • Copy the exact connection/kick message and note the timestamp; similar-looking login errors can have different causes.
  • Check the address, port, Minecraft version, and whether other players can connect at the same time.
  • Tell the owner whether the problem follows your account/device/network or affects everyone.

If you run the server

  1. Check the Geyser config for the current Bedrock port and `clone-remote-port` behavior.
  2. Open the same UDP port in host firewall and router/provider firewall.
  3. Do not rely on a TCP-only port-check website to prove a UDP Bedrock listener works.
  4. Use `geyser connectiontest <ip> <port>` for the Geyser-specific reachability check.

References

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

Focused diagnostic check: Geyser's Bedrock listener normally requires inbound UDP on the configured Bedrock port, independently of the Java server TCP port. Confirm the configured listener address and UDP forwarding on the host firewall, router or provider panel; TCP port-checking sites alone cannot establish UDP reachability.

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