Bedrock and Java players are not two flavours of the same connection arriving at the same door — Bedrock speaks an entirely different network protocol, which is exactly why it needs a listener of its own rather than simply being let in through the existing game port.
Why one port cannot serve both
Java Edition connects over TCP; Bedrock Edition connects over UDP, using RakNet rather than the game's own protocol directly. A shared node cannot bind more than one service to the same default Bedrock port (19132 UDP) across different tenants, so GeyserMC — which translates Bedrock's protocol into something the Java-side server understands — needs its own dedicated allocation to listen on.
What to do
- Request or select a secondary port allocation in the panel
This is the address GeyserMC will actually listen on.
- Set that same port, with protocol UDP, in Geyser's
config.ymlThe protocol field matters — Bedrock traffic will not arrive on a port configured for TCP.
- Give Bedrock players the custom port explicitly
Unlike Java's default-port convenience, Bedrock clients on a shared node always need
address:portwritten out, since 19132 is never uniquely theirs on shared infrastructure.
A Bedrock client connecting to the node's address on the custom port reaches the world, and Geyser's own startup log confirms it bound to that port successfully.