MarvinMC This guide covers a standalone Paper/Spigot-compatible server. For BungeeCord or Velocity, install the matching Geyser build on the proxy and follow the official proxy setup instead.
Step by step
- Back up your server. Check the linked Geyser version matrix for your Minecraft version and Java runtime before installing. Older backends may need ViaVersion or a proxy; a current Geyser plugin does not run on every old server.
- Install Geyser-Spigot.jar through the compatible plugin browser, if listed, or upload it to /server/plugins. Do not replace server.jar. Restart once to generate the configuration.
- In Overview, choose an unused Query / plugin port or an assigned additional port. Do not assume the default 19132 belongs to your server. Keep the main Java port unchanged and reserve a different port for Voice Chat.
- Stop the server and open /server/plugins/Geyser-Spigot/config.yml in Files. Set port inside bedrock to your chosen port. Keep a wildcard listener address, such as 0.0.0.0, rather than binding to the public node IP.
- Match transport to the installed Geyser release. NetherNet uses TCP and UDP; transport: both also needs a different allocated UDP port in webrtc-port. The hosting maps allocated ports for both protocols. Follow the linked setup for transport and HTTPS signaling rather than copying an outdated UDP-only tutorial.
- For Bedrock players without a Java license, also install the matching Floodgate plugin. After it has generated its files, set the existing auth-type option in the Geyser configuration to floodgate. Otherwise keep the authentication appropriate to your setup.
- Save and restart. Check the console for successful plugin startup, version errors or a port already in use. Connect in Bedrock using the public IP from Overview and the Geyser port, not the Java port.
Check the result
Test both a Java and a Bedrock connection. If Query already uses the chosen port, disable unused Query or move it to another assigned port. If every port is occupied, use Additional ports where your plan offers them.
Important
Keep account authentication enabled on a standalone Java server. Do not share Floodgate key.pem or archives containing it. A Java join subdomain does not automatically configure Bedrock discovery or HTTPS signaling. Console platforms can have additional connection restrictions; see the official setup.