Buscar páginas do site
A visual guide to diagnosing Geyser, Floodgate and Paper without changing configuration blindly.
online-mode controls Java authentication. RakNet and NetherNet control how a Bedrock client reaches the server. Neither one selects the other.
Traditional UDP transport. The script confirms it with an unconnected ping/pong.
WebRTC transport with signalling. It does not appear as a normal UDP pong.
If Geyser is configured as raknet, use RakNet. If it is nethernet, validate signalling/WebRTC. In both mode, the two routes need separate ports. Do not change auth-type just because transport changed.
Check server.properties and plugins/Geyser-Spigot/config.yml. Never publish management-server-secret, key.pem or passwords.
The Bedrock endpoint should appear on UDP. Java normally uses TCP 25565; Geyser uses the configured Bedrock port.
The probe separates RakNet pong, NetherNet configuration and signalling evidence in the log.
For offline + floodgate, keep the Floodgate key. For online + online, the Java account must be valid. On failure, copy the literal error.
python3 scripts/diagnose-geyser-network.py --server-properties server.properties --geyser-config plugins/Geyser-Spigot/config.yml --log logs/latest.log --format markdownO comando fica no repositório em scripts/diagnose-geyser-network.py e não imprime segredos.
Use auth-type floodgate, keep the key and use the configured RakNet endpoint. This is the local server case that was analysed.
Use auth-type online. Transport can be RakNet or NetherNet depending on client and build; online-mode does not define it.
If the log says duplicate_login, it is not a RakNet problem. A second session has the same identity; stop the old session before reconnecting.
A ping does not prove plugin presence, does not sync account data and does not make Forge/Fabric compatible. For mods, use the separate compatibility diagnosis.