Separate a Geyser signalling failure from a gameplay timeout

Applies to: Geyser; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A Bedrock server entry that never appears and a visible entry that times out during joining point to different checks. Current Geyser NetherNet uses TCP for signalling and UDP for gameplay. A successful Java connection proves neither Bedrock path.

Record the starting point

Write down the Geyser build, Bedrock client version, assigned public address and advertised Bedrock port. Keep one failed attempt's timestamp. Use a remote client outside the server network so a local shortcut cannot hide a public routing problem.

Work through the change

Open the service Network page and match the configured listener to an allocation that supports the protocols your Geyser setup requires. Ask support about protocol availability rather than inventing a second port.
From the remote Bedrock client, refresh the server entry and record whether its description and player count appear. Keep this result separate from the later join attempt.
Attempt one join and compare the timestamp with the Geyser console. Note whether signalling starts, gameplay negotiation begins, or no request reaches Geyser.
Check any configured external signalling provider as a separate component. The address players save may differ from the Java address and from the address inside the container.

Check the result

Success means a remote player can discover the entry, complete joining and move in the world. Ask the tester to disconnect and reconnect once; cached discovery information can conceal a broken new address. Record the public endpoint they actually used.

If the result differs

An empty console during discovery suggests the wrong endpoint, listener or TCP path. A visible entry followed by a negotiation timeout makes the UDP advertisement and gameplay path worth checking. Authentication errors after negotiation belong to the identity configuration, not a blanket firewall reset.

Restore only the listener or advertisement setting you changed if the previous endpoint worked. Preserve the failed attempt log for support; do not disable Java authentication or reinstall Floodgate to diagnose a missing network path.

CloudExa game panel network allocations — The CloudExa Network page lists assigned allocations; configure the relevant listener separately in the plugin.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report