Connect managed Bedrock rejects current client as “Outdated Geyser proxy”

[zokanzi]

Hi,

I’m testing Minekube Connect managed Bedrock support on a Paper server. The Connect plugin starts successfully and the endpoint is reachable, but a current Bedrock client is rejected by the Connect edge with an outdated Geyser proxy error.

Endpoint: corny-carlie.play.minekube.net
Connector: Paper/Spigot Connect plugin
Plugin version shown in server log: v0.15.9
Backend: Paper server
Join address tested: corny-carlie.play.minekube.net
Bedrock port: 19132

The exact client error is:

Outdated Geyser proxy! This server supports the following Bedrock versions: 26.0, 26.1, 26.2, 26.3, 26.10, 26.20, 26.21, 26.22, 26.23, 26.30, 26.31, 26.32, 26.33, 26.34, 26.40

The Connect plugin itself appears healthy. Relevant startup log:

[connect] Enabling connect v0.15.9
[connect] Endpoint name: corny-carlie
[connect] Your public address: corny-carlie.play.minekube.net
[connect] Started watching for new player sessions

I also have a separate self-hosted Geyser/Floodgate installation on the backend, but I understand from the Connect documentation that Bedrock clients joining through the Connect endpoint are translated at the Connect edge and should not depend on the backend Geyser installation.

Could you please check whether the managed Bedrock edge serving this endpoint is running an outdated GeyserLite/Geyser build, or whether the latest Bedrock protocol has not yet been deployed to the Connect network?

My goal is to use the Connect endpoint/custom domain with the standard Bedrock port 19132, while keeping my existing backend Geyser installation unchanged.

Thanks.

[zokanzi]

@robinbraemer Could you please confirm whether this is a known deployment issue on the managed Connect Bedrock edge?

Endpoint: corny-carlie.play.minekube.net

The edge currently rejects the latest Bedrock client with:

Outdated Geyser proxy

and reports support only up to Bedrock 26.40.

The Connect plugin itself is running normally (v0.15.9), so this appears to be an edge-side protocol mapping/version issue.

Is there an ETA for deploying the current Bedrock/Geyser protocol mappings to the managed Connect network, or can this endpoint be reassigned to an updated edge node?

[Icatgamer]

help me
[07:19:16 INFO]: [Geyser-Spigot] Bedrock user with ip: /5.106.25.197 has disconnected for reason Outdated Bedrock client! This server supports the following Bedrock versions: 26.0, 26.1, 26.2, 26.3, 26.10, 26.20, 26.21, 26.22, 26.23, 26.30, 26.31, 26.32, 26.33
pls help to dawnload and config to fix geyser

[robinbraemer]

Hey we will get this fixed asap