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 →To let Java Edition and Bedrock Edition players join the same Minecraft world, run a Java server and add Geyser as the protocol bridge. On Paper or Spigot, install the Geyser plugin; on Fabric or NeoForge, install the matching server mod; on a proxy network, install Geyser on the proxy. Configure a separate Bedrock UDP listener—commonly port 19132—then expose that port and choose whether Bedrock players authenticate with their own Java account or through Floodgate.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Bedrock servers with free DDoS protection and up to three free backups a day.
How Java–Bedrock crossplay works
Java Edition and Bedrock Edition do not use the same network protocol. A normal Java server understands Java traffic, while a Bedrock client sends Bedrock traffic over UDP. Geyser translates Bedrock packets into the Java protocol and translates the server’s responses back for the Bedrock client. The Java server remains the authoritative game server; Geyser is the compatibility layer in front of it.
As an Amazon Associate I earn from qualifying purchases.
That architecture means you configure two connection paths:
- Java players: connect to the server’s existing Java address and port.
- Bedrock players: connect to Geyser’s Bedrock address and UDP port.
Geyser does not turn a Bedrock client into a Java client, and it does not make arbitrary client-side Java mods work on Bedrock. The setup is intended for a Java server with a Geyser component installed on the server, proxy, or a separate Geyser process.
#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.
Choose the deployment model first
Your server software determines which Geyser package and installation path you need. Pick one model before downloading anything.
| Deployment | Install Geyser where | Best for | Important requirement |
|---|---|---|---|
| Paper or Spigot | Geyser-Spigot plugin in plugins |
A single Java server using the Bukkit-compatible ecosystem | Restart the server after copying the plugin |
| Fabric | Geyser-Fabric mod in mods |
Fabric servers and their server-side mod collections | Fabric API is also required according to the setup documentation |
| NeoForge | Geyser-NeoForge mod in mods |
NeoForge server deployments | Use the build matching the documented server version |
| BungeeCord, Waterfall, or Velocity | Geyser on the proxy | Networks that route players between multiple backend servers | Bedrock clients connect to the proxy, not directly to a backend |
| Standalone | Run Geyser as its own process | Installations where you do not want a plugin or mod inside the Java server | Point Geyser’s Java remote address and port at the backend |
Do not install Geyser only on a backend when your players enter through a proxy. In that arrangement, the proxy is the public entry point and must receive and translate Bedrock traffic.
Check versions and prerequisites
Geyser compatibility changes as Minecraft versions change. The current Geyser setup guidance states that servers older than version 26.2 need ViaVersion. The same documentation snapshot lists Geyser-Fabric and Geyser-NeoForge as running only on a 26.2 server. Treat those statements as version-sensitive: check the current Geyser setup page and the release notes immediately before installation rather than assuming an older or newer combination will work.
Prepare the following before you touch the configuration:
- Console or file access to the Java server, including its
pluginsormodsdirectory. - A recent backup of the world and server configuration.
- The exact Minecraft server version and platform (Paper, Spigot, Fabric, NeoForge, or proxy).
- Permission to edit the host firewall and, for a home server, the router’s port-forwarding rules.
- A decision about authentication: online mode for players who own Java Edition, or Floodgate for Bedrock players who should connect without a paid Java Edition account.
On an older Java server, install ViaVersion as required by the current compatibility guidance before diagnosing a Geyser connection problem. A protocol bridge cannot compensate for an unsupported server-version combination.
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.
Set up Geyser on Paper or Spigot
1. Download the matching plugin
Choose the Geyser-Spigot build that matches the server platform and place its jar file in the server’s plugins directory. Do not put a plugin jar in mods, and do not use a Fabric or NeoForge build on Paper or Spigot.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →2. Restart and let Geyser create its files
Stop and start the server cleanly. On first launch, Geyser creates its configuration under its plugin directory. A full restart is preferable to a reload because protocol plugins may register listeners and commands that a partial reload leaves in an inconsistent state.
3. Configure the Bedrock listener
Open Geyser’s generated configuration and set the Bedrock listener. The documented example uses:
address: 0.0.0.0
port: 19132
clone-remote-port: false0.0.0.0 tells Geyser to listen on the host’s available network interfaces. Port 19132 is an example, not a requirement; you may choose another unused UDP port, but every client, firewall rule, router rule, and tunnel must use the same value. Keep clone-remote-port: false unless you have a specific reason to mirror the Java port.
Bedrock uses UDP, so the selected port must allow UDP traffic. Do not assign the same UDP port to another service such as voice chat or a query listener.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRank #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
4. Restart after editing
Save the configuration and restart the server again. Read the startup log for Geyser’s bound address and port. If the port is already occupied, change the Bedrock port or stop the service that owns it; two listeners cannot bind the same address and port combination.
Set up Geyser on Fabric or NeoForge
Fabric
Copy the Geyser-Fabric mod into mods and install Fabric API as required by the setup documentation. Start the server once so the configuration is generated, then set the Bedrock listener address, UDP port, and authentication mode in the generated Geyser configuration. Use a Geyser build compatible with the server version; the current setup guidance documents Geyser-Fabric for a 26.2 server.
NeoForge
Copy the Geyser-NeoForge mod into mods, start the server to generate its files, and configure the listener in the same way. The current setup guidance documents this integration for a 26.2 server, so recheck compatibility if your NeoForge server is older or newer.
These are server-side integrations. Client-side Java mods do not automatically become available to Bedrock players through Geyser. If a gameplay feature requires a mod installed on every Java client, Bedrock users will not receive that feature merely because the server has Geyser.
Choose online authentication or Floodgate
| Authentication choice | What players need | When to use it | Trade-off |
|---|---|---|---|
| Online | Bedrock players have the Java Edition account required by the server’s online-mode setup | You want the normal account-ownership checks | Players without a qualifying Java account cannot join through this path |
| Floodgate | Bedrock players authenticate through Floodgate instead of presenting a paid Java Edition account | You want Bedrock users to join without buying Java Edition | You must install and configure the matching Floodgate component and handle account linking where needed |
Using normal online authentication
Leave the documented online authentication mode enabled when every connecting Bedrock player has the required Java account. This keeps the server’s normal account-ownership checks in place. Confirm that the Geyser authentication setting matches the Java server’s online-mode configuration; a mismatch produces login failures even when the network port is reachable.
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.
Using Floodgate
Install Floodgate for the same platform as Geyser and select the corresponding Floodgate authentication mode in Geyser’s configuration. Floodgate supports account-linking workflows, which let a player associate a Bedrock identity with a Java account when your server requires that relationship. Follow the prompts produced by your installed Floodgate version and complete linking before troubleshooting gameplay permissions or names.
On proxy networks, Floodgate may be installed across backend servers when you need its API or network-wide skin support. The exact placement depends on the proxy and backend arrangement, but Geyser itself belongs at the proxy entry point.
Recommended Free Tools
Do not treat offline mode as a shortcut
Standalone Geyser exposes floodgate, online, and offline authentication choices. Offline mode is a configuration option, not a recommendation for bypassing account ownership. Without the protections supplied by authenticated accounts, an improperly secured server can allow identity spoofing and unauthorized access. Use it only when you understand the security model and have compensating controls.
Expose the Bedrock UDP port
Local or LAN play
For players on the same network, have Bedrock connect to the host’s local address and the configured Bedrock port. Some LAN environments advertise the server automatically; if discovery does not appear, add the address manually. Java players continue to use the Java endpoint.
Remote play through a router
- Give the server computer a stable local address, either with a static assignment or a DHCP reservation.
- Create a router port-forward for the configured Bedrock port using UDP, not only TCP, to the server’s local address.
- Allow the same UDP port through the host operating system’s firewall and any provider-level firewall.
- Give Bedrock players the public address and configured Bedrock port. Keep the Java address and Bedrock address separate if they use different endpoints.
Forwarding a TCP port alone will not work because Bedrock traffic is UDP. Avoid exposing unrelated administration ports to the internet; forward only the listener that players need.
Using a tunnel
A tunnel such as playit.gg can provide a public route when you cannot configure the router. Create a UDP tunnel to the local Geyser port and give players the tunnel’s assigned address and port. Verify that the tunnel product supports UDP for this use. Geyser’s documentation specifically notes that Ngrok will not work for this path because its relevant tunnel is TCP-only.
Proxy networks: install Geyser at the front door
For BungeeCord, Waterfall, or Velocity, install Geyser on the proxy rather than separately on each backend. Bedrock clients should connect to the proxy’s Bedrock listener, and the proxy routes the translated Java connection to a backend server.
Check all of the following in a proxy deployment:
- The proxy’s Geyser listener has a public UDP port.
- The router, firewall, or tunnel forwards that port to the proxy host.
- The proxy can reach each Java backend on its internal Java address and port.
- Floodgate is placed wherever its API, account linking, or network-wide skin support requires it.
- Backend servers are not advertised to Bedrock players as if they were independent public Geyser endpoints.
Standalone Geyser configuration
With standalone Geyser, the bridge runs outside the Java server. In its configuration, set the Java remote address and port to the backend. The documentation example uses 127.0.0.1 and port 25565 when Geyser and the Java server share a machine; replace these with the actual backend values in your environment.
Select online, floodgate, or offline authentication according to the backend’s account setup. Then configure the standalone process’s Bedrock listener, open its UDP port, and start it before testing. If Geyser runs on a different machine, ensure the Java backend allows connections from that machine and that the remote address is routable from Geyser.
Test the connection in the right order
- From the server console, run
geyser connectiontest <ip> <port>using the public address and Bedrock UDP port you intend players to use. - Confirm that Geyser reports a reachable listener and that the firewall or tunnel shows traffic.
- On Bedrock, add a server with the public address and configured Bedrock port. Do not enter the Java port unless both services intentionally share it and the network supports that arrangement.
- On Java, connect through the normal Java endpoint and verify that existing Java players still join.
- Test with the authentication mode you will actually use. A successful online-mode test does not prove a Floodgate account-linking setup works.
Troubleshoot by symptom
| Symptom | Checks | Likely correction |
|---|---|---|
| Bedrock cannot connect at all | Configured address, UDP port, Geyser startup log, host firewall, router or tunnel rule | Correct the address or port and permit UDP end to end |
| LAN works but remote play fails | Public address, router forwarding, provider firewall, tunnel status | Forward the Bedrock UDP port or use a UDP-capable tunnel |
| Connection reaches Geyser but login fails | Online versus Floodgate mode, Java server online mode, account-linking state | Make the authentication settings consistent and finish linking where required |
| Server starts but Geyser reports incompatibility | Java version, Geyser build, platform, ViaVersion requirement | Install the matching build and add ViaVersion for older servers when the current guidance requires it |
| Proxy players cannot reach a backend | Geyser placement, proxy routing, backend reachability | Install Geyser on the proxy and verify its routes to Java backends |
| Port-binding error appears on startup | Other UDP services using the selected port | Choose an unused UDP port and update every firewall, forwarding, and client setting |
Operational and security checks
- Back up the world before changing server jars, mods, proxy components, or authentication settings.
- Keep Geyser, Floodgate, the server platform, and ViaVersion on compatible releases; recheck the documented compatibility matrix after Minecraft updates.
- Restrict administrative permissions independently of Bedrock access. Crossplay changes the client types that can connect, not who should receive operator privileges.
- Monitor the console after each update for listener, authentication, and protocol warnings.
- Document the Java endpoint, Bedrock endpoint, UDP port, authentication mode, and any account-linking procedure so players receive the correct instructions.
Which setup should you choose?
- One Paper or Spigot server: install Geyser-Spigot, configure its UDP listener, and add Floodgate only if Bedrock users should join without Java Edition accounts.
- Fabric or NeoForge: use the matching server mod, satisfy the documented version and Fabric API requirements, and avoid assuming client-side mods will work for Bedrock.
- Several servers behind a proxy: install Geyser at the proxy and expose the proxy’s UDP port.
- No plugin or mod installation desired: run standalone Geyser and point its Java remote settings at the backend.
- No router access: use a UDP-capable tunnel, while remembering that a TCP-only tunnel cannot carry the Bedrock listener.
The reliable sequence is always the same: match the Geyser package to the deployment, verify version compatibility, configure a unique UDP listener, choose authentication deliberately, expose that listener, and test with the exact client and account types your community will use.
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.
