Closed Ahptt closed 1 year ago
I'm also having the issue.
I found out that the request to playerdb.co
fails for some users on my server, not all:
if ! playerData=$(get "https://playerdb.co/api/player/minecraft/$i" | jq -re ".data.player"); then
log "WARNING: Could not lookup user $i for ${output} addition"
else
playerDataList=$playerDataList$(echo "$playerData" | jq -r "$userData")
fi
Therefore the error handling here is maybe not sufficient.
@Cherry, just wanted to let you know that users here are getting 429's (too many requests) from your service.
@apfohl agreed in principle, something should be improved on error handling, but 429's are a little tricky:
@Cherry, just wanted to let you know that users here are getting 429's (too many requests) from your service.
Yeah 😢 Mojang are heavily rate limiting requests right now, and PlayerDB uses Cloudflare Workers so all of the requests come from the same IP. We're in contact with Mojang and are trying to find a solution that'll work for everyone, and are also looking at hosting a few instances elsewhere to utilize more IPs, but for the time being we're seeing an increasing number of 429s unfortunately.
Thanks for the super quick reply @Cherry . If you don't mind, can you post an update here as appropriate?
Absolutely, I'll be sure to update here as soon as I have anything additional to share. Sorry for any inconvenience folks are experiencing because of this - it's impacting some of our internal tools too so we know the pain 😅
We've made some changes which should drastically reduce the number of 429s seen for the time-being. We're continuing to try and work with Mojang to find a long-term solution.
@Cherry I have been getting several reports over last few days of 429 responses. One was to https://playerdb.co/api/player/minecraft/GnU , if that helps.
Apologies for this, we've too been seeing the increase in 429s recently and are working to resolve it. The rate limits Mojang have in place are making this harder and harder 😢
We've made some more changes that'll improve things again. Hopefully this will help a lot moving forward, thanks for your patience. #2342 seems like a great addition too!
Describe the problem
My docker-compose.yml was working on 1.19.2. Upon attempting to update to version 1.19.3, I receive an error with docker adding users to the whitelist. I tried again on 1.19.2 after discovering this and the whitelist fails to compose properly. I do use a firewall, but I've verified that there isn't anything being blocked, and per the error message, it seems that I'm sending too many requests?
Container definition
Container logs