Geyser Users stuck on "Locating server"

[AceSurvival]

Describe the bug

Geyser users on all platforms are stuck on "Locating server" On latest version.

To Reproduce

Logging in. play.acemc.co to see what im referring to. Bedrock can no longer connect

Expected behaviour

To fully log in....

Screenshots / Videos

Server Version and Plugins

Velocity Build 357.

Geyser Dump

https://dump.geysermc.org/gXfyL0d4FZvWceNDjXmKy1ONuqOxNVue

Geyser Version

429

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

https://dump.geysermc.org/CCgA10KqhEr5xZTrjMw1LWtjpBLQjWad

All bedrock players were able to log in before the latest update.

[onebeastchris]

Please turn on debug-mode in Geyser's config, and send a full log via mclo.gs. Additionally:

• please try using paper instead of a paid spigot fork
• try shortening your motd's - there've been issues in the past where it being too long was able to cause issues.

@LUIS9799 bumping issues without contributing more information isnt of much help - at the very least, provide a geyser dump/logs to show what kind of setup you have.

[AceSurvival]

https://mclo.gs/mPGhJCR

here is the log with debugging on.

[onebeastchris]

The geyser dump you sent before indicates that you have Geyser installed on the backend servers. Remove Geyser from those servers, and only keep it on the proxies - as mentioned in the Geyser setup guide. Further, do you see anything in the server log when you're trying to connect with a client that's then stuck on "locating server"?Your log showed a geyser player connecting to the server.. but no other connection attempts

[AceSurvival]

Will remove right now. Do I keep or remove floodgate from backend servers as well?

"Your log showed a geyser player connecting to the server.. but no other connection attempts" Thats all it does. they physically log in, but they dont get past the locating server screen. Eventually they log out as it never loads.

[onebeastchris]

Having floodgate installed on all backend servers is fine, even recommended. I've just tried joining myself for testing; it looks like the client downloads resource packs fine but isn't able to join afterwards. Could you check if a client can join without the resource packs?

[AceSurvival]

Thank you. It's weird, it was all working prior to the 1.20.60 update.

Anyway, about to reboot. Changed resource pack forcing for geyser to false, and also removed geyser from backend servers.

[AceSurvival]

Joining works without the resource pack. Does something need to be updated? As I didn't have this issue prior to the latest 429 update.

[onebeastchris]

1.20.60 did change some things for custom items such as e.g. removing some item components. As for resource packs specifically - no idea.

I'd recommend removing parts of the resource pack, and then see when it starts working - maybe using a binary search.

[FantasyGirl1988]

On my Server is the same i use Bungeecord and the version 1.19.2 with via version

So i hope you can help me

[onebeastchris]

@FantasyGirl1988 you're getting a Connection Closed error - and judging by the Downstream packet error, you need to update BungeeCord and potentially ViaVersion. It however is unrelated to the issue described here.

[FantasyGirl1988]

@FantasyGirl1988 you're getting a Connection Closed error - and judging by the Downstream packet error, you need to update BungeeCord and potentially ViaVersion. It however is unrelated to the issue described here.

But can i use my 1.19.2 server then?

[onebeastchris]

Even if your server isn't on 1.20.4, you still need to use the latest version of BungeeCord. Additionally, you'll need to update/install Viaversion so 1.20.4 clients - which is what Geyser currently imitates - can join.

[onebeastchris]

Closing as the issue appears to be resolved - this seems to have been caused by a resource pack, not Geyser itself.