Geyser NetherNet Migration for Bedrock 26.60: Ports and Setup

Direct answer

Do this before the planned October 27, 2026 Bedrock 26.60 release. GeyserMC says Bedrock clients will require NetherNet rather than RakNet. Use a current Geyser build (support began in build 1237), enable NetherNet explicitly, and ensure the necessary TCP signaling and UDP gameplay traffic can reach the server. Existing UDP-only firewall rules are not enough for built-in signaling.

Basic self-hosted configuration

For a server with a separate Geyser Bedrock port and available TCP/UDP port 19132, the official setup guide shows this basic bedrock section. Keep the rest of your generated configuration intact:

bedrock:
  port: 19132
  transport: nethernet

For this arrangement, open TCP and UDP for the selected Geyser port. A Java server already listening on that TCP port is a conflict: use a separate Geyser port or an external signaling option recommended by GeyserMC.

Need to support older Bedrock versions?

If you must serve RakNet clients temporarily, Geyser’s official guide supports both transport with a separate UDP WebRTC port:

bedrock:
  port: 19132
  webrtc-port: 19133
  transport: both

Allocate and expose UDP 19133 as well as the TCP/UDP services needed on 19132. Confirm your host permits these ports; example port numbers are not universal.

Hosting provider or shared Java port

Some panels bind Geyser to the same numeric port as the Java server, or cannot assign an extra TCP port. In those cases, consult the official host-specific setup instructions for external signaling / NXS. Do not copy the self-hosted example onto a port the proxy or Java server already uses.

Test before clients update

Back up the existing Geyser configuration and note the original transport and port assignments.
Update Geyser, change only the relevant settings, and restart the Geyser instance.
Look for port-binding or signaling errors in the console.
Join from a supported Bedrock client (26.40+ for early NetherNet testing; consult the setup guide for current version behavior). Test an external network, not just localhost.
Verify MOTD, login, world join and rejoin, including behind Velocity if applicable. If the Bedrock client shows a first-use trust prompt, HTTP signaling may explain it; consider HTTPS per official guidance.

Troubleshooting and rollback

“Unable to connect”: check TCP signaling, UDP gameplay, host allocation, firewall and NAT mapping separately.
“Port already in use”: give the signaling listener a free TCP port or follow the Geyser external signaling documentation.
clone-remote-port: review the official caveat before migration; the shared Java port may prevent built-in signaling.
Rollback before 26.60: restore the previous tested configuration if necessary. After RakNet is retired, rolling back to RakNet will not restore connections from new clients.

Bedrock Dedicated Server and other software

The transport requirement originates with Bedrock clients, not Paper itself. These instructions apply specifically to Geyser. Native Bedrock server implementations require their own upstream compatibility and setup instructions; do not paste Geyser configuration keys into other software.

Official references

Official sources for version-sensitive details. Check the newest release notes before changing a production server.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.