Minecraft Bedrock 26.60 changes how players connect to third-party servers. Bedrock is moving away from the older RakNet connection system to NetherNet, which means older Geyser setups can fail when Bedrock players try to join your Java server. This guide explains the issue, the ports you need, and how to configure Geyser and Floodgate on Paper or Spigot.

Common errors: Terracotta and InitialConnection-149. These show up on Android, iOS and console clients, and are also tracked as MCPE-244019.

1. Understand the Issue

With Bedrock 26.60, players use TCP signaling to discover the server and UDP through WebRTC for gameplay. Older Geyser configurations that only expose the previous UDP (RakNet) port no longer work correctly, so Bedrock players cannot join.

Symptoms:
• Terracotta connection error
• InitialConnection-149
• Bedrock players unable to join your Java server through Geyser

2. Check the Requirements

You will need:
• Minecraft Bedrock Edition 26.60 or newer
• Geyser build 1237 or newer (latest build recommended)
• A Paper or Spigot server with Geyser-Spigot installed
• Floodgate, if Bedrock players should join without a Java Edition account
• Two additional network ports for Geyser, on top of your Java port

3. Know the Required Ports

In this setup, NetherNet needs separate ports for signaling and gameplay. Your existing Java server port stays unchanged.

Java Server — Port 25513 — TCP — Java Edition players join here.

Geyser Signaling — Port 28273 — TCP — Bedrock clients first contact the server here.

NetherNet WebRTC — Port 25573 — UDP — Used for the actual Bedrock gameplay connection.

These are example numbers. Your actual ports depend on what is allocated to your server. The Java port must be separate from both Geyser ports, and all three must be accessible using their own protocols.

Signaling (TCP): handles the first contact from the Bedrock client and sets up the NetherNet connection. Example: example.azelhost.in:28273

WebRTC (UDP): carries gameplay. Players never type this port into Minecraft, since Geyser advertises the public address during signaling. Example: example.azelhost.in:25573

AzelHost customers: The required ports are already opened on AzelHost infrastructure. You do not need to configure firewall rules or open ports manually.

4. Update Geyser

NetherNet support is available in Geyser build 1237 and newer. Download the latest Geyser-Spigot build from the GeyserMC Downloads page and replace the existing Geyser-Spigot.jar in your plugins folder.

Keep your existing Geyser configuration and Floodgate files as they are.

5. Configure Geyser

Open plugins/Geyser-Spigot/config.yml from the Files tab in the AzelHost Panel, find the bedrock section and set it up like this:

plugins/Geyser-Spigot/config.yml
bedrock:
  address: 0.0.0.0
  port: 28273
  webrtc-port: 25573
  transport: nethernet
  clone-remote-port: false
  signaling:
    mode: hybrid
    advertise-addresses:
      - "example.azelhost.in:25573"

Replace the example domain and ports with the values assigned to your server.

What each setting does

address — Listen address for Geyser. Keep it as 0.0.0.0.
port — TCP signaling port.
webrtc-port — UDP WebRTC port.
transport — Enables NetherNet transport.
clone-remote-port — Keep false for this separate-port setup.
signaling.mode — Sets the signaling mode.
advertise-addresses — The public WebRTC address that Bedrock clients are told to use.
Important: Keep the YAML indentation exactly as shown, and keep advertise-addresses inside the signaling section. It must point to the publicly reachable WebRTC address and port. Never use a private container IP or the node's IP.

6. Configure Floodgate

If you use Floodgate authentication, find the java section in the same file and set the auth type:

config.yml
java:
  auth-type: floodgate

Then make sure Geyser can read the Floodgate key file:

config.yml
advanced:
  floodgate-key-file: key.pem
Note: Do not replace or regenerate your existing key.pem unless you have to. If you are not using Floodgate, keep the authentication method that matches your current Geyser setup.

7. Apply the Configuration

Save config.yml and restart the server. Then check the console and confirm that Geyser started without errors. Look out for port binding errors or messages saying the signaling address is invalid.

8. Connect from Bedrock Edition

Add the server in Minecraft Bedrock Edition using the signaling port, not the WebRTC port:

Server Name: Your Server Name
Server Address: example.azelhost.in
Server Port: 28273
Do not ask players to enter 25573 as the server port. Geyser advertises the WebRTC port automatically.

9. Troubleshooting

Terracotta or InitialConnection-149

• Confirm the client is on Minecraft Bedrock 26.60 or newer.
• Confirm Geyser uses transport: nethernet.
• Verify that TCP signaling and UDP WebRTC ports are both reachable.
• Check that advertise-addresses has the correct public address.

Geyser cannot start signaling

Check whether another service is already using the signaling port. The Geyser signaling port must be separate from the Java server's TCP port.

Loopback address error

Make sure your config contains the following, and never use 127.0.0.1 as the external listening address:

config.yml
address: 0.0.0.0

Still unable to connect?

Run this in the server console to generate a Geyser diagnostic report:

Server Console
> geyser dump

Share the report and the relevant Geyser console errors with your hosting provider.

Note: A port showing up in a panel does not prove that the required protocol works. Make sure TCP and UDP are both actually accessible. If you are on another hosting provider, ask them to confirm this.

10. AzelHost Support

If your server is hosted with AzelHost, you do not need to troubleshoot port allocation or networking yourself. Create a support ticket and request:

Geyser NetherNet Setup for Bedrock 26.60

Our team will configure the TCP signaling port, the UDP WebRTC port, the Geyser NetherNet settings, the public advertised address and Floodgate where applicable. Your existing Java server address and port will remain unchanged.