#End of stream

5 messages · Page 1 of 1 (latest)

atomic cloud
#

https://dump.geysermc.org/TiRwSGm2eIwxBADHyocWIajOCaPTnbvM

Currently, I have installed GeyserMC and Floodgate on Velocity, and Floodgate on Paper, but there is an issue with connections.

The current setup is as follows:

  • Velocity: running on Pterodactyl Panel Wings
  • PaperMC: running on Pterodactyl Panel Wings, version 1.21.11

For Floodgate, send-floodgate-data: true is enabled, and the key.pem file is the same on both Velocity and Paper.

Things I have tried

  • Connecting to the server using a Java Edition client (this worked without any problems)
  • Running Geyser connectiontest ~~~~ (it reported online)
  • Changing use-direct-connection between true and false
  • Removing other plugins installed on Velocity

There are no related connection logs on the PaperMC side.

My Bedrock client IP is 100.xxx.xx.xxx:54455.

Below is the log when use-direct-connection: false.

The [servers] configured in velocity.toml uses addresses starting with 100.xxx...

[09:46:16 INFO] [geyser]: /100.xxx.xx.xxx:54455 tried to connect!
[09:46:17 INFO] [geyser]: Is player data signed? true
[09:46:17 INFO] [geyser]: Could not find packet for ClientToServerHandshakePacket
[09:46:17 INFO] [geyser]: Could not find packet for ClientCacheStatusPacket
[09:46:17 INFO] [geyser]: Player connected with username Nishi5011 (924)
[09:46:17 INFO] [geyser]: Nishi5011 (logged in as: Nishi5011) has connected to remote java server on address 172.18.0.2
[09:46:17 INFO] [geyser]: Downloading and loading locale: ja_jp
[09:46:17 INFO] [geyser]: Locale already downloaded and up-to date: ja_jp
[09:46:17 INFO] [geyser]: Nishi5011 has disconnected from remote Java server on address 172.18.0.2 because of End of stream
autumn thicketBOT
late heath
atomic cloud
#

I will test with Velocity 3.4.x and report back.

atomic cloud
#

Sorry about that. It turned out to be just a mistake in my configuration.

I was using haproxy-protocol on Velocity, but at some point the proxy-protocol related settings on the Geyser side had changed. I had simply forgotten to enable the setting java.use-haproxy-protocol: true.

After enabling that option, the issue was resolved.