
Quick setup on a Space-Node server:
- Put Geyser and Floodgate in your
pluginsfolder (Paper, Spigot, Purpur) ormodsfolder (Fabric, NeoForge). - Give Geyser its own port: create an extra allocation in the panel's Network tab. In the
bedrocksection of the Geyser config, setclone-remote-port: false, put that allocation inportand settransport: nethernet. GeyserMC says Bedrock 26.60, released on 27 October 2026, stops connecting over RakNet, and with NetherNet the Geyser port needs TCP as well as UDP. Use Geyser build 1273 or newer, the first that supports 26.60, and check thetransportline yourself: updating Geyser does not change an existingraknet. Our NetherNet guide has the full switch. - Set
auth-type: floodgatein the Geyser config, so Bedrock players do not need a Java account. - Restart, run
geyser connectiontest <ip> <port>in the console, then join from Bedrock with your server address and the Bedrock port.
On your own VPS: the same, but open the Bedrock port for TCP and UDP in your firewall (19132 by default).
Console players (Xbox, PlayStation, Switch): consoles have no "Add Server" button. They usually join through BedrockConnect, see the console section below. BedrockConnect added NetherNet in release 1.72.0 on 27 October, but on a 26.60 console it only helps once the DNS server you use runs that version; our console guide for Switch 2, Xbox and PS5 covers every route.
This is our most complete Geyser guide. Shorter guides with a single focus are listed at the end.
Why cross-play matters
Two editions, one group of friends
Minecraft comes in two editions that cannot talk to each other. Java Edition runs on PC. Bedrock Edition runs on phones, tablets, Xbox, PlayStation, Nintendo Switch and the Minecraft for Windows app. In most friend groups at least one person is on Bedrock.
Java servers cannot accept Bedrock connections on their own. The two editions use different network protocols.
GeyserMC translates between them in real time, so Bedrock players can join a Java server.
What you can and cannot do
With Geyser, Bedrock players can:
- join a Java server from mobile, Windows, and from Xbox, PlayStation and Switch with a workaround,
- play survival, creative and most minigames,
- see Java players, chat, trade and build together.
The limits:
- Geyser only works with server-side mods. The Geyser setup guide is direct about it: "Mods that players also need to install on their client will not work."
- Some things cannot be translated at all. The Geyser wiki's list of current limitations includes clickable links in chat, telling left and right clicks apart in inventories, and anything that relies on tab completion.
- Game rules come from the Java server. Redstone, combat and farms behave the Java way for everyone, which can surprise players used to Bedrock.
- Translating packets costs the server some extra work for every Bedrock player.
Use case: your friend only has a phone, you have a PC. With Geyser you play together on your Java server.
Want your whole friend group on one server? Java, mobile, Xbox, PlayStation and Switch players on the same world. Pick the Space-Node location closest to most of your group. The plan selector on the Minecraft page measures your ping to each location except India from your own browser.
Architecture: how Geyser works
The translation layer
Bedrock Player (Xbox): Java Server:
┌─────────────┐ ┌──────────────┐
│ Bedrock │ TCP + UDP │ │
│ Client ├───────────────>│ Geyser │
│ (Sends │ Bedrock port │ Plugin │
│ Bedrock │ │ (Translates)│
│ Packets) │ └──────┬───────┘
└─────────────┘ │ Java protocol
│
┌──────▼───────┐
│ Java Server │
│ (Thinks it's │
│ a Java client)│
└──────────────┘
Key points:
- Geyser listens for Bedrock players on a port of its own, 19132 by default. With NetherNet, players find the server over TCP on that port and play over UDP.
- It translates Bedrock packets to Java packets and back, in real time.
- It hands them to the Java server as if a Java client connected. The Geyser FAQ says it "emulates a Minecraft: Java Edition client". The plugin and mod versions do this inside the server process, which the FAQ says gives faster loading, lower latency and accurate IP addresses.
- The Java server treats Bedrock players as normal players.
Why TCP and UDP?
- Java Edition connects over TCP.
- Bedrock Edition used to connect over UDP only, through RakNet. With NetherNet, the client first asks the server over TCP how to connect, which GeyserMC calls signaling, and then plays over UDP. The Geyser setup guide: "Before NetherNet, forwarding UDP was enough. Now, players use TCP to find your server and UDP to play on it, so without TCP your server will not show up."
That is why Geyser needs a port number of its own. The same guide: "Geyser uses it over both TCP and UDP, so it cannot be the port of the Paper / Spigot server." Earlier versions of our guide offered clone-remote-port to put Bedrock on the Java port number. GeyserMC's NetherNet post now says that option "only works with external signaling".
Installation: step by step
Prerequisites
| Requirement | What you need |
|---|---|
| Server software | Paper, Spigot or Purpur (plugin), Fabric or NeoForge (mod), a proxy such as Velocity, or Geyser Standalone |
| Minecraft version | Geyser follows the newest Java version, 26.3 since Geyser 2.12.0 on 14 October 2026. Older Paper and Spigot servers need ViaVersion. Geyser-Fabric and Geyser-NeoForge run only on 26.3 |
| Ports | The Java port (TCP) and a Bedrock port of its own, open for TCP and UDP. On a hosted server that is an extra allocation. Sharing the Java port with clone-remote-port only works on RakNet, which 26.60 clients no longer use, or with external signaling |
| RAM | Some headroom on top of what the server already uses. How much depends on how many Bedrock players are online |
Where Geyser does not run directly:
- Vanilla servers cannot load plugins. Use Geyser Standalone next to them.
- Forge is not among the platforms on the Geyser setup page (Paper and Spigot, Fabric, NeoForge, proxies, ViaProxy, Standalone). And even with Standalone, mods that need a client install do not work for Bedrock players.
- Realms cannot run plugins at all.
Method 1: Paper, Purpur or Spigot (plugin)
Step 1: Download Geyser
# Navigate to plugins folder
cd ~/minecraft-server/plugins
# Download latest Geyser-Spigot
wget https://download.geysermc.org/v2/projects/geyser/versions/latest/builds/latest/downloads/spigot \
-O Geyser-Spigot.jar
On a Space-Node server you can skip the command line. Download the jars from geysermc.org and upload them through the panel's file manager or over SFTP.
Step 2: Download Floodgate
Floodgate lets Bedrock players join without owning Java Edition.
# Download Floodgate
wget https://download.geysermc.org/v2/projects/floodgate/versions/latest/builds/latest/downloads/spigot \
-O floodgate-spigot.jar
Step 3: Restart the server
Restart fully so both plugins create their config files. You should see Geyser start in the console. Then set the Bedrock port as described in the port section below and restart once more.
If you see errors, skip to the troubleshooting section.
Method 2: Fabric or NeoForge (mod)
The Geyser docs note that Geyser-Fabric and Geyser-NeoForge run only on a 26.3 server. Fabric also needs Fabric API.
# Navigate to mods folder
cd ~/minecraft-server/mods
# Download Geyser-Fabric (use .../downloads/neoforge for NeoForge)
wget https://download.geysermc.org/v2/projects/geyser/versions/latest/builds/latest/downloads/fabric \
-O Geyser-Fabric.jar
Floodgate for Fabric and NeoForge comes from its Modrinth page, as the Floodgate setup page describes. The Geyser config then sits in /config/Geyser-Fabric/config.yml or /config/Geyser-NeoForge/config.yml.
Remember the rule from above: only server-side mods work for Bedrock players. A modpack that players must install on their own PC will not work for them.
Restart the server as in Step 3 above.
Method 3: Standalone (for servers that cannot load plugins)
If you run vanilla, or cannot install plugins:
# Create Geyser directory
mkdir ~/geyser-standalone && cd ~/geyser-standalone
# Download Geyser-Standalone
wget https://download.geysermc.org/v2/projects/geyser/versions/latest/builds/latest/downloads/standalone \
-O Geyser-Standalone.jar
# Start Geyser
java -Xms512M -Xmx512M -jar Geyser-Standalone.jar
Edit the config to point to your Java server:
# config.yml (Standalone)
java:
address: 127.0.0.1 # Java server IP (localhost if same machine)
port: 25565 # Java server port
auth-type: online # Requires Java accounts unless using Floodgate
Older Geyser versions call this section remote instead of java. The setting names inside are the same.
In the bedrock section of the same file, set transport: nethernet. Keep port at 19132 or pick another free port, and open it for TCP and UDP as shown in the port section below.
Restart Geyser. Bedrock players connect to <geyser-ip>:<bedrock port>. The GeyserMC FAQ recommends the plugin versions over Standalone where you can use them.
Critical: the Bedrock port, TCP and UDP
A very common reason Geyser fails
Error seen by Bedrock players:
Unable to connect to world.
Cause: the Bedrock port does not reach Geyser over both TCP and UDP. Without TCP the server does not show up in the list. Without UDP it shows up, but joining times out.
Why this is confusing: most tutorials only talk about the Java port, which is TCP, and older Geyser tutorials open UDP only for Bedrock. With NetherNet the Geyser port needs both.
On Space-Node (and other panel hosts)
Give Geyser a port of its own. It costs nothing.
- In the panel, open the Network tab and click Create Allocation. Your plan includes three allocations, and we can raise that to five on request.
- Note the new port.
- Set it in the Geyser config:
bedrock:
address: 0.0.0.0
clone-remote-port: false
port: 25591 # your new allocation's port
transport: nethernet
- Restart. The console shows a line that starts with
Built-in signaling started on http://, followed by the address and your Geyser port. Bedrock players type your server address and this port. Our panel opens every allocation for both TCP and UDP, which is what NetherNet needs.
These are the lines GeyserMC's setup guide gives for hosts where you can allocate ports. GeyserMC says Bedrock 26.60, released on 27 October 2026, stops connecting over RakNet, so these are the lines current Bedrock clients need. Geyser build 1273, the first with 26.60 support, only uses nethernet by default in a new config, so check the line in an existing one. Our NetherNet guide covers HTTPS, the first-join trust prompt and the checks after the switch.
Why not clone-remote-port? Earlier versions of this guide offered it to save the extra allocation. It puts Bedrock on the Java port, and built-in signaling needs that port over TCP, which the Java server already holds. GeyserMC's NetherNet post: "clone-remote-port only works with external signaling." Geyser then falls back to the Warden signaling service by itself, and players join with the address and port Geyser prints in the console instead of your own. If your config still says clone-remote-port: true, switch it off as above and give your players the new port.
Players on older Bedrock versions. transport: both accepts NetherNet and RakNet side by side. GeyserMC suggested it for players on versions older than 26.40, but Geyser build 1273 supports Bedrock 26.40 to 26.60 only, so today it mainly helps 26.40 clients, which the setup guide says fetch the server's MOTD and player count over RakNet. The two cannot share a UDP port, so NetherNet then needs its own as webrtc-port. GeyserMC's guide says that can be the Java port, because the Java server only uses it over TCP, as long as nothing else uses UDP there. Otherwise it is one more allocation: with Java, Geyser and voice chat on three, webrtc-port is a fourth, so ask us in live chat to raise your limit.
Ports that cannot be shared. The Geyser setup guide is explicit: "No other program can use the Geyser port, over either protocol. This includes programs that use UDP, such as voice chat mods or Query, and programs that use TCP, such as another server, a web map, or a website." If you run Simple Voice Chat, it gets its own allocation. If you have enable-query=true in server.properties, the query uses UDP on query.port, so keep that off the Geyser port and off the port you use as webrtc-port. Our Simple Voice Chat fix explains the voice side. Bedrock players cannot use Simple Voice Chat itself; our Bedrock voice chat guide explains why and covers the Discord and web bridges.
If Bedrock players still cannot connect after this, ask in live chat.
Linux (UFW firewall)
# Allow 19132 for Bedrock: TCP for signaling, UDP for gameplay
sudo ufw allow 19132/tcp
sudo ufw allow 19132/udp
# Verify
sudo ufw status
# Should show:
# 19132/tcp ALLOW Anywhere
# 19132/udp ALLOW Anywhere
# 25565/tcp ALLOW Anywhere
If UFW is inactive:
sudo ufw allow 25565/tcp
sudo ufw allow 19132/tcp
sudo ufw allow 19132/udp
sudo ufw enable
Allow the Java port before you enable UFW, and also allow SSH if you manage the box over SSH, or you lock yourself out. With transport: both, also allow the webrtc-port for UDP.
VPS (cloud firewall: AWS, DigitalOcean, Hetzner)
Example: DigitalOcean
- Go to Networking, then Firewalls
- Edit your firewall rule
- Add two Inbound Rules, one with protocol TCP and one with UDP:
- Type: Custom
- Protocol: TCP, then UDP
- Port Range: 19132
- Sources: All IPv4 / All IPv6
Example: AWS EC2 Security Group
- Go to EC2, then Security Groups
- Select your instance's security group
- Inbound Rules, Edit
- Add two rules:
- Type: Custom TCP, then Custom UDP
- Port: 19132
- Source: 0.0.0.0/0 (anywhere)
Windows Server (firewall)
# Open PowerShell as Admin
New-NetFirewallRule -DisplayName "Minecraft Bedrock (Geyser) TCP" `
-Direction Inbound `
-Protocol TCP `
-LocalPort 19132 `
-Action Allow
New-NetFirewallRule -DisplayName "Minecraft Bedrock (Geyser) UDP" `
-Direction Inbound `
-Protocol UDP `
-LocalPort 19132 `
-Action Allow
Verify:
Get-NetFirewallRule -DisplayName "Minecraft Bedrock (Geyser)*"
Test the port
Tools like nc -u cannot tell you whether a UDP port is open, because UDP has no handshake. Use Geyser's own test instead. In the server console:
geyser connectiontest <ip> <port>
Use your public server address and the Bedrock port players will type.
To check the TCP side on its own, run this from a machine outside your network:
curl http://YOUR_SERVER_IP:19132/v1/join
That is the first request a NetherNet client sends. Geyser answers it with JSON that holds the server name, version and player count. A timeout means TCP does not reach Geyser. With HTTPS set up for signaling, use https:// and your domain.
Floodgate configuration
Why Floodgate matters
Without Floodgate:
- Bedrock players must own Java Edition and sign in with that account.
With Floodgate:
- Bedrock players join with the Microsoft account they already use on Bedrock.
- No Java Edition purchase required. In the Floodgate docs' words, they join "without needing a paid Minecraft: Java Edition account".
- The server sees them with a prefix,
.by default, soSteveon Bedrock becomes.Steve.
Setup
- Install Floodgate next to Geyser (see Method 1 or 2) and restart.
- In the Geyser config, set:
java:
auth-type: floodgate
(remote: instead of java: on older Geyser versions.)
- Restart again.
Floodgate creates its own config in plugins/floodgate/config.yml. The defaults are fine for most servers. The prefix lives here:
# plugins/floodgate/config.yml
# Prefix added to Bedrock usernames to avoid name clashes with Java players
username-prefix: "."
# Should spaces be replaced with '_' in Bedrock usernames?
replace-spaces: true
Floodgate also creates key.pem. The Floodgate docs are blunt about it: "DO NOT DISTRIBUTE THIS KEY TO ANYBODY!" Anyone with that key can let Bedrock accounts bypass Java authentication on your server.
Test: join from Bedrock. Your name shows with the . prefix.
Connecting from Bedrock clients
Mobile (iOS/Android)
- Open Minecraft (Bedrock)
- Tap Play, then the Servers tab
- Scroll down, tap Add Server
- Enter:
- Server Name: Your Server
- Server Address: your server address
- Port: your Geyser port
- Tap Save, then tap the server to join
Example:
Server Address: play.yourserver.com
Port: 19132
Windows (Bedrock edition)
Not Java Edition. This is the Minecraft for Windows app.
- Open Minecraft for Windows
- Click Play, then Servers
- Scroll to the bottom, Add Server
- Enter the same details as on mobile
- Join
Common mistake: opening the Java Edition launcher instead of the Bedrock app.
Xbox, PlayStation and Nintendo Switch
Consoles have no "Add Server" button. The Geyser wiki says all consoles can still join third-party servers, Geyser servers included, with workarounds. The usual workaround is BedrockConnect. BedrockConnect added NetherNet, the transport Bedrock 26.60 moved every client to on 27 October, in release 1.72.0 of that day. The steps below only work on a 26.60 console once the DNS server you use runs that version, so check its GitHub page before you rely on them. Our Switch 2, Xbox and PS5 guide for 26.60 keeps the current status of every console route.
Console connection: BedrockConnect DNS
What is BedrockConnect?
BedrockConnect is a small third-party Bedrock server that shows players a server list where they can type any address. It is free and open source, and not affiliated with GeyserMC.
How it works:
- You change the console's primary DNS to a BedrockConnect server.
- You open one of the featured servers in the Servers tab.
- Instead of that featured server, the BedrockConnect server list opens.
- There you enter your own server address and port.
The BedrockConnect page lists these featured servers as redirect-compatible: Mineville, Lifeboat, Enchanted, Galaxite and The Hive.
Only use DNS addresses from the official BedrockConnect GitHub page. A DNS server sees your console's lookups, so do not take addresses from random videos or comments.
Xbox and Nintendo Switch
Step 1: Have your server details ready
- Server address:
play.yourserver.com(or an IP like123.45.67.89) - Port: your Bedrock port
Step 2: Change the DNS
In the console's network settings, set DNS to manual and enter:
- Primary DNS:
104.238.130.180 - Secondary DNS:
8.8.8.8
On Switch: System Settings, Internet, Internet Settings, pick your network, Change Settings, DNS Settings, Manual.
Step 3: Join via a featured server
- Open Minecraft
- Play, then Servers
- Pick a redirect-compatible featured server, such as The Hive
- The BedrockConnect server list opens
- Enter your server address and port, and join
BedrockConnect can keep your server in its list, so next time it is one click. The Nintendo Switch needs a Nintendo Switch Online membership for online play.
PlayStation 4/5
The BedrockConnect page lists a separate DNS for PlayStation:
Primary DNS: 45.55.68.52
Secondary DNS: 8.8.8.8
Steps (PS4, the PS5 menus are similar):
- Settings, Network, Set Up Internet Connection
- Select Wi-Fi or LAN cable
- Custom
- IP Address Settings: Automatic
- DHCP Host Name: Do Not Specify
- DNS Settings: Manual
- Primary:
45.55.68.52 - Secondary:
8.8.8.8
- Primary:
- Test Connection
Join via a featured server, the same as on Xbox.
If it does not work: the Geyser wiki notes that the main BedrockConnect IP is often blocked on consoles. The BedrockConnect GitHub page lists other community-run instances, and the Geyser wiki points to the Public GeyserConnect as another option.
Phone apps (no DNS change)
For players who would rather not change DNS:
Apps such as BedrockTogether (Android, iOS 14 or later) and MCCompanion (iOS, Android, macOS, Windows), both listed on the Geyser wiki, make your server show up as a LAN game.
- Install the app on a phone
- Enter your server address and Bedrock port
- Start it
- On the console, open Minecraft, go to the Friends tab and join the LAN game
Limitation: the console and the phone must be on the same network.
Geyser configuration in more detail
config.yml
Location: plugins/Geyser-Spigot/config.yml (plugin), config/Geyser-Fabric/config.yml or config/Geyser-NeoForge/config.yml (mod).
Current Geyser versions group the settings into sections. The ones most people touch:
bedrock:
# IP Geyser listens on. Leave at 0.0.0.0 unless you want to limit it.
address: 0.0.0.0
# Port Bedrock players connect to, used over TCP and UDP
port: 19132
# Keep this off: it puts Bedrock on the Java port and ignores "port"
clone-remote-port: false
# nethernet, both or raknet. New configs default to nethernet since build 1273
transport: nethernet
java:
# online (Java account needed), floodgate, or offline
auth-type: floodgate
motd:
# Shown to Bedrock players when passthrough-motd is false
primary-motd: "My Java Server"
secondary-motd: "Java and Bedrock"
passthrough-motd: true
# Only visual, and only used when passthrough-motd is false
max-players: 100
gameplay:
# Show coordinates to Bedrock players
show-coordinates: true
# Block Bedrock's scaffolding-style bridging
disable-bedrock-scaffolding: false
Note on max-players: this is not a separate player limit for Bedrock. The config itself says it "is only visual". Your real limit is the Java server's max-players in server.properties.
Restart the server after changes. geyser reload exists too, but the Geyser docs warn that it kicks all players when used.
Linking Java and Bedrock accounts
Problem: you have a Java account (Steve) and a Bedrock account (.Steve through Floodgate). The server sees two different players with two inventories.
Solution: Floodgate's Global Linking, which is on by default in Floodgate 2.0.
How to link:
- Join the GeyserMC link server with both accounts:
link.geysermc.org, Java port 25565, Bedrock port 19132. - Type
/linkaccounton one of them. You get a code. - On the other account, type
/linkaccount <code>. - Both accounts are kicked with a message that the link worked.
After linking, the GeyserMC docs say you use the Java account's location, inventory and achievements from either platform. The Bedrock account's own data is not accessible until you unlink, so move your items to the Java side first.
You do not need to install anything on your server for this. Servers that prefer their own database can set up local linking with a Floodgate database extension and enable-own-linking, as described on the Floodgate linking page.
Troubleshooting
Error: "Unable to connect to world" (Bedrock)
Cause 1: the Bedrock port does not reach Geyser
Run geyser connectiontest <ip> <port> in the console. On Space-Node, check that port is an allocation that belongs to your server, that clone-remote-port is false and that transport is nethernet. On a VPS, check that Geyser listens on the port and that the firewall allows it for TCP and UDP:
# Test from the server itself
sudo ss -tulpn | grep 19132
# Should show the Java process that runs Geyser on :19132
Fix: see the port section above.
Cause 2: Geyser is not running
Check the console during startup for Geyser's startup message, and check that the jar is in the right folder:
ls ~/minecraft-server/plugins/ | grep -i geyser
Fix: reinstall Geyser (see the installation section).
Cause 3: something else holds the port
Voice chat or the query on the same port as Geyser. Give each its own port.
Bedrock players must sign in to a Java account, or are kicked on login
Cause: auth-type is online and Floodgate is not set up. Geyser then expects a Java account.
Fix: install Floodgate and set auth-type: floodgate in the Geyser config.
java:
auth-type: floodgate # Not "online"
server.properties:
# Keep this true for Java players
online-mode=true
Restart the server. Bedrock players can now join without Java accounts.
Error: Bedrock players see "Outdated Client" or "Outdated Server"
Cause: Bedrock clients update automatically, and your Geyser build does not support the newest Bedrock version yet.
Fix: update Geyser to the latest build and restart. On Paper and Spigot, also check whether ViaVersion needs an update.
Performance: Bedrock players lag more than Java players
Cause: translation work on the server, plus mobile connections that are often less stable than a wired PC.
What helps:
- Keep Geyser, Floodgate and your server software up to date.
- Check with spark where the server's time actually goes before changing anything.
- If the whole server is under load, lower
view-distanceorsimulation-distanceinserver.properties. That affects every player, Java and Bedrock. - Remember that a phone on mobile data will always feel worse than a PC on a cable.
Java players cannot see Bedrock skins
Cause: Bedrock skins come from Microsoft accounts, not from Java's skin system.
Fix: make sure Floodgate is installed. It is what normally makes Bedrock skins visible to Java players. If skins still show as Steve or Alex, our Bedrock skins fix goes through the other causes.
Security considerations
Bedrock sign-in
Floodgate trusts players because Geyser checks their Microsoft (Xbox) sign-in before passing them on. That trust rests on the key.pem shared between Geyser and Floodgate. Keep that file private, never paste it in a support chat or a public repository, and replace it if it leaks.
Result: a .Steve on your server is the Bedrock account "Steve", not someone typing that name.
Bedrock-specific mechanics
Some movement is different on Bedrock. Scaffolding-style bridging is the best-known example. If that matters on your server, set disable-bedrock-scaffolding: true in the gameplay section of the Geyser config.
If you run an anticheat, check the Geyser wiki's anticheat compatibility page before you open the server to Bedrock players. Anticheats that do not know about Geyser can flag Bedrock movement.
X-ray resource packs work on Bedrock clients too. Paper's Anti-Xray hides ores from Bedrock players on Geyser as well; our Bedrock x-ray and Anti-Xray guide has the settings and tests.
Performance impact
Java only versus Geyser enabled
We do not publish benchmark numbers for this. The load depends on your plugins, your world and how many Bedrock players are online at once. This is what changes:
| Area | Java only | With Geyser |
|---|---|---|
| Server work per player | Normal | Extra work for every Bedrock player, because each packet is translated |
| RAM | Normal | Somewhat higher while Bedrock players are online |
| Ports | Java port (TCP) | Plus a Bedrock port of its own, open for TCP and UDP |
| Where the cost lands | n/a | On the server that runs Geyser (or the proxy, if Geyser runs there) |
Check the cost on your own server with spark while Bedrock players are online.
For larger networks, Geyser can run on the proxy (Velocity or BungeeCord) or as Standalone, which moves the translation work off the game server:
Bedrock Players → Geyser (proxy or Standalone) → Java Server
Multi-server setup (Velocity + Geyser)
For networks with multiple backend servers:
┌─────────────┐
│ Velocity │ (Proxy)
│ + Geyser │
│ + Floodgate│
└──────┬──────┘
│
┌───────────────┼───────────────┐
│ │ │
┌────▼────┐ ┌────▼────┐ ┌────▼────┐
│ Lobby │ │ SMP │ │Minigames│
│ Server │ │ Server │ │ Server │
└─────────┘ └─────────┘ └─────────┘
The Geyser setup guide: "Install Geyser only on the Velocity server!"
1. Install Geyser and Floodgate on the Velocity proxy
cd ~/velocity/plugins
wget https://download.geysermc.org/v2/projects/geyser/versions/latest/builds/latest/downloads/velocity \
-O Geyser-Velocity.jar
wget https://download.geysermc.org/v2/projects/floodgate/versions/latest/builds/latest/downloads/velocity \
-O floodgate-velocity.jar
Set auth-type: floodgate in the Geyser config on the proxy. Give Geyser its own port on the proxy, open for TCP and UDP, and set transport: nethernet, the same way as above.
2. Optional: Floodgate on the backend servers
You only need this when plugins on the backends use the Floodgate API. The Floodgate setup page adds that it also displays Bedrock skins properly. Then:
- set up player information forwarding on Velocity,
- set
send-floodgate-data: truein the proxy's Floodgate config, - copy
key.pemfrom the proxy's Floodgate folder to every backend's Floodgate folder.
3. Versions
The Geyser docs: "All servers on the network must accept 26.3 Java clients, as Geyser imitates one." Use ViaVersion on older backends.
Result: Bedrock players connect to the proxy and get routed to the backend servers like everyone else.
Monitoring Bedrock players
Seeing who is on Bedrock
In game or in the console:
/geyser list
This lists all players connected through Geyser.
In the logs:
tail -f logs/latest.log | grep -i geyser
Spark profiling for Geyser overhead
/spark profiler --timeout 120
Look for org.geysermc.geyser in the results. If Geyser takes a large share of the tick while few Bedrock players are online, update Geyser first. If it grows with the number of Bedrock players, consider moving Geyser to a proxy.
Conclusion: is cross-play worth it?
Pros
- Bedrock friends can join your Java server from phones, Windows and consoles
- One community instead of a separate Bedrock server
- Free: Geyser and Floodgate are open source
- No extra cost for the port on Space-Node: Geyser gets a free extra allocation
Cons
- Extra server load for every Bedrock player
- Some things cannot be translated (see the Geyser limitations list)
- Client-side mods do not work for Bedrock players
- Consoles need a workaround (BedrockConnect or a phone app)
Recommendation
Use Geyser if:
- you have friends or community members on mobile or console,
- you run vanilla, plugins, or server-side mods only,
- you want the widest possible reach.
Skip Geyser if:
- your modpack must be installed on the client,
- you need every Java mechanic to feel identical for everyone, such as on a competitive PvP server.
For most friend groups and community servers, cross-play is worth setting up.
Run your cross-play server on Space-Node
What you get for Geyser on a Space-Node Minecraft server:
- The Bedrock port at no extra cost: create an extra allocation in the Network tab. The panel opens it for TCP and UDP, as NetherNet needs. Three allocations are included, and we can raise that to five on request.
- Room for voice chat too: Simple Voice Chat gets its own allocation next to Geyser.
- Full file access: file manager and SFTP, so you can install Geyser, Floodgate and ViaVersion yourself.
- Locations in Europe, North America, Asia and Australia: the plan selector measures your ping to each one except India before you order.
Start a Minecraft server at Space-Node
Other Geyser guides with a narrower focus:
- Connect mobile players to your Java server
- GeyserMC and Floodgate on Paper, step by step
- GeyserMC cross-play tutorial: plugin or Standalone
- What to check in a host before you run Geyser
Related guides: