Geyser says "port already in use" / the server won't start with Geyser — how do I fix it?

If Geyser reports "port already in use" or your server won't start once Geyser is added, something else is sitting on Geyser's port. Sorting out the port assignment fixes it.

Why this happens

Geyser's Bedrock port is conflicting with another service — often your Java port, or a second copy of Geyser. Giving Geyser its own dedicated port allocation resolves the clash.

Step-by-step

1. Make sure Geyser's Bedrock port matches a dedicated allocation on the IPs & Ports page — not your Java port.
2. Don't run two things on the same port (for example Geyser standalone and the plugin).
3. If clone-remote-port is enabled, Geyser tries to reuse the Java port — turn it off and set an explicit Bedrock port instead.
4. Restart.

Tip: Geyser needs its own UDP allocation separate from your Java port. Extra ports are free to add on the IPs & Ports page, up to what your plan includes.

Frequently asked questions

Can Geyser share the Java port? It's cleaner to give it a dedicated port. If clone-remote-port is on, disable it and set an explicit Bedrock port.

I'm running Geyser standalone and the plugin — is that the problem? Likely yes. Don't run two Geyser instances on the same port; pick one.

Where do I add the port? On the IPs & Ports page — extra ports are free, up to what your plan includes. Then point Geyser's config at it.