Closed aimattoff closed 2 years ago
Can you share your full server logs by uploading to https://mclo.gs and pasting the link here?
immediately after the geyser fell, I turned off the server *
the player who did badly to the server said that because of one query ping on the udp port is enough to put the Geyser. can you check this information with yourself?
Not much we can do with the information provided, so will close this. If anyone has updated replication steps or encounters this issue, please open a new issue.
Describe the bug It appears that when someone is trying to ping a geyser server through UDP port it becomes completely unresponsive in Minecraft Bedrock until whole server is restarted.
To Reproduce
Expected behaviour Server continues to work and replies to ping packet accordingly.
Screenshots / Videos
Server Version and Plugins 1.17.1(Java), 1.17.10(Bedrock) LuckPerms, ProtocolLib, Themis, Geyser-Spigot, Vault, dynmap, WorldEdit, PlayerKits, Essentials, AdvancedBan, WorldBorder, WorldGuard, Citizens, AuctionHouse, EssentialsProtect, EssentialsChat, NexEngine, EssentialsSpawn, CMILib, Towny, SmallPets, Jobs, TownyChat, NexAuth, Dynmap-Towny
This server is running CraftBukkit version 3210-Spigot-18c71bf-e1c96e5 (MC: 1.17.1) (Implementing API version 1.17.1-R0.1-SNAPSHOT)
Geyser Dump https://dump.geysermc.org/9ensaNdRnpyiqsH7un7YETKHYpoNqgCD
Geyser Version This server is running Geyser version 1.4.1-SNAPSHOT (git-master-3eb73a5) (Java: 1.17.1, Bedrock: 1.17.0/1.17.1/1.17.2 - 1.17.10)
Minecraft: Bedrock Edition Version 1.17.10
Additional Context
Update: Server log: https://mclo.gs/G0xN0ZH