Check the public address Geyser advertises behind container networking

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

The address a game process sees inside its container can differ from the address a player can reach. A correct listening port does not help if signalling sends the client a private, loopback or obsolete public address for gameplay.

Record the starting point

Collect the assigned endpoint from your service details, the Geyser build and the current signalling arrangement. Save the relevant Geyser configuration and any startup properties. Treat a support-provided public address as authoritative over an address guessed from an interface inside the container.

Work through the change

Reproduce a failed Bedrock join from a remote connection and note the address used in the saved entry. Check whether a domain still resolves to a previous service.
Compare the advertised gameplay endpoint described by your installed Geyser release with the public allocation. Read the current NetherNet setup guidance before using startup overrides from an older tutorial.
If an advertisement override is necessary, ask support to confirm the public mapping and supported startup control. Change the advertisement without moving the Java listener or changing the world.
Restart through the panel, refresh the Bedrock server entry, and repeat the remote join. Keep the old and new endpoint values in your change record.

Check the result

The test should reach the same server ID, world and player identity as before while completing negotiation through the assigned public endpoint. Check a second remote client if the first has cached the previous discovery response.

If the result differs

If only one network fails, compare that client's saved endpoint and connection route before changing the server again. If all remote clients receive an unreachable address, send support the advertised endpoint, timestamp and build number with private configuration values removed.

Undo the single advertisement change if it makes discovery fail. Do not replace the allocation with another customer's IP, expose container management ports or copy an unrelated host's startup properties. Preserve the working Java endpoint throughout the investigation.

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