Fix "Unable to connect to world" on a Geyser server

"Unable to connect to world" means the Bedrock client sent a request and got no usable answer. On a Geyser server it is almost always the wrong port, Geyser not running, or an outdated Geyser. Work through the checks below in order.

1. Is the server online and Geyser running?

Open the console and look at the startup log. You want to see Geyser start and report the address and port it is listening on. If you see an error about binding the port, or Geyser is missing entirely, fix that first:

Is Geyser-Spigot.jar in the plugins folder?
Is the server Paper (or another Spigot-based server)? Geyser's Spigot build does not load on Vanilla or Forge.
Run plugins in the console. Geyser should be listed in green.

2. Is the port right?

This is the most common cause. Open plugins/Geyser-Spigot/config.yml:

bedrock:
  address: 0.0.0.0
  port: 25571

port must be a port allocated to your server: either your main port or an extra allocation from the Network section. The default 19132 will not work unless it is actually yours.
If clone-remote-port: true is set, Geyser uses the Java port and ignores port.
address should be 0.0.0.0.
The player must type this exact port in the Bedrock Port field.

Details: which port do Bedrock players use.

3. Did you restart after editing?

Port changes only apply after a full restart. geyser reload is not always enough for network settings.

4. Is something else using the UDP port?

Voice chat plugins and some other plugins also listen on UDP. If two plugins share a port, one fails. Give each its own port or allocation.

5. Is Geyser up to date?

If the client shows "Outdated server" or disconnects right after "Locating server", update Geyser. See Geyser version compatibility.

6. Does it work for anyone on Bedrock?

Ask a Bedrock player on a different network or device to try.

Nobody can join: it is a server-side setup problem; recheck steps 1 to 4.
Only one player fails: their network may block UDP. School, work and some public Wi-Fi networks often do. Mobile data, a different network, or disabling VPN and ad-block apps usually helps.

Other messages and what they mean

Message	Likely cause
Unable to connect to world	Wrong port, Geyser not running, UDP blocked
Connection timed out	Server reachable but not answering; port mismatch or server still starting
Outdated server	Geyser older than the client; update Geyser
Outdated client	Player's Minecraft is too old; update the game
Disconnected, asked to log in to Java	Floodgate missing or auth type set to `online`
You are not whitelisted	Add them with `fwhitelist`; see whitelist Bedrock players

If players are kicked after connecting, see Bedrock players kicked when joining.

Get a debug report

Run this in the console:

geyser dump

It uploads a report of your Geyser setup (with sensitive values hidden) and prints a link. Share that link when asking for help.

Still stuck?

Post your geyser dump link and the exact error in the Schokr Discord. Also check status.schokr.gg in case of a node issue.