whitelist adds wrong UUID to whitelist.json
heya, i've been having this recurring issue on all of my servers where adding someone via the /whitelist command adds the right username, but the wrong UUID, to the server's whitelist.json file. they are all paper servers tied to a proxy. the only solution is to update the whitelist.json with the right uuid, and then restart the server, which takes time and is an unnecessary amount of work as startup takes a while.
how can i fix this issue so it adds the right UUID to whitelist.json?
20 Replies
btw this is NOT a cracked server, though our proxy does support bedrock w/ geyser
can you show one of the uuids it adds? remove the last like 4 letters
"eb7af4c6-d72e-3cff-acdd-66d8d23595f0"
thats someone i tried to whitelist just now
their actual uuid is:
"37797aa3-85c4-444c-bfb1-9a848b9e9907"
but this is what was added to the json file
this is their uuid v3 (name based uuid) due to it being offline-mode
is proxy doing proper authentication
i really hope so
i mean cracked players have never been able to join and everythings always been fine proxy wise
how can i check if proxy is authenticating properly?
using velocity btw
and proxy has online-mode set to true
what mode is backend set to
modern, legacy etc
modern
hmm
in paper-global.yml
is it set to online-mode
next to velocity
of the individual servers?
and i believe its like this for all the servers
needs to be true
which one?
online-mode on velocity
in paper-global.yml
gotcha yeah, did it a bit ago and seems to have fixed the issue
thanks a lot