-
-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to verify username #3068
Comments
Have done some more testing with relation to this bug. I found that if I set a secondary backend running Fabric / Fabric Proxy Lite then the bedrock client connects to this ok, and from here the client can run the command "/server minigames" (which is the paper server) and they will connect ok. Weirdly, once they have connected to the paper server in this way, they can then connect to the paper server first time, and the error does not re-occur. I've tested this with various combinations of backends with the same exact thing happening each time: Primary backend: paper-1.17.1-411 Primary backend: paper-1.17.1-411 Primary backend: paper-1.18.2-386 |
No
…On Sat, Jun 18, 2022, 2:03 AM seb303 ***@***.***> wrote:
Have done some more testing with relation to this bug.
I found that if I set a secondary backend running Fabric / Fabric Proxy
Lite then the bedrock client connects to this ok, and from here the client
can run the command "/server minigames" (which is the paper server) and
they will connect ok.
Weirdly, once they have connected to the paper server in this way, they
can then connect to the paper server first time, and the error does not
re-occur.
I've tested this with various combinations of backends with the same exact
thing happening each time:
Primary backend: paper-1.17.1-411
Secondary backend: Fabric 1.17.1
Primary backend: paper-1.17.1-411
Secondary backend: Fabric 1.19
Primary backend: paper-1.18.2-386
Secondary backend: Fabric 1.19
—
Reply to this email directly, view it on GitHub
<#3068 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS4BQUTKZU4ROTKPE2UBNGTVPV7DVANCNFSM5ZDLHMQA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Further note: the trick of joining a Fabric backend first, and then switching to the Paper backend, seems to only work sometimes. At other times I get the same error when switching to the Paper backend using the /server command. If I retry then it eventually connects and afterwards can connect to the Paper backend every time (at least for a few hours anyway). |
Is Floodgate present on the backend server / do you have |
Ah that might well be the problem. We used to have Floodgate on the backend but removed it as it didn't seem to do anything. But we hadn't set send-floodgate-data back to false. Have done this now and will see if the problem persists. Thank you! |
Setting send-floodgate-data false fixed the issue :) |
i also have this issue |
https://wiki.geysermc.org/floodgate/issues/#failed-to-verify-username-with-paper |
Describe the bug
Connecting bedrock client via Velocity proxy to 1.17.1 Paper server no longer works with latest Geyser/Floodgate.
Client reports "Failed to verify username"
Velocity logs show:
Paper logs show:
To Reproduce
velocity-3.1.2-SNAPSHOT-153
Geyser 2.0.4-SNAPSHOT (git-master-71c489b)
Floodgate 2.2.0-SNAPSHOT (b70-6e2c19f)
ViaVersion 4.3.2-SNAPSHOT
ViaBackwards 4.3.1-SNAPSHOT
Expected behaviour
This used to work very recently until updating to latest versions.
The exact same Velocity setup works fine to connect to a Fabric 1.17.1 backend using Fabric Proxy Lite.
Screenshots / Videos
No response
Server Version and Plugins
velocity-3.1.2-SNAPSHOT-153
Geyser 2.0.4-SNAPSHOT (git-master-71c489b)
Floodgate 2.2.0-SNAPSHOT (b70-6e2c19f)
ViaVersion 4.3.2-SNAPSHOT
ViaBackwards 4.3.1-SNAPSHOT
git-Paper-411 (MC: 1.17.1) (Implementing API version 1.17.1-R0.1-SNAPSHOT) (Git: 6625db3 on ver/1.17.1)
Geyser Dump
https://dump.geysermc.org/IPstrVSgtlvEWwPNWQERgtJVDlvFrU9j
Geyser Version
2.0.4-SNAPSHOT (git-master-71c489b)
Minecraft: Bedrock Edition Device/Version
Minecraft for Windows
Additional Context
No response
The text was updated successfully, but these errors were encountered: