Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →To let Minecraft: Bedrock Edition players join a Java Edition server, install GeyserMC as the protocol bridge, expose its Bedrock UDP listener, and point it at your Java server. Add Floodgate when Bedrock players should authenticate with Xbox Live and join without owning Minecraft: Java Edition. Geyser can run as a server plugin, a Fabric mod, a proxy component, or a separate standalone process.
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 GeyserMC and Floodgate do
Java and Bedrock use different networking protocols. GeyserMC translates Bedrock network traffic into the Java protocol so a Bedrock client can communicate with a Java server. It does not replace the Java server; it sits in front of it and forwards the translated connection.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
Geyser can be installed directly on several Java server platforms, on a proxy such as BungeeCord, Waterfall, or Velocity, or as a standalone program on another machine. Your choice determines where the Bedrock port is opened and which machine Bedrock players enter.
Floodgate is an optional authentication component. With Floodgate, a Bedrock player signs in through Xbox Live and can join without a Java Edition account. Without Floodgate, Geyser uses the server’s normal Java-oriented authentication arrangement, which generally means the Bedrock player must authenticate as a Java account.
#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.
- Geyser: translates Bedrock traffic and listens for Bedrock connections.
- Floodgate: provides Xbox Live-based Bedrock authentication without requiring a Java Edition account.
- Java server: remains the world, gameplay, permissions, and plugin or mod environment that players ultimately use.
Choose the right installation layout
Use the simplest layout that matches your server. A single Paper or Spigot server normally needs only the Geyser plugin and, if required, the matching Floodgate plugin. A network with several backend servers should put Geyser on the proxy so Bedrock players have one public entry point.
| Layout | Where Geyser runs | Where Bedrock connects | Floodgate arrangement | Operational impact |
|---|---|---|---|---|
| Paper, Spigot, or another plugin server | In the Java server’s plugins folder |
That server’s Bedrock UDP address and port | Install the platform-specific Floodgate plugin on the same server when account-free Bedrock login is needed | Lowest complexity for one server |
| Fabric | As the Geyser platform mod in the server’s mod installation | The Fabric server’s Bedrock UDP address and port | Use the Floodgate build intended for the Fabric/server arrangement | Fits a Fabric modded server; keep platform versions aligned |
| BungeeCord, Waterfall, or Velocity network | On the proxy | The proxy’s public Bedrock UDP address and port | Share one key.pem with Floodgate instances on any backends that also run Floodgate |
One front door, but coordinated proxy and backend configuration |
| Standalone | In a separate Geyser process, potentially on another machine | The standalone host’s Bedrock UDP address and port | Copy the server-generated key.pem to the standalone directory and set auth-type to floodgate |
Separates the translation service from the Java server; requires an additional process and network route |
Requirements and decisions before installing
- Have administrative access to the Java server, proxy, or machine where Geyser will run.
- Know the Java server’s reachable address and port from the machine running Geyser.
- Choose a Bedrock UDP port.
19132is the commonly used example, but your host may assign a different port. - Confirm that your hosting provider permits and exposes UDP traffic on that port. A TCP-only allocation is not sufficient for normal Bedrock access.
- Decide whether Bedrock players must own Java Edition. Install Floodgate if they should join with Xbox Live authentication instead.
- For a proxy network, decide which component owns the public Bedrock port. In the documented layout, that is the proxy, not each private backend.
Install Geyser on Paper, Spigot, and other plugin servers
This is the usual route for a single Java server. The exact jar name varies by platform, so use the Geyser build made for your server software rather than a build for a proxy, Fabric, or standalone deployment.
- Stop the server. Installing or replacing a plugin while the server is running can leave files locked or partially written.
- Download the platform-specific Geyser plugin jar. Select the build intended for your server platform, then place that jar directly in the server’s
pluginsfolder. - Start the server once. Geyser creates its configuration and data files during startup. Watch the console for a successful plugin load and stop the server cleanly after the files are generated if you need to edit them before continuing.
- Open Geyser’s generated configuration. Set the Java server target to the address and port where the Java server is listening. On a single machine this may be a local address; in a hosted arrangement it may be an internal or provider-specific address.
- Set the Bedrock listener. Configure the listen address and UDP port that Bedrock clients will use. The common example is port
19132, but use the port assigned by your host when it differs. - Expose the UDP port. For players outside your LAN, forward the selected UDP port to the server and allow it through the operating system or hosting firewall. Forwarding only the Java server’s TCP port does not make the Geyser listener reachable.
- Restart after editing. Geyser reads its settings at startup. Restart the Java server after configuration changes, then verify that the console reports the listener on the expected address and port.
- Connect from Bedrock. Add the public server address and the configured Bedrock port in Bedrock’s server list. On the same LAN, the server may also appear in the Bedrock Friends tab, but an external player still needs the externally reachable address and UDP port.
Hosting panels sometimes expose a separate allocation for Bedrock. If the panel gives you a port other than 19132, put that assigned value in Geyser’s Bedrock listener and give the same value to Bedrock players. Do not assume the Java port and Bedrock port are interchangeable.
Add Floodgate for Bedrock players without Java Edition
Install the Floodgate build that matches the platform where authentication is being handled. On a plugin server, that means the platform-specific Floodgate jar goes in the server’s plugins folder alongside Geyser. On a proxy topology, install Floodgate according to the proxy/backend arrangement and keep its key consistent everywhere it is used.
Rank #2
- 【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.
Floodgate authenticates the Bedrock player through Xbox Live. It is the component to use when the goal is “Bedrock players can join without purchasing or owning Java Edition,” rather than merely translating Bedrock packets for players who already have Java accounts.
For a standalone Geyser process, use this sequence:
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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Install the platform-specific Floodgate jar on the Java server.
- In the standalone Geyser configuration, set
auth-typetofloodgate. - Copy Floodgate’s generated
key.peminto the same directory as the standalone Geyser files. - Restart standalone Geyser and confirm that it can read the key and reach the configured Java server.
The key is a credential, not a shareable configuration example. The Floodgate documentation warns: “DO NOT DISTRIBUTE THIS KEY TO ANYBODY!” Anyone who obtains it may be able to bypass the intended Java authentication boundary and cause serious damage to the server. Keep key.pem private, restrict file access, and do not upload it to public repositories or send it to players.
Install Geyser on Fabric
Fabric requires the Geyser build intended for Fabric rather than the plugin jar used by Paper or Spigot. Install that build in the server’s mod installation, then start the server once so Geyser creates its files. Use the Floodgate build intended for the same Fabric/server arrangement when account-free Bedrock authentication is required.
Rank #3
- [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
- Stop the Fabric server.
- Place the Fabric Geyser mod in the server’s mod directory.
- Place the matching Floodgate mod there as well if Bedrock users should authenticate through Xbox Live.
- Start the server once and inspect the generated Geyser configuration.
- Set the Java target and the Bedrock listen address and UDP port.
- Expose and firewall the selected UDP port, then restart the server.
- Test with a Bedrock client using the public address and that Bedrock port.
Do not mix a proxy, standalone, or plugin build into the Fabric installation. A jar can be valid Geyser software yet still be the wrong build for the platform loading it.
Install Geyser on a proxy network
For BungeeCord, Waterfall, or Velocity, install Geyser on the proxy and direct Bedrock clients to the proxy. The proxy becomes the public Bedrock front door and selects or forwards to the Java backend, while the backend servers can remain private to the network.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Stop the proxy and backends before changing their files.
- Install the proxy-specific Geyser build on the proxy.
- Install Floodgate on the proxy when the proxy is responsible for Bedrock authentication.
- Configure the proxy’s Bedrock listener and expose its UDP port publicly.
- Configure the Java target or forwarding arrangement so the proxy can reach the intended backend.
- If Floodgate also runs on one or more backends, use the same
key.pemon every Floodgate instance. Do not generate or substitute separate keys for individual servers. - Restart the proxy and backends, then have Bedrock players connect to the proxy address and Bedrock port rather than directly to a backend.
A common failure is installing Geyser only on a backend while telling Bedrock players to use the proxy address. In that arrangement the proxy is receiving traffic it cannot translate. Either put Geyser at the proxy entry point or give players the address of the machine that actually owns the Geyser listener.
Run Geyser as a standalone process
Standalone is useful when you want Geyser on another machine, separated from the Java server’s plugin or mod environment. The standalone process still needs network access to the Java server and its own reachable Bedrock UDP port.
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.
- Create a dedicated folder for standalone Geyser.
- Place the standalone Geyser jar in that folder.
- Launch it once. The first run generates the configuration and supporting files.
- Open the generated configuration and set the remote Java server address and port.
- Set the Bedrock listener address and UDP port on the standalone host.
- If using Floodgate, set
auth-typetofloodgateand copy the Java server’skey.peminto the standalone Geyser folder. - Stop the process cleanly after editing, then launch it again.
- Allow the Bedrock UDP port through the standalone host’s firewall and any upstream network firewall.
- Give Bedrock players the standalone host’s address and configured port.
When troubleshooting standalone, distinguish the two network legs: Bedrock must reach the standalone listener, and standalone Geyser must reach the remote Java server. A working Java server connection does not prove that the public Bedrock UDP port is open.
Identity, usernames, whitelist, and skins
Keep the Floodgate username prefix unless collisions are controlled
Floodgate normally identifies Bedrock users with a username prefix so their names do not collide with Java usernames. Removing that prefix can make names look more familiar, but it is not recommended unless you are certain that Java and Bedrock names can never overlap. A collision can produce confusing behavior, including commands or teleports targeting the wrong player or being unable to distinguish one player from another.
If you deliberately change this behavior, edit username-prefix in Floodgate’s configuration, test with both a Java and a Bedrock account, and maintain a naming policy that prevents duplicates. Do not remove the prefix merely to make a scoreboard or chat line shorter.
Whitelist Bedrock players
Floodgate 2.0 provides dedicated whitelist commands. Use the name as the Bedrock player knows it; the prefix does not need to be included:
fwhitelist add <name>fwhitelist remove <name>
If a player appears to be whitelisted but still cannot enter, check that the command was run on the component handling Floodgate authentication and that the spelling matches the Xbox Live-authenticated name.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Bedrock skins
Floodgate 2.0 is designed to make Bedrock skins visible to Java players. Skin uploads can pass through an upload queue, so a skin may not appear immediately after the player joins. Treat a short delay as normal; persistent absence points to a configuration or connectivity issue rather than a reason to remove the username prefix.
Test the connection in the right order
- From the Geyser console, confirm the Bedrock listener is bound to the intended address and UDP port.
- From the Geyser machine, confirm the configured Java target is reachable.
- From the same LAN, test with the local address if available. Bedrock may show the server in its Friends tab on the same network.
- From an external network, use the public address and the exact Bedrock UDP port. Cellular data is a practical way to avoid accidentally testing a local route.
- If Floodgate is enabled, test with a Bedrock account that is signed in to Xbox Live and, if applicable, added with
fwhitelist. - On a proxy, verify that the Bedrock client is entering through the proxy, not a backend address.
Troubleshooting common failures
“Unable to connect to world”
- Recheck the Bedrock address and UDP port in the client.
- Confirm the host or proxy actually exposes that UDP port; a port shown in a control panel may be reserved, internal, or TCP-only.
- Allow the port through the host and operating-system firewalls.
- For standalone deployments, verify the remote Java address in Geyser’s configuration and test the Java connection separately.
- On a home network, confirm that the router forwards UDP to the machine running Geyser, not merely to a machine running the Java server.
Bedrock reaches the server but authentication fails
- Confirm Floodgate is installed for the platform that is actually handling the connection.
- For standalone, verify that
auth-typeis exactlyfloodgate. - Check that Geyser can read the matching
key.pem. - On a proxy network, make sure every Floodgate instance uses the same key and that the Bedrock client enters through the proxy.
A proxy network rejects Bedrock players
- Install Geyser on the proxy rather than only on a backend.
- Point Bedrock players at the proxy’s public address and Bedrock port.
- Check that the proxy can reach the selected backend.
- Use one shared Floodgate key wherever Floodgate is installed.
Names collide or commands affect the wrong player
- Restore a distinguishing username prefix.
- Avoid removing the prefix unless Java and Bedrock names are controlled so they cannot overlap.
- After changing identity settings, restart the relevant server or proxy and retest commands, teleportation, permissions, and whitelisting.
The whitelist says a Bedrock player is not allowed
- Use
fwhitelist add <name>. - Enter the Bedrock name without the Floodgate prefix.
- Run the command on the server or proxy where Floodgate handles that player’s authentication.
Operational checklist
- Use the Geyser build made for your platform: plugin, Fabric, proxy, or standalone.
- Set the Java target before testing external Bedrock access.
- Use the host-assigned Bedrock UDP port, commonly
19132, rather than assuming the Java port works. - Forward and firewall UDP, not just the Java server’s usual TCP traffic.
- Install Floodgate only when Xbox Live authentication without a Java account is required.
- Protect
key.pemand share the same key across proxy and backend Floodgate instances. - Keep the username prefix unless you have a deliberate collision-control policy.
- Use
fwhitelistwithout adding the prefix to Bedrock names. - When diagnosing a failure, test Bedrock-to-Geyser and Geyser-to-Java as separate network paths.
Bottom line
For one Paper or Spigot server, install the matching Geyser plugin, configure its Java target and Bedrock UDP listener, expose that port, and add Floodgate if Bedrock users should join without Java Edition. Use the Fabric build on Fabric, put Geyser at the proxy for BungeeCord, Waterfall, or Velocity networks, and choose standalone when the translator must run separately. Most connection failures come from the wrong platform build, an unreachable UDP port, an incorrect Java target, or a missing or mismatched Floodgate key.
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.
