WEB-7591Cannot Whitelist Players - 403 Forbidden error
When trying to whitelist players, the server returns back a 403: Forbidden error. This behaviour can also be observed if we send a cURL request to the API directly. This is running with a standard server jar downloaded from https://minecraft.net/download/server and ran according to the instructions there.
Notably, this problem does not occur if the player has previously joined the server.
See the images attached for further details.
Linked Issues
MC-279558
NormalCreated Issue:
Cannot Whitelist Players - 403 Forbidden error
When trying to whitelist players, the server returns back a 403: Forbidden error. This behaviour can also be observed if we send a cURL request to the API directly. This is running with a standard server jar downloaded from https://minecraft.net/download/server and ran according to the instructions there.
Interestingly, this problem does not occur if the player has previously joined the server.
See the images attached for further details.
Attachments3
When trying to whitelist players, the server returns back a 403: Forbidden error. This behaviour can also be observed if we send a cURL request to the API directly. This is running with a standard server jar downloaded from https://minecraft.net/download/server and ran according to the instructions there.
Interestingly, this problem does not occur if the player has previously joined the server.
See the images attached for further details.
When trying to whitelist players, the server returns back a 403: Forbidden error. This behaviour can also be observed if we send a cURL request to the API directly. This is running with a standard server jar downloaded from https://minecraft.net/download/server and ran according to the instructions there.
Notably, this problem does not occur if the player has previously joined the server.
See the images attached for further details.
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
![[Mojang] Web Team](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Web Team![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
is duplicated by
relates to
is duplicated by
WEB-7680
Thank you for your report!
We're tracking this issue in WEB-7591, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I'm unable to replicate this. Please see if this is still an issue for you.
If it is, please attach a video showcasing this, and please try using a mobile hotspot and switching DNS
I did as you suggested and tried changing my DNS settings- I changed from the default ones my ISP assigns to Cloudflare's 1.1.1.1 DNS, After a full restart and ensuring the new DNS is being utilized, the issues are still occurring.
If this is a network issue it's a very peculiar one as I've tried it on my home network as well as mobile hotspot.
Attached is a recording of my terminal running the vanilla server and attempting to whitelist a few different people, after that fails I run a command to show the DNS server being utilized, just to confirm I'm using the right one, and finally I tried again with a cURL request, which failed as well.
Screencast 2024-12-12 15_22_37.mp4
I was able to replicate this when attempting to run /whitelist add on a player, I have also had issues with the bulk endpoint starting around the time of 1.21's release through modded server plugins calling it for name lookups, it gives a 403 fairly consistently (though not always). Interestingly, I have not had issues with the non-bulk endpoint. I am guessing some sort of WAF rule being too strict. Requests are being made from a datacenter in Virginia:
I was able to replicate this too. running the newest version 1.21.4. No mods no plugin system pure vanilla and i get:
Have the same issue on a fresh server and when attempting to run a spigot server. I simply downloaded the jar and ran it, nothing else is added so this issue is still going on.
Have the same issue, fresh server:
Will add that occasionally it worked after insisting, but maybe 1 out of 30 times on average, and that was yesterday, today it doesn't seem to be working at all.
I too am experiencing this issue today. It works on my home internet but on my AWS server I just get the response:
My server is not going above the rate limit, I've double checked. I've also cross referenced via another DB (https://api.ashcon.app/mojang/v2/user/) and they too receive a 403 for usernames that they haven't cached.
Edit: Username also shows up as "Available" on namemc.com, so I assume they are getting a 403 as well and therefore are just returning the result as not found and thus available.
We're experiencing this as well when hitting api.mojang.com from AWS Lambda
Ran into this as well, attached are screenshot and a copy of the HAR of the request.
har.json
Same problem since early yesterday afternoon (GMT time), either on my servers (Hetzner) or directly from my personal connection
403 errors on: https://api.mojang.com/users/profiles/minecraft/SiriHack
We are currently working on implementing an appropriate rate limit rule for the old Mojang API to ensure our servers are not strained by scanning traffic. At the same time, we want to ensure this does not impact legitimate traffic. We are aware of the issue and investigating it.
In the last 24 hours the API uptime was at 38.66% with 148ms average response time. This is really bad. Please roll back your experimental constraints and implement a proper rate limiting process before deploying this on your production servers.
+1 on the issue, the fact this change hasn't been reverted already is appalling.
[21:25:20 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>
[21:25:21 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>
[21:25:22 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>
[21:25:22 INFO]: That player does not exist
---
Paper server 1.21.4
—
Intermittent issue and rate limited? I was able to whitelist shortly after making my comment.
same thing here and still going: