The definitive 2026 technical guide to setting up GeyserMC and Floodgate for seamless Bedrock and Java crossplay. Covers the modern NetherNet WebRTC protocol shift, Pterodactyl dual port allocation, config.yml setup, and troubleshooting Terracotta & Guardian errors.
Running a multiplayer Minecraft server in 2026 requires catering to a fragmented player base. While PC purists continue to favor Minecraft Java Edition for its unmatched modding ecosystem, client customizability, and Paper/Purpur performance, the overwhelming majority of casual players, friends, and community members connect through Minecraft Bedrock Edition on smartphones (iOS and Android), consoles (PlayStation 5, Xbox Series X/S, Nintendo Switch), and Windows 10/11.
Historically, running a server meant choosing between two mutually exclusive worlds: you either built a Java server and locked out console and mobile friends, or you spun up a Bedrock Dedicated Server (BDS) and lost access to Spigot, Paper, Purpur plugins, WorldEdit, and custom anti-cheat engines.
GeyserMC and Floodgate bridge this divide permanently. Geyser acts as a real-time protocol translator, while Floodgate handles authentication without forcing Bedrock players to buy a separate Java Edition license.
However, over 90% of online crossplay guides written between 2021 and 2024 are now obsolete. The modern Minecraft Bedrock protocol has undergone a fundamental architectural shift from legacy RakNet UDP transport to NetherNet (WebRTC + TCP Signaling). Server owners following outdated tutorials frequently encounter connection timeouts, broken handshakes, or cryptic error codes like Terracotta and Guardian.
This guide provides the authoritative, 2026-tested blueprint for configuring Geyser and Floodgate on modern Minecraft servers (Paper, Purpur, Spigot) and Pterodactyl-based hosting panels.
Before diving into configuration files, it is vital to understand the technical division of labor between Geyser and Floodgate:
Minecraft Java and Minecraft Bedrock speak completely different network languages:
Geyser operates as a translator proxy. When a Bedrock player swings a sword, places a block, or opens an inventory, Geyser intercepts the Bedrock packet, translates it into an equivalent Java packet, and forwards it to the Java server engine. The Java server believes it is communicating with a standard Java client. In reverse, Geyser translates Java world chunks and entity movements back into Bedrock packets in real time.
Under standard conditions, an online-mode Java server demands cryptographic handshake verification against Mojang's session servers (sessionserver.mojang.com). Because Bedrock players log in using Microsoft Xbox Live gamertags rather than official Java accounts, the Java server rejects their connection with Invalid Session or Not authenticated with Minecraft.net.
Floodgate resolves this without creating security vulnerabilities:
. or *) to their Bedrock gamertag (e.g., .SteveGamer99) to prevent username collisions with existing Java accounts.Bedrock Client (iOS/Console/PC)
│
▼ [NetherNet: TCP Signaling + WebRTC UDP]
┌───────────────────────────────────────────────┐
│ GeyserMC Proxy │
│ (Translates Bedrock Packets -> Java Packets)│
└──────────────────────┬────────────────────────┘
│
▼ [Local TCP Loopback]
┌───────────────────────────────────────────────┐
│ Paper / Purpur Server Engine │
│ │ │
│ ▼ │
│ Floodgate Plugin │
│ (Validates Xbox XUID -> Custom UUID) │
└───────────────────────────────────────────────┘
[!NOTE] Combining Geyser and Floodgate allows mobile, console, and PC players to play together on a single server, share the same economy, fight together in dungeons, and build in the same survival world.
The single most common reason Geyser crossplay fails on game server hosting is port conflict and improper port allocation.
Minecraft Java Edition and Minecraft Bedrock Edition cannot share the exact same port on standard game hosting environments unless specialized, complex proxy setups (like BungeeCord or Velocity with multiplexing) are used.
25565 (or a custom 5-digit port like 25605 assigned by your hosting panel). Runs strictly on TCP.19132 (or a secondary allocated port like 25606). Must support both TCP (for HTTP signaling) and UDP (for WebRTC gameplay packets).If you host your server on a modern containerized game hosting panel like Pterodactyl (used by VisiHost and top game server providers):
stan-1.visihost.in:25605). This is the port your Java players use.25606). This will become your dedicated Bedrock port in config.yml.Understanding this section is what separates a working 2026 server from a broken one.
Until recently, Minecraft Bedrock relied almost exclusively on RakNet, a pure UDP-based network protocol originally developed by Jenkins Software. All older YouTube tutorials and 2022-2023 blog posts tell you to open a single UDP port and set Geyser's transport to RakNet.
In modern Bedrock releases (v1.21.60+ and onward into 2026), Mojang transitioned the core Bedrock multiplayer protocol to NetherNet. Modern Bedrock clients connecting to legacy RakNet endpoints suffer from:
NetherNet splits the client-server connection into two distinct operational phases:
Client Handshake Sequence:
Bedrock Client ───[ 1. HTTP Signaling (TCP) ]───► Geyser Port
Bedrock Client ◄──[ 2. ICE Negotiation (TCP) ]── Geyser Port
Bedrock Client ═══[ 3. WebRTC Media Stream (UDP) ]═══ Geyser Port
To support modern Bedrock clients without demanding multiple extra ports from your host, Geyser introduced unified NetherNet transport settings:
transport: nethernet: Instructs Geyser to use the modern NetherNet protocol engine.webrtc-port: 0: The most critical setting. Setting webrtc-port: 0 instructs Geyser to multiplex both TCP signaling and UDP WebRTC data onto the exact same port! Without this, you would need to configure and open two separate Bedrock ports.signaling.mode: builtin: Launches the local signaling HTTP daemon internally on your game node.Follow these steps sequentially to configure your crossplay server.
Ensure your server is running a modern Java server software (PaperMC or Purpur are strongly recommended for crossplay):
Upload all .jar files into your server's /plugins directory using the Pterodactyl File Manager or SFTP.
Restart your server once to let the plugins generate their default configuration folders, then stop the server completely before editing configuration files.
plugins/Geyser-Spigot/config.yml)Open plugins/Geyser-Spigot/config.yml in your editor. Locate the bedrock: and java: blocks and update them as follows:
yamlbedrock: # The local network interface to bind to. 0.0.0.0 binds to all container interfaces. address: 0.0.0.0 # Your SECONDARY port allocated in Pterodactyl (NOT your Java 25565 port!) port: 25606 # Golden 2026 rule: 0 instructs Geyser to share this port for both TCP signaling and WebRTC UDP webrtc-port: 0 # Modern NetherNet protocol transport transport: nethernet # MUST be false on containerized hosting (prevents Geyser from trying to steal Java's port) clone-remote-port: false # Maximum Bedrock player capacity (0 = match Java server max-players) max-players: 50 # Server list MOTD displayed on Bedrock client server menus motd1: "VisiHost Crossplay Server" motd2: "Java + Bedrock Supported" # Built-in NetherNet HTTP signaling configuration signaling: mode: builtin advertise-addresses: # Put your public server domain or node IP with your BEDROCK port - mc.visihost.in:25606 java: # The local IP of your Java server (typically 127.0.0.1 or localhost when running as a plugin) address: 127.0.0.1 port: 25605 # Instructs Geyser to authenticate Bedrock players through Floodgate auth-type: floodgate
[!WARNING]
In signaling.advertise-addresses, make sure you specify your publicly reachable hostname or IP and your Bedrock secondary port, NOT 0.0.0.0 and NOT your Java port.
server.propertiesNavigate back to your server root directory and open server.properties. Adjust the following two critical parameters:
online-mode=falsepropertiesonline-mode=false
online-mode remains true, Mojang's session servers will intercept Bedrock connection attempts and reject them because Bedrock players do not hold Mojang Java session tokens.enforce-secure-profile=false (CRITICAL)propertiesenforce-secure-profile=false
enforce-secure-profile is set to true, Bedrock players will be instantly kicked from the server with Missing or invalid chat signature the second they send a chat message or execute a slash command.Save the file and start your server.
When crossplay fails, Minecraft Bedrock displays obscure, stylized error codenames. Use this troubleshooting matrix to decode and fix them instantly:
InitialConnection-149Connection timed out with error tag InitialConnection-149 or codename Terracotta.25565) instead of the Bedrock port, or Geyser failed to bind to its assigned port due to a port conflict.25606), not the default Java port.Started Geyser on 0.0.0.0:25606. If you see Address already in use, change your port in config.yml.InitialConnection-46 (juice: Lost connectivity)Locating Server... or Loading Terrain, and then abruptly disconnects with InitialConnection-46 (Guardian) and juice: Lost connectivity in console.plugins/Geyser-Spigot/config.yml, ensure webrtc-port: 0 is set.ufw allow <port>/udp.No network path to this server was found.config.yml, the advertise-addresses field under signaling: contains an unreachable IP, an incorrect hostname, or was copy-pasted from another server node.config.yml.signaling.advertise-addresses.- play.myserver.com:25606).FAILED TO BIND TO PORT! Exception: Address already in use.clone-remote-port: true or manually typed your Java server port into Geyser's port: field. Geyser attempted to bind to the same socket Java was already listening on.clone-remote-port: false.port: is set to your allocated secondary port.Distribute this connection cheat sheet to your player community so players on each platform know exactly how to connect:
| Client Platform | Editions Included | Address / IP | Port to Enter | Required Account |
|---|---|---|---|---|
| Java Edition | PC (Windows, macOS, Linux) | yourdomain.com | Primary Port (e.g. 25565 or default) | Official Minecraft Java Edition License |
| Bedrock Mobile | Android & iOS (iPhone/iPad) | yourdomain.com | Secondary Port (e.g. 25606 or 19132) | Standard Microsoft / Xbox Live Account |
| Bedrock Windows | Windows 10 & 11 Bedrock App | yourdomain.com | Secondary Port (e.g. 25606 or 19132) | Standard Microsoft / Xbox Live Account |
| Bedrock Consoles | Xbox One/Series, PS4/PS5, Switch | yourdomain.com | Secondary Port (via BedrockTogether or DNS) | Xbox Live / PSN / Nintendo Account |
[!TIP]
Connecting from Consoles (PlayStation, Xbox, Switch):
Console editions of Minecraft Bedrock do not feature a "Direct Add Server" button by default due to platform restrictions. Players on PlayStation, Xbox, and Nintendo Switch can connect to your server using free mobile relay utilities like BedrockTogether (available on iOS and Android) or by changing their console's primary DNS settings to point to a public server list resolver.
Translating block states, animations, and entity physics between Bedrock and Java is computationally intensive. When 10 Bedrock players join alongside 10 Java players, Geyser consumes CPU cycles on the host server to handle packet serialization and coordinate transformations.
To ensure your crossplay server maintains a locked 20.0 TPS with zero tick lag:
Looking for high-performance, low-latency hosting engineered specifically for Minecraft Java & Bedrock crossplay?
Launch your high-performance Minecraft or VPS server in India with 20.0 steady TPS, NVMe SSD storage, and instant UPI activation.
Sub-20ms Mumbai ping, unmetered NVMe, Pterodactyl panel & Geyser crossplay starting at ₹44/mo.