How to Set Up Geyser for Java and Bedrock Cross-Play

Enable crossplay between Bedrock and Java Edition players using the Geyser plugin. This guide covers finding an available port, installing Geyser on your server, and configuring it for Bedrock connections. Geyser works on any Java Edition server, including Minecraft server hosting at WinterNode, where new servers already include the extra ports Bedrock connections need.

Check Your Available Ports

Geyser needs its own port for Bedrock connections. Bedrock players use it over TCP to find your server and over UDP to play on it, so it can’t be your Java server’s port. New servers automatically include additional ports you can use, and each one already works for both TCP and UDP:

1. Navigate to Management → Allocations in your control panel
2. Look for unused ports - you’ll see your primary port plus several additional ports
3. Choose a port close to the default Bedrock port (19132) - typically 19134 or the closest higher number available
4. Note this port number for the configuration step

Install Geyser

1. Visit geysermc.org/download and download the latest version for your server software (Paper, Spigot, Fabric, NeoForge, BungeeCord, or Velocity). You need Geyser 2.12.1 or newer for Bedrock 26.60 players to join.
2. Stop your server
3. Upload the Geyser JAR file to your plugins/ folder (or mods/ for Fabric/Forge)
4. Start your server to generate the Geyser config file
5. Stop your server again

Configure Geyser

1. In your control panel sidebar, click Files
2. Open plugins/Geyser-[platform]/config.yml (on Fabric or NeoForge, config/Geyser-[platform]/config.yml)
3. Find the bedrock section and set the port, transport and advertise address:

bedrock:
  address: 0.0.0.0
  port: 19134  # Replace with your available port from Allocations
  transport: nethernet
  signaling:
    advertise-addresses:
      - 203.0.113.10  # Replace with your server's IP address

4. Save the file and start your server
5. Check the console. Geyser should start without NetherNet or signaling errors.

transport: nethernet is the connection method Bedrock 26.60 and newer require. advertise-addresses tells Bedrock players which IP to connect to; use the IP shown in your server address, without the port. Your config may list other signaling settings below it; leave those as they are.

Bedrock players can now connect by going to Add External Server in Bedrock’s server list (on phones, tablets, and Windows PCs), entering your server address, and changing the Port field from the default 19132 to your assigned port (e.g., 19134). The first time they join, Bedrock shows a Trust on First Use? prompt. That’s expected; players accept it once.

Updating an Existing Geyser Server for Bedrock 26.60

If Bedrock players could join before October 27, 2026 and now can’t, your Geyser is still using RakNet, the connection method Bedrock 26.60 removed.

1. Stop your server
2. Replace the Geyser JAR with the latest build from geysermc.org/download (2.12.1 or newer). Update Floodgate at the same time if you use it.
3. In Geyser’s config.yml, add the transport and signaling lines shown in Configure Geyser
4. Check that port is a separate port from Management → Allocations, not your Java port. If clone-remote-port is set to true, change it to false.
5. Start your server

Players keep using the same address and port as before, unless you had to change the port in step 4.

Adding Floodgate (Strongly Recommended)

Without Floodgate, Geyser alone only allows Bedrock players who also own Java Edition to connect. Most console and mobile players only own Bedrock - they’ll hit an authentication error and get kicked before they can even load in. Floodgate solves this by handling Xbox/Microsoft authentication directly, so any Bedrock player with a valid Xbox account can join regardless of whether they own Java Edition.

Beyond authentication, Floodgate adds several things that improve the crossplay experience: Bedrock player skins render correctly for Java players, Bedrock-aware plugins can send native Bedrock UI forms, and players who own both editions can link their accounts using Global Linking so their progress, permissions, and data stay unified across both versions.

1. Download Floodgate from geysermc.org/download (same platform as Geyser)
2. Stop your server
3. Upload the Floodgate JAR to your plugins/ folder (or mods/ for Fabric/Forge)
4. Start your server

Bedrock players can now connect without a Java account. Their usernames will have a . prefix to distinguish them from Java players (e.g., .BedrockPlayer). Your server stays secure - Floodgate still requires a valid Xbox account, it just drops the Java Edition license requirement.

About Geyser

Geyser is a packet translator that converts Bedrock Edition network traffic into Java Edition traffic. This means Bedrock players on consoles, mobile, or Windows 10/11 can join your Java server. Console players need one extra step, covered in Connect Xbox and Consoles.

Version requirements: Geyser only supports the latest Minecraft release because Bedrock Edition can’t run older versions. If you’re running an older Java server version, install ViaVersion to let newer clients connect.

Port and domain: Bedrock doesn’t support SRV records, the DNS record type that lets you hide non-standard ports behind a clean domain. If you use a custom domain or our Domains tool, Bedrock players still need to enter your Geyser port (for example 19134) in the Port field when adding your server. Your Java port won’t work for them. A dedicated IP lets you run on port 19132, which removes that requirement since 19132 is the port Bedrock defaults to.

We see this combination requested frequently for servers trying to build cross-platform communities. The Geyser team maintains excellent documentation at wiki.geysermc.org, which we recommend checking for advanced configuration options and troubleshooting.