Crossplay: Bedrock players (mobile, consoles, Windows) on a Java server

Java and Bedrock are two different editions of Minecraft that can't play together on their own. The Geyser plugin translates between them, so players on phones, Windows (Bedrock), Xbox, PlayStation or Switch can join your Java server too. With the Floodgate add-on, they don't even need a Java account. This guide covers the installation, the port setup and every important option.

How Geyser and Floodgate work#

Java Edition talks over TCP, Bedrock Edition over UDP and with a completely different protocol. Geyser runs as a plugin on your server, listens on a UDP port for Bedrock players and “presents” each of them to the server as a Java player.

Floodgate adds a prefix to Bedrock players' names (a dot by default, for example .Steve123), so they don't get mixed up with Java players who have the same name.

Supported servers and versions#

• Server type: Paper or Purpur (Geyser-Spigot), Fabric and NeoForge (Geyser as a mod), or a Velocity proxy. Geyser doesn't work on Vanilla.
• Minecraft version: Geyser connects to the server as a Java client of one specific version. As of October 1, 2026, it supports Java 26.2 and Bedrock 26.30–⁠26.51 (the current status is on the Supported versions (opens in a new window) page).
  • Server on an older version (Paper or Purpur 1.20.5 and newer): also install the ViaVersion plugin. On servers older than 1.20.5, Geyser doesn't work as a plugin.
  • Server on a newer version than Geyser supports yet (for example 26.3): the most reliable option is to wait for a Geyser update (watch the Supported versions page), or to create the new server on a supported version. The Geyser documentation only counts on ViaVersion for servers older than the supported version. The ViaVersion and ViaBackwards pair can bridge the gap for a while, but it isn't officially documented – only try it with a backup. The catalog in the Plugins tab won't offer you Geyser for such a version, so you'd upload Geyser-Spigot.jar by hand from geysermc.org/download (opens in a new window).
  • Geyser as a mod (Fabric, NeoForge) works only on the version Geyser currently supports.
• UDP port: Bedrock connects over UDP. Our server ports work for both TCP and UDP, so you can use either the game port or an additional port (see below).

Installing on Paper and Purpur#

1. Create a server backup in the Backups tab.

2. Open the Plugins tab › Browse, choose Modrinth as the source and search for Geyser.

3. On the Geyser project by GeyserMC, click Install and confirm.

   The catalog only shows versions for your server. If you can't find Geyser for your version, it most likely doesn't support it yet (see above).

4. Download Floodgate for Spigot/Paper to your computer from the official page geysermc.org/download (opens in a new window) (the Floodgate-Spigot.jar file). On Modrinth, Floodgate is only available for Fabric and NeoForge.

5. In the Files tab, open the plugins folder and upload the file with the Upload button. In the plugin list it will be marked Uploaded manually (you then keep track of its version and updates yourself).

6. Restart the server.

   The console shows the line Started Geyser on 0.0.0.0:19132 (or Started Geyser on UDP port 19132), and the folders plugins/Geyser-Spigot and plugins/floodgate (with the key.pem file inside) are created.

Now set up the port and Floodgate.

The port for Bedrock players#

By default, Geyser listens on port 19132. That port doesn't belong to your server at StormHost, so nobody can connect on it. Pick one of two options:

The Java game uses TCP and Bedrock uses UDP, which is why they can share the same port number.

Option A: the same port as Java#

1. In the Files tab, open plugins/Geyser-Spigot/config.yml.

2. In the bedrock section, set clone-remote-port: true:

   bedrock:
     address: 0.0.0.0
     port: 19132
     clone-remote-port: true

   Don't change the port value – with clone-remote-port turned on, Geyser replaces it with the Java server's port on every start.

3. Save the file (Ctrl+S).

Option B: a separate port#

1. In the Network tab, under Additional ports, click Add port and note the new number.

2. In the Files tab, open plugins/Geyser-Spigot/config.yml.

3. In the bedrock section, enter the new port and leave clone-remote-port turned off:

   bedrock:
     address: 0.0.0.0
     port: <PORT>
     clone-remote-port: false

   Replace <PORT> with the port number from the Network tab, without the angle brackets, for example 27015.

4. Save the file.

Setting up Floodgate#

1. In plugins/Geyser-Spigot/config.yml, find the java section and set auth-type:

   java:
     auth-type: floodgate

   In older Geyser versions the section is called remote instead of java. The setting is the same.

2. In the Server properties tab, in the Players group, turn off Require signed chat (enforce-secure-profile=false). Bedrock doesn't support chat signing, and Bedrock players wouldn't be able to chat otherwise.

3. Click Save and restart.

The most important options in Geyser's config.yml#

Floodgate: config.yml#

The plugins/floodgate/config.yml file:

Joining from Bedrock#

