Skip to content

fix(paper,paper-gamemode): authenticate against Mojang directly#107

Merged
hbrombeer merged 1 commit intomainfrom
fix/paper-online-mode
May 6, 2026
Merged

fix(paper,paper-gamemode): authenticate against Mojang directly#107
hbrombeer merged 1 commit intomainfrom
fix/paper-online-mode

Conversation

@hbrombeer
Copy link
Copy Markdown
Member

Servers shipped with online-mode=false + Velocity-modern-forwarding-enabled, but there's no Velocity proxy in the architecture (mc-router is just SNI relay). Result: offline-mode UUIDs that don't match the Mojang-resolved whitelist. Flip both to direct Mojang auth.

Both images shipped with online-mode=false + Velocity-modern-
forwarding enabled — a config that only makes sense behind a
Velocity proxy that does the auth and signs the player profile.
There's no Velocity in the architecture: mc-router handles fan-out
via raw TCP/SNI relay, no protocol-level auth. So Paper saw the
client directly, computed an offline-mode UUID via
nameUUIDFromBytes("OfflinePlayer:<name>"), and that didn't match
the Mojang-resolved UUID we whitelisted. Players got "You are not
whitelisted on this server!" even though they were in the list.

Flip both images to authenticate directly:
  - server.properties online-mode=true
  - paper-global.yml proxies.velocity.enabled=false

If we later add Velocity for hub/queue/cross-server features,
revisit — modern forwarding wants this exact reverse pair.
@hbrombeer hbrombeer merged commit 82290fa into main May 6, 2026
6 checks passed
@hbrombeer hbrombeer deleted the fix/paper-online-mode branch May 6, 2026 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant