Floodgate Setup: Let Bedrock Players Join Without a Java Account
Geyser alone gives Bedrock players a way in, but it still wants them to log in with a Java account. Plenty of Bedrock players don't have one. Floodgate is the piece that lets them join with the Bedrock account they already use.
The steps below come from GeyserMC's Floodgate setup page and common-issues list, checked on November 21, 2026. Install Geyser first, using the Geyser guide. Floodgate does nothing without it.
On this page
What Floodgate does
It lets Bedrock users authenticate with their Bedrock account on your Java server. Installed on a proxy, it also makes Bedrock players' skins show properly. That's all Geyser's docs promise on the page we read, and we won't claim more than that.
Install it on a Paper server
- Download Floodgate
Get the Spigot version of Floodgate from GeyserMC's download page.
- Upload it
Put the jar in your
pluginsfolder using the Files tab, then Restart the server. - Tell Geyser to use it
Open
plugins/Geyser-Spigot/config.ymland setauth-typetofloodgate. Save the file. - Restart again
Restart so Geyser reads the change, and watch the Console tab for errors.
Then have a Bedrock player join. If they're told they need a Java account, auth-type is probably still on its old value.
The key.pem file
Floodgate creates a file named key.pem in its config folder. GeyserMC's warning is blunt: do not distribute this key to anybody. It lets Bedrock accounts bypass Java Edition authentication, so a person who holds it can do real damage to your server.
- Treat it like a password. Don't paste it in Discord, a support ticket or a public repo.
- Copy it only where the setup steps tell you to, and nowhere else.
- If you copied it into Geyser's own folder on the same server, delete that copy. Geyser's common-issues page lists that as the cause of the "Cannot reply to EncryptionRequestPacket" error.
Running a proxy
Behind BungeeCord or Velocity, Floodgate only has to be installed on the proxy. You only need it on the backend servers if you want to use the Floodgate API there. The documented backend steps are:
- Install Floodgate-Spigot (or the Fabric version) on each backend.
- Turn on
ip_forwardin BungeeCord'sconfig.yml, or set up player information forwarding for Velocity. - Set
bungeecordtotrueinspigot.ymlfor BungeeCord. For Velocity, follow Velocity's guide. - Start the proxy, then set
send-floodgate-datatotruein the proxy's Floodgate config. - Copy
key.pemfrom the proxy's Floodgate folder into each backend's Floodgate folder. - Restart the backends and the proxy.
On a hosted panel like ours, a proxy setup is more involved than most single servers need. If you're not already running one, you can skip this section.
Names, whitelists and linking
Floodgate has a username prefix setting, a space-replacement option and an account linking feature. The pages we checked don't give their defaults, so look in your generated Floodgate config.yml instead of trusting a number from a forum post. Whatever name Floodgate gives a Bedrock player is most likely the name your whitelist and permissions plugin will see, so test it with one Bedrock account. The whitelist and ops guide covers adding players.
Frequently asked questions
Do I need Floodgate to use Geyser?
Not strictly, but without it Bedrock players need a paid Java account to log in. Floodgate removes that requirement.
What is key.pem in Floodgate?
A key file that lets Bedrock accounts join without Java authentication. GeyserMC says never to give it to anyone.
Where do I install Floodgate behind a proxy?
On the proxy. Install it on the backend servers only if you want the Floodgate API there.
Why do I get Cannot reply to EncryptionRequestPacket?
A common cause is a copy of the Floodgate key sitting in Geyser's folder on the same server. Delete it and restart. A mismatch between online and offline mode is the other usual cause.
Does Floodgate change how skins look?
Installed on a proxy, it makes Bedrock skins show properly, according to GeyserMC.