The Bedrock port on a Geyser server, and how players use it

Bedrock players connect on a different port to Java players, and using the wrong one is the single most common crossplay mistake. Here is where to find yours and exactly what to tell your players.

6 min read · Updated Oct 21, 2026 · By GuavaHost Team

If a Bedrock player says "Unable to connect to world" and a Java player on the same server is standing in your spawn right now, you are almost certainly reading the right guide.

Why Bedrock needs a port of its own

Java Minecraft talks over TCP, the careful, ordered way computers send data. Bedrock talks over UDP, the fast, fire-and-forget way, using a protocol called RakNet. They are two different conversations in two different languages, and a single listener cannot do both.

So a crossplay server listens twice:

• the Java port, over TCP, which is the address at the top of your server page,
• the Bedrock port, over UDP, which Geyser opens, and which Bedrock players use instead.

Give a Bedrock player the Java port and they get nothing, because nothing is listening for UDP there. It does not fail with a helpful message, it just times out. TCP versus UDP game server ports goes into why the two behave differently.

Two useful facts while you are here. Bedrock's default port is 19132, which the game pre-fills in the Port field, and it is almost certainly not your port. And there is nothing to forward: GuavaHost opens your server's ports for UDP as well as TCP.

Find your Bedrock port

1. Sign in at customer.guavahost.com, open My servers and click Manage on your server.
2. Open the Overview tab and find the Ports & network card.
3. Server address at the top is the Java one. The Bedrock port is listed under Other ports, each with its own copy button.
4. If a port carries a label, use the one labelled for Geyser or Bedrock.

Startup settings on the Settings tab may also show the same number as a Geyser port setting. Both are showing you one real port, so if they disagree you have misread one. Finding your server IP and port covers the ports card in more detail, including managing ports yourself.

On GuavaHost's Geyser plan, the startup command hands the Bedrock port straight to Geyser, which overrides the port line in Geyser's own config. That is why editing that line does nothing here. Leave the port settings where they are.

If your server does not have a second port yet

This happens when you have added Geyser to a plain Java server rather than ordering a crossplay one. Geyser has nowhere to listen, so no Bedrock player can reach it:

1. On the Ports & network card, click Manage to open the Ports & network page.
2. Click Add a port and either let us pick the next free one or choose from the list of free ports on your machine.
3. Add a note on it, something like "Bedrock", so you know what it is for later.
4. If there is a Geyser or Bedrock entry under Game ports, click Choose a port and point it at the port you just added. If there is not, set the port in Geyser's config as below.
5. Restart the server. Port changes apply the next time it starts.

The port has to be one the panel has actually allocated to your server. Picking 19132 because it is the Bedrock default will not work unless that happens to be one of yours.

The Geyser config fields

Geyser's config lives at plugins/Geyser-Spigot/config.yml, which you open on the Files tab. The section that matters is the one at the top:

bedrock:
  address: 0.0.0.0
  port: 19132
  clone-remote-port: false
  server-name: Geyser

What each one is doing:

• address is which network interface Geyser listens on. 0.0.0.0 means all of them, which is what you want. Changing it is a reliable way to make your server unreachable.
• port is the UDP port Geyser listens on. On the Geyser plan the startup command sets this and the file is ignored. If you added Geyser yourself, set this to the port you allocated.
• clone-remote-port tells Geyser to reuse the Java port number instead. Leave it false, because your Bedrock port is a separate allocation.
• server-name is cosmetic, the name shown in some Bedrock listings.

Current Geyser versions also have a broadcast port setting, for the unusual case where players reach Geyser on a different port from the one it binds. Leave it alone on a normal setup.

After any change, press Save and restart the server. Then run geyser version in the Console to confirm Geyser came back up cleanly.

Exactly what a Bedrock player types

This is the part worth copying into your Discord, because it is where it goes wrong:

1. Open Minecraft, tap Play, then the Servers tab.
2. Scroll to the bottom and tap Add Server.
3. Server Name: anything, it is just a label for them.
4. Server Address: the IP only. No colon, no port, nothing after the last number. For example 123.45.67.89.
5. Port: the Bedrock port from Other ports. Delete the 19132 the game filled in first.
6. Save, then tap the server in the list to join.

The two mistakes to warn people about: pasting the whole IP:port into the address field, which wants the IP alone, and leaving 19132 in the Port field without noticing it was pre-filled. Join your Minecraft Bedrock server has the same steps with more detail.

Send your players one line with the two values spelled out separately, rather than an address with a colon in it.

Console players

Xbox, PlayStation and Switch have no Add Server button, so console players cannot type an address at all, whatever port you give them. They need a free workaround, which Play Bedrock on console covers. That is a limitation of those editions, not of your server or your ports.

When it still will not connect

Work through these in order:

• Check the server is Online. The status next to your server's name has to read Online, not Starting.
• Check Geyser actually started. Open the Console and look for Geyser's startup lines. An error there, especially about binding the port, explains everything else.
• Re-read the port. Copy it from Other ports rather than typing it from memory, and have the player re-enter it instead of trusting their saved server entry.
• Try another device on another network. If a phone on mobile data connects and the one at home does not, the problem is at that player's end.
• Confirm Floodgate is loaded. If Bedrock players reach the server but are asked to sign in to a Java account, the port is fine and your auth-type is not. Set up Geyser and Floodgate for crossplay covers that setting.

A bind error on the Bedrock port usually means one of two things: two Geyser jars in plugins both trying to listen, or a port that is not allocated to this server.

Common questions

Why can my Java friends join but not my Bedrock friends?

Because they are not connecting to the same place. Java players use the address at the top of your server page, and Bedrock players need the separate Bedrock port listed under Other ports, entered in the game's own Port field. Nothing is wrong with your server.

Do I have to use port 19132?

No, and on a hosted server you almost certainly cannot. 19132 is just the number Minecraft pre-fills, and your Bedrock port is whichever one the panel allocated to your server. Players have to clear the default and type yours.

Should Bedrock players put the port in the address field?

No. The Server Address field takes the IP on its own, with no colon and no port after it, and the port goes in the separate Port field below it. Pasting the full address with a colon into the first field is one of the two most common reasons a Bedrock player cannot connect.

Do I need to open or forward the Bedrock port myself?

No. GuavaHost opens the ports assigned to your server, including for UDP, so there is nothing to forward and no firewall rule for you to add. If you add a new port in the panel, it is open once the server restarts.

Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.

• geyser
• crossplay
• bedrock
• port
• udp
• minecraft

Host a Minecraft Geyser server From $3.99/mo, with instant setup and DDoS protection.

Still need help? Our team is online 24/7 to answer questions.

Contact support