This was already reported and even marked as solved; however, this issue persists until today: WEB-6834
Issue/Bug 1.21.4
When trying to add a new username to the whitelist using the whitelist add [username] command, the output will always be That player does not exist, despite the fact that the account is a valid and active Minecraft account. Additionally, a lot of server admins are reporting random rate limits coming from https://api.minecraftservices.com/minecraft/profile/lookup/bulk/byname when running the whitelist add command.
To Reproduce:
On a server, run the whitelist add command alongside a valid Minecraft account nickname.
Expected Behavior:
If the account is valid, the username and UUID of the account will be added to the whitelist.json file, and the player will be able to join the server.
Actual Behavior:
The result is always an error message: That player does not exist. This command has been tested with multiple valid Minecraft accounts. Additionally, the following response will be printed to the server console:
[19:33:24 ERROR]: Got an error with a html body connecting to https://api.minecraftservices.com/minecraft/profile/lookup/bulk/byname:
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>Microsoft-Azure-Application-Gateway/v2</center>
</body>
</html>Current Workaround:
As of today, the current solution me and other admins have found is to simply run the command again until it recognizes the account or manually adding the username and UUID to the whitelist.json file. This has been an active issue since 1.20.1, and it happens across multiple server forks like Paper or Purpur.
Note:
The rate-limit started happening out of nowhere for many servers after updating to 1.21.4, and it has lasted for over a week. On my personal experience and server, the whitelist command gets ran 1–2 times every 3 days, this shouldn’t trigger any rate limit. Other admins have reported the same issue with even less usage of the command.
Comments 0
No comments.
