How to Run Geyser as a Standalone Proxy for Any Java Server

Standalone vs Plugin Mode

Geyser can run as a plugin inside a Java server, or as a standalone proxy that forwards Bedrock players to any Java server you choose. Standalone mode is useful when you don't control the Java server or don't want to install plugins on it. Download the standalone Geyser build and run it like any Java application; it generates its own config.yml.

Configuring the Remote Target

In the standalone config, set the remote section's address and port to the Java server you want Bedrock players to reach. Set auth-type appropriately: online for premium servers, or floodgate if you also run Floodgate alongside the standalone Geyser. Set the bedrock section's port to the UDP port Bedrock clients will use. Because standalone Geyser is a separate process, make sure its port is reachable from the internet.

Connecting and Limitations

Start the Geyser process and watch the console for a successful startup message. In Bedrock Edition, add a server using the machine's IP and the Bedrock port. Keep in mind that standalone mode can't use server-side plugins like Floodgate the same way an integrated setup can, and some Java-server-specific features may behave differently. Test joining with a Bedrock client and check the console for translation warnings.