Skip to content
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

Bedrock can't connect to Velocity when force-key-authentication=true #3019

Closed
seb303 opened this issue Jun 8, 2022 · 7 comments
Closed

Bedrock can't connect to Velocity when force-key-authentication=true #3019

seb303 opened this issue Jun 8, 2022 · 7 comments
Labels
Confirmed Bug The bug reported is confirmed and able to be replicated.

Comments

@seb303
Copy link

seb303 commented Jun 8, 2022

Describe the bug

When Velocity is configured with force-key-authentication = true (the default setting), Bedrock clients are unable to connect.

[11:49:14 INFO] [geyser]: /<ip-address>:58822 tried to connect!
[11:49:15 INFO] [geyser]: Player connected with username seb30303
[11:49:15 INFO] [geyser]: seb30303 (logged in as: seb30303) has connected to the Java server
[11:49:15 INFO] [floodgate]: Floodgate player who is logged in as .seb30303 00000000-0000-0000-0009-01f65009eec0 joined
[11:49:15 INFO]: [initial connection] /<ip-address>:0 has disconnected: multiplayer.disconnect.missing_public_key
[11:49:15 INFO] [floodgate]: Floodgate player logged in as seb30303 disconnected
[11:49:15 INFO] [geyser]: seb30303 has disconnected from the Java server because of Missing profile public key.
This server requires secure profiles.

This is using latest Geyser (#1108), Floodgate (#65) & Velocity (3.1.2#147)

To Reproduce

  1. Install Geyser-Velocity & floodgate-velocity with velocity-3.1.2-SNAPSHOT-147 with default Velocity settings
  2. Connect with Bedrock 1.19 client

Expected behaviour

It should work with force-key-authentication=true as this is needed for Java clients to securely authenticate.

Screenshots / Videos

No response

Server Version and Plugins

Velocity 3.1.2#147
Geyser #1108
Floodgate #65
ViaVersion-4.3.1
ViaBackwards-4.3.0

Geyser Dump

https://dump.geysermc.org/clNSSOPHicvZ1d8ipGRFRvIEgDjONToP

Geyser Version

2.0.4-SNAPSHOT (git-master-78bb69b)

Minecraft: Bedrock Edition Device/Version

1.19 Windows 10

Additional Context

No response

@Camotoy
Copy link
Member

Camotoy commented Jun 8, 2022

It should work with force-key-authentication=true as this is needed for Java clients to securely authenticate.

This is incorrect - the key is currently only used to validate that chat messages were written by the player.
In any case, Velocity having this enabled and Floodgate being unable to work with this is something of a bug we're aware of.

@Camotoy Camotoy added the Confirmed Bug The bug reported is confirmed and able to be replicated. label Jun 8, 2022
@Noorquacker
Copy link

Hi, where is the config option for force-key-authentication? I couldn't find this in Velocity's config

@PureGero
Copy link

PureGero commented Jun 9, 2022

Hi, where is the config option for force-key-authentication? I couldn't find this in Velocity's config

You need to add the option to the velocity.toml yourself. It goes under the offline-mode as so:

# Should we authenticate players with Mojang? By default, this is on.
online-mode = true

# Should the proxy enforce the new public key security standard? By default, this is on.
force-key-authentication = true

@Noorquacker
Copy link

Thank you! Sadly it's breaking java users for me, so I might just go without Geyser for now 😔

@Camotoy
Copy link
Member

Camotoy commented Jun 9, 2022

How is it breaking Java users?

@Noorquacker
Copy link

Ah
It seems another config of mine is breaking Java users as well

@Camotoy
Copy link
Member

Camotoy commented Jun 11, 2022

Floodgate should now deal with this error if you're on the latest Velocity and Floodgate builds.

@Camotoy Camotoy closed this as completed Jun 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Confirmed Bug The bug reported is confirmed and able to be replicated.
Projects
None yet
Development

No branches or pull requests

4 participants