ViaBackwards
ViaBackwards copied to clipboard
Secure profile is really wonky with ViaBackwards (some dont have issue, others do)
'/viaversion dump' Output
https://dump.viaversion.com/e57077c1c31d9fcfdab6f50aac6cb73447231ec7f098a9dbd5832f2dc57076ef
Console Error
[21:22:47 INFO]: com.mojang.authlib.GameProfile@babd3b3[id=ef62aae1-fd90-4451-963a-11aa57f460bc,name=thecta,properties={textures=[com.mojang.authlib.properties.Property@6ff8c282]},legacy=false] (You cannot have my user's IP) lost connection: Internal Exception: com.mojang.authlib.minecraft.InsecurePublicKeyException$InvalidException: Invalid profile public key signature
Bug Description
Some players using the intended client for my server cannot connect due to invalid profile public keys, despite me disabling enforce-secure-profile beforehand! This should NOT be happening! What is going on?
Steps to Reproduce
- Add ViaBackwards on a 1.19.1 server
- Log in on 1.19
- Pray that this error happens
- You fail to connect, with "Invalid profile public key signature"
- Cry (As there is NO fix)
Expected Behavior
All players are able to join on 1.19
Additional Server Info
Currently using velocity with force-key-authentication = false
Checklist
- [X] Via plugins are only running on EITHER the backend servers (e.g. Paper) OR the proxy (e.g. BungeeCord), not on both.
- [X] I have included a ViaVersion dump.
- [X] If applicable, I have included a paste (not a screenshot) of the error.
- [X] I have tried a build from https://ci.viaversion.com/ and the issue still persists.
Please try the latest build(s) from https://ci.viaversion.com/
:thonk: I literally pulled from actions a few minutes ago.
https://dump.viaversion.com/9928cd9cce25726b6dc084b321ce23b115f83ef20cb8a02f0f29823de7ba68bc
From our discord's pins via #support:
To resolve the "Missing profile public key" issue:
-
You need to disable
enforce-secure-profilein server.properties file via 1.19.1 or later backend server(s), -
If you have velocity as your proxy; ensure that
force-key-authenticationis disabled in the velocity.toml file, (+ Please try Legacy Forwarding if modern fails) -
Whenever the "Chat messages can't be verified" toast appears after disabling both, ViaVersion will be unable to remove this as this is an client-side issue - to counter this; you must install a mod that suppresses the toast itself. (Fabric / Quilt servers with the Sinply Chat Reports mod installed will be your best option)
Related to #487
From our discord's pins via #support:
To resolve the "Missing profile public key" issue:
- You need to disable
enforce-secure-profilein server.properties file via 1.19.1 or later backend server(s),- If you have velocity as your proxy; ensure that
force-key-authenticationis disabled in the velocity.toml file, (+ Please try Legacy Forwarding if modern fails)- Whenever the "Chat messages can't be verified" toast appears after disabling both, ViaVersion will be unable to remove this as this is an client-side issue - to counter this; you must install a mod that suppresses the toast itself. (Fabric / Quilt servers with the Sinply Chat Reports mod installed will be your best option)
Invalid. This isn't the issue I'm happening. PLUS I already tried that.
Closing this as the fix has been long merged.