Downstream packet error! Invalid packet id: 25 & more

Describe the bug

I am on Velocity 1.1.0-SNAPSHOT and Paper 228. Geyser is installed on Velocity. Floodgate is installed on both Velocity and Paper. This bug occurs when a Bedrock player attempts to connect to the Velocity proxy. The player connects without anything loaded for a split second, and then disconnects with “Connection closed.” message.

Here is a full log of the error on Paper: https://paste.mod.gg/sadecefuha.md.

The Geyser plugin on Velocity spits this out:

[15:00:51 INFO] [geyser]: Attempting to login using floodgate mode... authentication will be encrypted.                                     
[15:00:51 INFO] [geyser]: Loaded Floodgate key!
[15:00:52 INFO] [geyser]: Kot9744 (logged in as: Kot9744) has connected to remote java server on address 127.0.0.1                          
[15:00:53 WARN] [geyser]: Downstream packet error! Invalid packet id: 25                                                                    
[15:00:53 INFO] [geyser]: Kot9744 has disconnected from remote Java server on address 127.0.0.1 because of Connection closed.               
[15:00:53 INFO] [geyser]: Bedrock user with ip: /MY-IP has disconnected for reason CLOSED_BY_REMOTE_PEER

To Reproduce

I have not tried to reproduce this bug, but it is fairly straightforward TMK.

1. Download Velocity
2. Download Paper
3. Install Geyser and Floodgate on Velocity.
4. Install Floodgate on Paper.
5. Configure both instances to use Floodgate. Copy the private keys to the floodgates, and the public key to Geyser.
6. Attempt to connect using a Bedrock client.

Expected behavior

The user can connect to the server.

Server Version

Velocity: Velocity 1.1.0-SNAPSHOT (git-3b1009ca-b262) Paper: This server is running Paper version git-Paper-228 (MC: 1.16.3) (Implementing API version 1.16.3-R0.1-SNAPSHOT)

Geyser Version

Geyser is on version 1.1.0. Floodgate is on 1.0-SNAPSHOT I am using Floodgate-Velocity on Velocity, Floodgate-Bukkit on Paper.

Minecraft: Bedrock Edition Version

1.16.40 - I was told there are no protocol revisions between 1.16.2 and 1.16.40.

Additional Context

Here is the Geyser dump. https://dump.geysermc.org/Q6Td3MZ5dLqkxvnBul1fp7UKsvldT93U

[Magi1053]

I can confirm that changing remote address from 127.0.0.1 to auto fixes this issue for me

[Camotoy]

Not quite sure how you got 30066 as a port when your reported Velocity port is 25565, but I assume you tried changing things in an attempt to debug a situation that ultimately was corrupt Floodgate keys after all.