Closed TechClusterHQ closed 7 months ago
Thanks for the report. I couldn't reproduce this myself, but I'd like to help debug. I didn't try your start script exactly, but it looks good at first glance. The Drasl config looks correct also.
FallbackAPIServers
? i.e. can you create the user in Drasl and still get a 404 from Drasl?curl --verbose -X POST https://drasl.XXX/profiles/minecraft -d '["myusername"]' -H 'Content-Type: application/json'
or to Mojang:
curl --verbose -X POST https://api.mojang.com/profiles/minecraft -d '["myusername"]' -H 'Content-Type: application/json'
But I think 1.20.4 still uses the old route, so I'm not sure this is the problem.
Ah, no, it looks like the route was changed in 1.20.3, so I bet that's it.
v1.0.3 did indeed fix it! I totally forgot about this change, thanks for implementing it!
I am unable to whitelist players that have never joined the server and am getting the error "That player does not exist". I can see in the Drasl logs that it indeed returns a 404 for the player. If I disable the whitelist then I can join just fine. This is my Drasl config (url changed):
I am using the fabric server version 0.15.10 with MC 1.20.4, launching using Aikar's flags. Start script:
Mods: NoChatReports (same problem occurs without it as well)
enforce-secure-profile is currently set to false, but changing it to true does not fix the issue.
Is this a known issue with whitelist or is my config not set up properly? Thanks!