To let Bedrock players join a Java server through Geyser without owning a Java Edition account, install Floodgate 2.0, start it once to generate key.pem, place a copy where Geyser can read it, set auth-type: floodgate under Geyser’s remote: section, and restart. Proxy networks additionally require send-floodgate-data: true and the identical key on every backend.
Godlike.Host offers hosted Minecraft Java servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What Floodgate 2.0 changes in a Geyser setup
Geyser translates connections from Minecraft: Bedrock Edition so they can reach a Java Edition server. A normal Java server still expects Java authentication, however. Floodgate is the companion authentication component that allows a Bedrock player to connect through Geyser without separately signing in with a Java Edition account.
As an Amazon Associate I earn from qualifying purchases.
Floodgate 2.0 identifies the connection with a key generated by Floodgate itself. Geyser must have a matching copy of that key and must be told to use Floodgate authentication. If either the key or the authentication setting is wrong, Bedrock connections fail even when Geyser is otherwise running normally.
Requirements before you edit anything
- A working Geyser installation, either Standalone or a plugin build integrated with a server or proxy.
- Floodgate 2.0 installed on the server or proxy that handles Floodgate authentication.
- Permission to stop and start the service and to edit Geyser’s
config.yml. - File access to the Floodgate configuration directory and to Geyser’s configuration directory.
- For a proxy network, access to the proxy and every backend server, because the same key must be distributed throughout the network.
Do not mix a Floodgate 1.0 build with a Floodgate 2.0 build. Geyser and all Floodgate installations participating in the login path should be updated as a matched set.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Understand Floodgate 2.0’s key files
Floodgate 2.0 creates its authentication key the first time it loads. The current model uses one active file, key.pem. During a migration, Floodgate keeps the previous key as old-key.pem; that file is not the key you should configure for new 2.0 logins.
| File or setting | Where it belongs | Purpose |
|---|---|---|
key.pem |
Floodgate’s configuration folder and a matching copy in Geyser’s folder | The active Floodgate 2.0 key used to authenticate Bedrock connections. |
old-key.pem |
Floodgate’s configuration folder after a 1.0-to-2.0 migration | Retained old key; do not substitute it for the active 2.0 key. |
auth-type: floodgate |
Geyser config.yml, inside remote: |
Tells Geyser to use Floodgate authentication. The value is lowercase. |
send-floodgate-data: true |
Geyser configuration on the proxy | Passes Floodgate connection data through a proxy to the backend. |
config-version |
Floodgate 2.0 configuration | An indication that the installed configuration follows the 2.0 format. |
The exact directory depends on the platform. On Spigot, Paper, or Bungee-style installations, Floodgate commonly stores its files under plugins/floodgate/. For a standalone Geyser installation, the relevant location is normally the directory containing the Geyser jar and config.yml. Plugin builds use Geyser’s own configuration folder. Treat those paths as starting points and confirm the actual folders created by your installation.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Configure Floodgate 2.0 step by step
-
Install Floodgate 2.0 on the authentication endpoint
Install the Floodgate 2.0 build appropriate for your server or proxy platform. If Bedrock players enter through a proxy, install Floodgate where that proxy performs the Floodgate handshake, then install the corresponding Floodgate components required by each backend. Do not start by copying an old 1.0 key into the new installation.
-
Start Floodgate once to generate the key
Start the service and allow Floodgate to finish loading. Its first successful load generates the active
key.pem. Stop the service cleanly before copying the file if your platform keeps files open during runtime. If no key appears, inspect the startup log for a failed Floodgate load or a configuration-directory permission problem.Rank #2
Sale
Smart Watch for Men Women Compatible with iPhone Samsung Android Phone 1.69 inch Full Touch Screen IP68 Waterproof Bluetooh Fitness Tracker Heart Rate/Sleep Monitor (Black)- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
-
Find the generated
key.pemOpen Floodgate’s configuration folder. On many plugin installations this is
plugins/floodgate/, but use the folder reported or created by your platform. Confirm that the file is named exactlykey.pem, including its lowercase spelling. Floodgate 2.0’s folder may also containold-key.pemafter an upgrade; select the active file, not the old one. -
Copy the key into Geyser’s configuration location
For Geyser Standalone, copy
key.peminto the same directory as the Geyser Standalone jar and itsconfig.yml. For a Geyser plugin build, copy it into Geyser’s configuration folder. The copied file must be readable by the account that runs Geyser, and its contents must remain byte-for-byte identical to the Floodgate-generated file.The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Set the authentication type
Open Geyser’s
config.yml. Under the existingremote:section, set the value to lowercase:remote: auth-type: floodgateKeep the setting under
remote:; adding a second top-level setting or using a different capitalization does not configure the intended option. Preserve the YAML indentation used by the file.Rank #3
New Bee Guitar Cable 10ft Electric Instrument Bass AMP Cord- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
-
Check the configured key filename
Geyser’s configuration includes a key-file name setting. The default for the 2.0 arrangement is
key.pem. Make sure that setting matches the file you copied. If you deliberately renamed the file, either restore the namekey.pemor change Geyser’s key-file setting to the exact new name; the two names cannot disagree. -
Restart Geyser
Restart Geyser after saving the configuration. A reload is not a reliable substitute when the key file or authentication mode has changed, because the process may retain the previous authentication state.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Test with a Bedrock connection
Connect from a Bedrock client while watching the Geyser and Floodgate logs. A successful test should show Geyser accepting the connection with Floodgate authentication rather than reporting a missing key, an invalid authentication mode, or a key mismatch. Test a normal Java login separately so that a proxy or backend routing problem is not mistaken for a Floodgate problem.
Proxy networks: distribute one key consistently
A proxy adds another hop between Geyser and the backend server. Configure the proxy’s Geyser instance with send-floodgate-data: true. Then copy the proxy’s active key.pem into the Floodgate configuration folder of every backend that can receive the connection.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Identify which Floodgate installation is authoritative for the proxy login path.
- Stop or maintenance-lock the proxy and backends before replacing key files.
- Copy that authoritative
key.pemto each backend’s Floodgate folder. - Verify that every copy has the same filename and contents; do not generate a separate key on each backend and leave those keys in place.
- Set
send-floodgate-data: truein the proxy’s Geyser configuration. - Restart the proxy and all affected backends, then test a Bedrock connection through the real proxy route.
Floodgate rejects logins when the participating servers use different keys. This commonly happens when a new backend is added, a proxy is restored from backup, or one server is upgraded independently. Re-copy the key from the proxy or primary Floodgate folder rather than copying from an already suspect backend.
Floodgate 1.0 to 2.0 migration
Floodgate 2.0 is not a drop-in replacement for a 1.0 installation. On first load, 2.0 generates a new active key and preserves the former key as old-key.pem. The 2.0 setup uses one key.pem where older arrangements used two keys.
Recommended Free Tools
Upgrade Geyser and every Floodgate server or proxy in the login path together. A Geyser build that worked with Floodgate 1.0 is not compatible with Floodgate 2.0 simply because the jar was left in place. After upgrading, repeat the key-copy procedure, update the authentication setting, and restart all participating components.
To confirm that the installation is actually using the 2.0 configuration format, open Floodgate’s configuration and look for a config-version entry. Its presence is a useful confirmation, but it does not by itself prove that Geyser has the matching key; the file copy and authentication setting still need to be checked.
The key.pem versus public-key.pem naming conflict
Some Geyser documentation still describes copying public-key.pem, while other Floodgate and Geyser setup instructions describe copying key.pem. That difference reflects documentation written for different key models. Floodgate 2.0’s active configuration uses a single key.pem, and that is the file this procedure configures.
Before changing anything, inspect the actual Floodgate folder on your installation. If it contains only the 2.0 key.pem, copy and reference that file. Do not create a made-up public-key.pem or rename files merely to match an older page. If your installation genuinely contains a differently named key, align Geyser’s key-file setting with the file generated by the installed Floodgate build and verify that your Geyser version supports the same 2.0 model.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSecurity rules for the Floodgate key
Treat key.pem like a password. Possession of the key can allow Bedrock accounts to bypass the Java Edition authentication step, so exposure can give an attacker a way to cause harm through the server.
- Never publish the file in a public repository, paste it into a support forum, or attach it to an untrusted ticket.
- Restrict filesystem permissions so only the service account and administrators can read it.
- When transferring it between proxy and backends, use an administrator-controlled private channel.
- Do not include the key in diagnostic archives or screenshots; redact its contents before sharing logs or configuration bundles.
- If the file may have been exposed, treat the installation as compromised and follow your Floodgate version’s key-rotation procedure rather than continuing to distribute the exposed copy.
Verification checklist after the restart
- Floodgate starts without a configuration or permission error.
- The Floodgate folder contains the active
key.pem. - Geyser can read a matching copy from its own configuration location.
remote.auth-typeis exactlyfloodgate, in lowercase.- Geyser’s configured key filename matches the file on disk.
- A proxy has
send-floodgate-data: true. - Every backend uses the same key as the proxy or authoritative Floodgate installation.
- The Floodgate configuration includes
config-version, confirming the 2.0-style configuration. - A Bedrock client can join through the same route ordinary players use.
Troubleshooting common failures
| Symptom | Likely cause | Fix |
|---|---|---|
| Geyser says it cannot find the Floodgate key. | Floodgate never completed its first load, the file is in the wrong directory, or Geyser cannot read it. | Start Floodgate once, confirm that key.pem exists, copy it into the correct Standalone or plugin configuration folder, and check filesystem permissions. |
| Geyser starts but Bedrock authentication does not use Floodgate. | The authentication value is missing, outside remote:, or capitalized incorrectly. |
Set auth-type: floodgate under remote:, save the YAML, and perform a full restart. |
| A key-mismatch error appears. | Geyser has a different key from Floodgate, or a proxy and backend were given different generated keys. | Copy the active key from the proxy or primary Floodgate folder again to every participating component. Do not use old-key.pem. |
The setup followed an older guide that mentions public-key.pem. |
The instructions target a legacy naming or key model. | Inspect the files generated by Floodgate 2.0 and configure the active key.pem; ensure Geyser’s filename setting matches it. |
| One backend works while another rejects Bedrock players. | The new or restored backend has its own key, an outdated key, or no key. | Replace that backend’s Floodgate key with the authoritative proxy key and restart the backend. |
| Floodgate 2.0 appears installed, but the old Geyser build fails. | The Geyser and Floodgate versions are from incompatible generations. | Update Geyser and all Floodgate server/proxy components together, then redo the 2.0 configuration. |
Safe change procedure for live servers
For a small server, the numbered setup is usually sufficient. On a busy network, make the change as a controlled maintenance operation:
- Announce a short maintenance window and stop new logins.
- Back up the existing Floodgate and Geyser configuration files without exposing the key.
- Upgrade Geyser and Floodgate together if migrating from 1.0.
- Start Floodgate and verify the generated 2.0 key before editing Geyser.
- Copy the key through a private administrative channel and check the destination filename.
- Edit
remote.auth-typeand, for proxies,send-floodgate-data. - Restart in an orderly sequence: proxy first when it carries the client connection, then the backends it can select.
- Test a Bedrock login, a Java login, and a route to each backend before ending maintenance.
Keep the old configuration backup offline and access-controlled. It can help you recover the YAML settings, but it should not become an accidental source for redistributing an obsolete or exposed key.
Configuration reference
| Component | Required value or file | Scope |
|---|---|---|
| Floodgate 2.0 | Generated key.pem |
Created on first successful load; authoritative copy must be protected. |
| Geyser | remote.auth-type: floodgate |
Every Geyser instance that handles the Bedrock login. |
| Geyser key filename | key.pem unless you intentionally configured another exact name |
Must match the file present in Geyser’s configuration location. |
| Proxy Geyser | send-floodgate-data: true |
Required when Floodgate data must be passed to backend servers. |
| Backends | Identical copy of the authoritative key.pem |
Every backend that may receive a proxied Bedrock connection. |
When the setup is complete
Floodgate 2.0 authentication is correctly configured when Floodgate has generated the active key, Geyser can read the matching copy, Geyser’s remote: section specifies lowercase auth-type: floodgate, and a proxy passes Floodgate data with one identical key shared across all backends. A clean restart and a real Bedrock login are the final confirmation; a server that merely starts without errors has not yet proved that the complete authentication path works.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
