Direct answer
Bedrock clients do not join a Java Edition server directly. Install and configure a supported bridge such as Geyser, or provide a separate Bedrock Dedicated Server for Bedrock-only play.
What it means
Java and Bedrock editions use different network protocols. Geyser translates Bedrock traffic to Java traffic; Floodgate is an optional authentication component for supported Bedrock-account sign-in setups.
If you are a player
- Confirm you are entering the Bedrock server address and its UDP port, not the Java TCP port.
- Check whether the server advertises Bedrock support before assuming the Java IP works on mobile or console.
If you run the server
- Check whether Geyser is installed on the proxy or backend and that its Bedrock listener has started.
- Confirm the configured Bedrock UDP port is reachable externally and allowed in host/router firewalls.
- Follow the current Geyser authentication documentation and check whether Floodgate is required by the chosen mode.
- Test from a Bedrock device outside the local network; a working Java TCP connection does not prove UDP reachability.
Confirm the fix: Validate player identity and inventory consistency after connecting; do not change the Java backend to unauthenticated mode merely to accept Bedrock players.
References
Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.
- GeyserMC: Setup
- GeyserMC: Fixing Unable to Connect to World
- PaperMC: Getting started / Java requirements
Related fixes and guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.