Loading...
Set up Geyser and Floodgate on a Paper Minecraft server. Check Java requirements, allocated ports, authentication, console limits, and connection errors.
Geyser lets supported Bedrock clients join a Java Edition server; Floodgate lets authenticated Bedrock players join without owning Java Edition. For a single Paper server, install the Spigot builds of both plugins, run Java 21 or later as required by your server software, configure an allocated Bedrock endpoint and Floodgate authentication, then test Java and Bedrock connections separately. Windows/mobile clients can add an external server directly; consoles need an additional connection method.
Use this guide for a single Paper server, with Geyser and Floodgate installed on the same instance. Geyser translates Bedrock connections to Java; Floodgate handles Bedrock authentication without requiring a Java Edition license. Neither plugin converts the world to Bedrock format or makes every Java feature compatible.
This guide was checked against the official documentation on November 20, 2026. It is not a claim of a completed GaleniusNodes server or console playtest. Exact panel controls, port allocations and transport support must be confirmed for your service before making changes.
Current Geyser-Spigot needs Java 21 or later and supports Paper/Spigot server versions 1.20.5 and above. Your server build may need a newer Java runtime. Check the startup log or runtime selection in the panel; a Java version installed on your own computer does not change the hosted server runtime.
| Your setup | What to install | Important boundary |
|---|---|---|
| One Paper server | Geyser-Spigot and Floodgate-Spigot in plugins | This guide's configuration scope |
| Velocity or BungeeCord network | The matching proxy builds | Install Geyser on the proxy and follow the official Floodgate/forwarding guide; do not copy single-server authentication settings |
| Fabric or NeoForge | The matching loader builds and dependencies | Not Spigot JARs; check the supported-version page and client-mod limitations |
| Java server below 1.20.5 or a separate bridge | A supported proxy, ViaProxy or Standalone deployment | Current Geyser-Spigot cannot run directly on these older servers |
Geyser emulates a particular Java client version and supports a changing range of Bedrock versions. If your supported Paper server is older than that Java protocol, check whether ViaVersion is needed. Use the official supported-versions page linked below rather than assuming an old compatibility list still applies.
Ask support which address and port are allocated for Geyser, which transports are supported, and whether signaling is provided. A Java address that works over TCP does not prove Bedrock gameplay can reach it. Do not choose a random unused-looking port or assume 19132 is included.
| Connection type | Networking to confirm | What players use |
|---|---|---|
| NetherNet with built-in signaling | TCP for signaling and UDP for gameplay on the allocated port, unless configured separately | The host-confirmed public address and signaling port |
| NetherNet with external signaling | The signaling service plus reachable UDP/WebRTC networking required by that setup | The address and port reported by the service/Geyser, which may differ from the Java address |
| NetherNet and RakNet together | Separate UDP ports as specified by Geyser, including webrtc-port | The endpoint appropriate to the client and configured transport |
| Older RakNet-only build | Its allocated UDP listener | The Bedrock address and port; do not apply this older UDP-only assumption to current NetherNet |
On panel hosting, an allocation must be assigned to your server, not merely opened somewhere on the node. Docker must publish the required protocols as well. On a VPS, check the provider firewall, operating-system firewall and any NAT rules. Do not disable the firewall globally. The official networking guide covers these layers.
Built-in NetherNet signaling cannot share the Java server's TCP listener. If only the Java port is available, ask support about a supported external-signaling setup instead of binding a second TCP service to the same port. We have not confirmed a GaleniusNodes-wide signaling or extra-port entitlement.
Open plugins/Geyser-Spigot/config.yml. Edit the generated file for your installed build; do not replace it with an entire configuration from an old tutorial. The fragment below is for current builds using NetherNet and a separate allocated TCP/UDP port, with both plugins on the same Paper server.
# Example only: replace 19132 with your assigned TCP/UDP port.
# Do not create duplicate bedrock or java sections.
bedrock:
address: 0.0.0.0
port: 19132
clone-remote-port: false
transport: nethernet
java:
auth-type: floodgate0.0.0.0 is a listening address, not the address players enter. Keep other generated settings unless the official platform guide or your host tells you to change them. Current builds use a java section; older files may call it remote. Update through the supported migration path rather than adding both sections. The integrated plugin normally discovers its local Java server; do not hardcode 127.0.0.1:25565 for an unrelated proxy or container.
Floodgate on the same instance normally supplies its key automatically. Keep key.pem, signaling tokens and authentication caches private. Without Floodgate, use the generated online-authentication option and require Java account authentication; do not switch to offline authentication to bypass a login problem.
online-mode=trueKeep Java authentication enabled for this single-server setup. Proxy backends have different forwarding requirements and must be protected from direct public connections. A blanket online-mode=false change is not a safe crossplay fix.
Save, start the server and read the startup log for listener, signaling or Floodgate errors. A normal restart is preferable to a plugin hot reload. For trusted first connections, review the official HTTPS for NetherNet instructions with your host; browser-website HTTPS does not automatically configure Geyser's signaling listener.
Consoles cannot join arbitrary third-party servers out of the box. The Windows/mobile Add Server instructions are not universal console instructions. Geyser's official console guide describes BedrockConnect, MCXboxBroadcast and LAN-emulation helper apps; follow the method appropriate to the specific console and network.
| Symptom | Check first | Next action |
|---|---|---|
| Plugin fails to load / unsupported Java | The server's Java runtime and exact plugin/platform build | Use at least Java 21 and meet Paper's own requirement; read the first startup error |
| Address already in use | Duplicate listener, Java TCP collision or another plugin using the port | Use the assigned allocation and a supported signaling topology; do not keep changing ports at random |
| Unable to connect to world / timeout | Correct Bedrock endpoint, assigned ports, transport and client version | Check TCP signaling and UDP gameplay separately, plus panel/Docker/firewall layers; test from another network |
| Server appears but joining fails | A reachable listing does not prove UDP gameplay works | Check WebRTC/UDP reachability, the startup log and any separate webrtc-port allocation |
| Java-account or authentication error | Floodgate actually loaded and Geyser auth-type matches | Check the generated configuration and key discovery; do not disable online-mode |
| Outdated client/server | Installed Geyser version and the official supported-protocol list | Back up and update compatible builds; check ViaVersion requirements for older Java servers |
| Only consoles fail | The chosen console connection method and account/network restrictions | Test Windows/mobile first, then follow the official console-specific method |
| Whitelist, permissions or missing player data | Floodgate username/UUID and account-linking configuration | Back up player data before changing prefixes or authentication; review the Floodgate documentation |
geyser version
geyser listRecord the plugin/server/runtime versions, client platform, configured transport and the first relevant error when asking for help. geyser dump can provide diagnostic data, but review it for sensitive details and share it privately only when needed. Do not publish keys, tokens, account credentials or full private connection details.
Bedrock clients may update automatically. Recheck the official version matrix before changing Geyser, Floodgate, Paper or ViaVersion; back up first and verify both editions afterward. Crossplay does not guarantee Java client-mod support or identical mechanics. If a change fails, stop the server and restore the matched plugin/configuration backup; do not downgrade a world without a compatible backup.
Your setup is ready only after both editions can join the intended world, the required gameplay works, authentication stays enabled and connections still work after a restart. Verify consoles separately if your community needs them.
Current Geyser builds require Java 21 or later. The Minecraft server or proxy may require a newer runtime, so check both requirements. Java 17 is not sufficient for current Geyser builds.
Not when Floodgate is installed and Geyser uses Floodgate authentication. Players still need a legitimate Bedrock account and multiplayer access. Without Floodgate, Geyser's online authentication requires a Java Edition account.
No. 19132 is a default, not a guaranteed hosting allocation. Use the port assigned by your host. Current NetherNet setups with built-in signaling need TCP for signaling and UDP for gameplay; external signaling and mixed NetherNet/RakNet configurations have different requirements. Check the setup instructions for your installed build.
Consoles cannot join arbitrary third-party servers out of the box. Geyser documents additional methods such as BedrockConnect, MCXboxBroadcast and LAN helper apps. Compatibility, account settings and platform restrictions vary; a successful Windows/mobile test does not guarantee console access.
No, not for the single-server Paper setup in this guide. Keep online-mode=true and select Floodgate authentication inside Geyser. Proxy networks need their own secured forwarding configuration; never disable authentication on a publicly reachable backend as a shortcut.
No. Geyser translates supported protocol behavior; it does not install Java client mods on Bedrock. Mods requiring a Java client and some custom mechanics or interfaces will not work. Review Geyser's limitations before promising crossplay for a modpack.
How to Install Plugins on a Minecraft Server
Install Minecraft plugins with the GaleniusNodes plugin installer or manually on Paper, Purpur, and Spigot. Includes compatibility checks and troubleshooting.
Read guideHow to Join a Minecraft Server
Learn how to join a Minecraft server on Java and Bedrock editions using an IP address.
Read guideHow to Use SFTP on a Minecraft Server
Connect to your Minecraft server with SFTP and FileZilla. Learn where to find GaleniusNodes credentials, upload worlds and server files, and fix connection errors.
Read guideInclude your Minecraft version, server software or loader, plugin or mod URL, and the first console error.