Direct answer

Geyser’s Bedrock listener uses UDP, commonly port 19132. This is separate from the Minecraft Java TCP listener, commonly 25565.

Recommended procedure

  1. Identify whether Geyser runs on Velocity, a Paper backend or standalone and edit that instance’s documented configuration.
  2. Set its Bedrock listener port to the assigned UDP port and ensure the host or panel allocates it.
  3. Allow that UDP port through host/router firewalls and avoid double-binding the same port.
  4. Keep the Java TCP connection and proxy forwarding configuration correct for the chosen deployment.

Why this matters

Opening a Java TCP port does not open Bedrock UDP. Conversely, a UDP listener can be working while a Bedrock login still fails later due to Geyser/Floodgate authentication setup.

How to verify the result

Restart Geyser and inspect the listener bind message; test a Bedrock device from outside the local network using the selected UDP port.

Version and compatibility notes

Some hosts allocate special ports or container mappings. Do not hard-code 19132 when the provider requires a different externally accessible UDP port.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

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