Bedrock Players Cannot Join Your Minecraft Server

If Bedrock players cannot join your Minecraft Java server on PlayNHost, open the Bedrock crossplay card on Ports & Network first. If it says Bedrock players cannot join until crossplay is updated, click Update crossplay, restart the server and give players the new port. Otherwise the cause is usually a missing restart or the wrong port.

Check the card first

Open your server in the panel and click Ports & Network in the left menu.
Look at Bedrock crossplay:
- The warning Bedrock players cannot join until crossplay is updated: see the next section.
- Enabled and Bedrock players connect to with an address and port: crossplay is set up. Compare that address and port with what your players typed.
- Enable crossplay: it is not on yet. See How to let Bedrock players join your Java server with Geyser.
- A sentence instead of a button: your server cannot bridge right now. See "The card says crossplay cannot run here" below.

The card says crossplay must be updated

Bedrock 26.60, released on 27 October 2026, connects with NetherNet only. GeyserMC's NetherNet guide says Bedrock players cannot join servers that have not made the switch. Older crossplay setups on PlayNHost used the older method, by default on your main port, and NetherNet needs the TCP side of the Bedrock port, which Java holds on the main port. The card then says Minecraft Bedrock 26.60 changed how players connect. Updating gives Bedrock a port of its own and a current Geyser. After a restart, Bedrock players use the new port shown here.

Click Update crossplay. You need permission to edit files and to add ports.
Restart the server.
If the port under Bedrock players connect to changed, send the new port to your Bedrock players.
Each player changes the port in the server they saved in Minecraft, or adds the server again with the new port.

When Bedrock was on the main port, the update takes one port of your plan. It keeps your other Geyser settings and saves the old Geyser settings once as config.yml.pre-nethernet in Geyser's folder.

If Update crossplay is refused

Geyser can only be updated on this server type while the server is stopped. Stop the server, then press Update crossplay again. This happens on Fabric, NeoForge and proxies. Stop the server, click Update crossplay, then start it.
Bedrock needs a port of its own and none could be added: followed by This server already uses all <n> ports its plan includes, so a Bedrock port could not be added. Remove a port you no longer use under All ports, then click Update crossplay again. See How to add a port to your Minecraft server.
Bedrock's port and Geyser's settings were updated, but the new Geyser could not be downloaded right now. Press Update crossplay again in a few minutes. Do that, then restart.

The card says crossplay cannot run here

This server type cannot host the Geyser bridge. Crossplay works on Paper, Purpur, Spigot, Folia, Magma, Ketting, Fabric, NeoForge, Velocity, BungeeCord and Waterfall. See How to change your Minecraft version or server type.
Bedrock crossplay is not ready for Minecraft <version> yet. Geyser has no release for your version yet. Choose the version the card names, or wait and turn it on later.
Bedrock crossplay needs Minecraft <version>, and this server runs <version>. Your version is older than Geyser supports. Switch to the version the card names.
Geyser needs Java 21 or newer, and this server runs Java <n> Your Minecraft version needs an older Java than Geyser can run on. The card says which versions work.

Geyser did not start

The card says Geyser did not start on the last restart. The console shows why, in the lines that mention Geyser.

Open the Console and look for lines with Geyser in them.
A healthy start has a line that says Built-in signaling started on followed by the Bedrock port.
Built-in signaling cannot use port <port> because the Java server already uses it means Bedrock is still on your main port. Click Update crossplay on the card and restart.
Built-in signaling will not start! Could not load or create this server's identity file means Geyser's identity.pem cannot be read. Open a ticket with that line: do not delete the file, because a new identity makes every player confirm your server again.
Restart the server once more after any change.

If the lines do not make sense to you, open a ticket with the last Console lines that mention Geyser. See How to open a support ticket.

The game says it cannot connect

The server was not restarted after crossplay was turned on or updated. Restart it, wait until it is online, and try again.
Wrong port. Bedrock players type the address and the port in separate boxes. They need the port under Bedrock players connect to, which is a different port from the Java port once crossplay is up to date. A server saved in Minecraft before an update still has the old port.
The server is stopped or still starting. Wait until the Console shows it has started.
The player said no to the trust question. The first time a player joins, Minecraft asks them to trust your server, and Mojang's guide for servers says the join stops if they refuse. They try again and accept. The card says this is expected: The first time they join, Minecraft asks them to trust this server. That is expected.
The player's game is too old. On 1 November 2026, Geyser's supported versions page lists Bedrock 26.40 to 26.60. The player updates Minecraft.

Outdated client or Outdated server

Geyser joins your server as a Java player on one Java version, the one named on Geyser's supported versions page. When your server runs another version, the server refuses it and the Bedrock player sees the reason. Geyser's own list of common issues gives these fixes:

Outdated server! I'm still on <version>: your server runs an older Minecraft than the version Geyser speaks. On Paper, Purpur, Spigot and Folia the panel installs ViaVersion when it sets up or updates crossplay on an older version, and the card says ViaVersion could not be added if that fails. Check that ViaVersion is listed under Modding, Plugins, Installed. If it is not, install it and restart: see How to let older and newer Minecraft versions join with ViaVersion.
Outdated client! Please use <version>: your server runs a newer Minecraft than your copy of Geyser knows. Update Geyser: open Modding, then Plugins (or Mods on Fabric and NeoForge), then Installed. If Geyser shows Update, click it and restart the server. If it does not, open a ticket.

Geyser also supports only a range of Bedrock versions at a time. A brand new Bedrock release works once Geyser supports it and your server runs that Geyser.

Can my friends join? says the Bedrock port answers

Can my friends join? on Overview tests the Bedrock port from outside. If it says Bedrock players cannot join until crossplay is updated, follow the steps above. If it says Bedrock players can reach your server, your Bedrock port answers the way an updated Bedrock game connects: look at the other causes on this page. See How to find out why friends cannot join your Minecraft server.

The player gets in but is refused

You are not white-listed on this server: the whitelist is on. Add Bedrock players with fwhitelist add <name> in the Console. See Players see "You are not white-listed on this server".
In other commands, such as kick or ban, use the name as the game shows it, with Floodgate's prefix (by default a dot, for example .Steve).

Console players

Xbox, PlayStation and Switch players cannot add a server by address. They need console joining, which goes through crossplay's Bedrock port, so update crossplay first if the card asks. See How to let console players join your Minecraft server.

Bedrock players cannot join your Minecraft server