Bedrock players enter the address and the port separately (Bedrock doesn't use SRV records).

In the game: Play › the Servers tab › Add Server, fill in the fields and click Save. More about addresses and domains in the guide Server address and domain.

Consoles (Xbox, PlayStation, Switch)#

Consoles only allow connections to selected servers. Players get to other servers through unofficial workarounds, typically the BedrockConnect service (changing DNS in the console's network settings) or apps that make the server visible on the local network. The steps for each console are described in Geyser's documentation on the Using Geyser with Consoles (opens in a new window) page. We don't run these services and can't guarantee they work.

Whitelist and permissions for Bedrock players#

• Whitelist: use Floodgate's fwhitelist command without the prefix:

  fwhitelist add Steve123
  fwhitelist remove Steve123

  • fwhitelist add – adds a Bedrock player to the whitelist (to whitelist.json).
  • Steve123 – the player's Xbox name without the leading dot.

  The regular whitelist add doesn't work for Bedrock players, because their names aren't in the Java account database.

• Commands targeting a player (teleport, ban) use the name including the prefix, for example tp .Steve123.

• LuckPerms: by default, LuckPerms rejects names with a dot. In plugins/LuckPerms/config.yml, set allow-invalid-usernames: true and restart the server (LuckPerms).

Geyser on a Velocity proxy#

On a network of servers behind a proxy, install Geyser and Floodgate only on the proxy. Bedrock players connect to the proxy's port, and the proxy sends them on to the servers.

1. On Velocity, install Geyser and Floodgate for Velocity (both from geysermc.org/download (opens in a new window)).
2. In Geyser's configuration on the proxy, set the port (option A or B as above) and auth-type: floodgate.
3. In velocity.toml, set force-key-authentication = false, otherwise Bedrock players won't be able to chat.
4. All servers behind the proxy must accept a Java client of the version Geyser supports – install ViaVersion on them if needed.

You only need Floodgate on the servers behind the proxy if plugins on those servers use its data. In that case, turn on send-floodgate-data: true in plugins/floodgate/config.yml on the proxy (the subfolder depends on the platform), install Floodgate on the backends and copy key.pem from the proxy to them. Details are in the guide A server network with Velocity.

Geyser on Fabric and NeoForge#

1. In the Mods tab › Browse, install Geyser (on Fabric, the required Fabric API is added automatically).
2. Install Floodgate (on Modrinth it's available for both Fabric and NeoForge).
3. Restart the server and set the port and auth-type as above. Geyser's configuration is in config/Geyser-Fabric/config.yml (on NeoForge, config/Geyser-NeoForge/config.yml).

Geyser as a mod only supports one Minecraft version, the newest supported one. You can't use it on an older modded server.

Verification#

1. After the restart, look for the line Started Geyser on … with your port in the console.

2. Run a reachability test in the console:

   geyser connectiontest <IP_ADDRESS> <PORT>

   • geyser connectiontest – checks whether Geyser can be reached from outside and suggests what's wrong if it can't.
   • <IP_ADDRESS> – the server's IP address from the Network tab.
   • <PORT> – the Bedrock port (option A: the game port, option B: your additional port).

3. Check the server with the Minecraft Status tool in Bedrock mode.

4. Join from Bedrock. Once you're in, the console shows a line saying the player with the prefix joined, and geyser list shows their name.

Troubleshooting#

Bedrock: Unable to connect to world#

The most common error. Go through these one by one:

• The player entered the wrong port. Option A: the game port, option B: the port from bedrock.port. Port 19132 doesn't work at StormHost.
• Geyser isn't running on the port you expect. Check the Started Geyser on … line in the console.
• Something else is running on the same UDP port (Query, voice chat). Switch to option B.
• Run geyser connectiontest (see Verification) and follow its advice.
• On a phone, try fully closing the game and opening it again.
• The Geyser documentation says ports below 10,000 sometimes cause trouble. If you can, pick a higher port.

Outdated Bedrock client! This server supports the following Bedrock versions: …#

The player has a different Bedrock version than Geyser supports. The player updates the game, or you update Geyser (in the Plugins tab › Check for updates; Floodgate uploaded by hand has to be updated by hand).

This server does not support Java Edition …, which is required for Geyser to connect.#

The server version differs from the version Geyser emulates. Install ViaVersion (and ViaBackwards for a newer server), or update Geyser.

This server requires a paid Java account.#

Geyser has auth-type: online, or Floodgate isn't running. Install Floodgate, set auth-type: floodgate and restart.

Please log into Xbox to join this server.#

The player isn't signed in to the game with a Microsoft account. Floodgate requires an Xbox account – the player signs in from the game settings.

Tried to log in as a Java Edition player! Is Floodgate set up correctly?#

Floodgate isn't running on the server or didn't load. Look for Floodgate errors in the console during startup and check that the plugins folder has the Spigot/Paper file.

javax.crypto.AEADBadTagException: Tag mismatch!#

Geyser and Floodgate are using different keys. Stop the server, delete the plugins/floodgate folder and any key file in Geyser's folder, then start the server – a new key is created.

Bedrock players can't chat#

enforce-secure-profile is turned on (on a Velocity proxy, force-key-authentication). Turn it off and restart.

A Bedrock player isn't on the whitelist#

Add them with fwhitelist add <NICK> without the dot, not with whitelist add.

Further reading#

• Geyser: setup on Paper/Spigot with a hosting provider (opens in a new window)
• Supported Geyser versions (opens in a new window)
• Fixing “Unable to Connect to World” (opens in a new window)
• Floodgate: setup (opens in a new window)
• Geyser and chat signing (opens in a new window)