mojira.dev

hmc

Assigned

No issues.

Reported

WEB-7039 Too many requests - 429 errors, when limit was not exceeded Awaiting Response WEB-6617 The request is blocked Invalid WEB-6270 Wrong uuid and null name Works As Intended MC-256456 Slow/failed server list ping/refreshing, connecting also is slow Awaiting Response WEB-5999 Expected HTTP response 200 OK, got 503 Service Unavailable Duplicate WEB-5994 Many 500 error codes Awaiting Response WEB-5980 API returns 429 even when there is no rate limit Cannot Reproduce WEB-5959 Mojang API returns errors Works As Intended WEB-5958 Increase Mojang API rate limit Duplicate MC-254196 Increase Mojang API rate limit Duplicate MC-253198 Slow rendering of entities Incomplete MC-253197 Slow rendering of text Duplicate MC-253196 Slow rendering of chat Duplicate MC-253195 Slow rendering of nametags Duplicate MC-253194 Slow rendering of scoreboard/sidebar Duplicate MC-253193 Slow rendering of status bar Duplicate MC-253192 Slow rendering of hotbar Duplicate MC-252351 Slow rendering of hotbar, status bar, scoreboard, nametags, chat, text and entities Invalid MC-203052 1.16 or lower versions have disadvantage from players on 1.8 with higher/lower version Invalid

Comments

This 429 error I didn't see today, but there were some time outs or different errors. It may not happen today, but maybe it will happen again.

Even with only 1 request made in last 10 minutes, you can get 429 error. You can use bulk api to get up to 10 names at once, but this is global error with api going for at least couple of days.

? It is visible even in the browser.

I think it was random bug.

Do you want to wait 24 hours for your server to be playable?

Now may be working, but what's the reason there are problems with it? It should be stable.

Yes, I sometimes see 500 and 503 error codes.

It was a different issue.

I don't know if you have an idea of what you are talking about, but I pointed that rendering entities is slow, there is also screenshot from the profiler showing which parts are lagging. If ever developer responsible of any optimizations will see that, he will know what to do.

You have profiling report and description, what else is needed?

How is it resolved?

Right now the api is down again.

{"error":"Internal Server Error","errorMessage":"The server encountered an unexpected condition which prevented it from fulfilling the request"}

Around 17:00 CET whole api went down, sessionserver, api.mojang.com

Around 17:00 CET whole api went down, sessionserver, api.mojang.com

I don't.

This is the same for https://sessionserver.mojang.com/session/minecraft/hasJoined?username=

It can repeat and happen and different times.

We use this link https://api.mojang.com/users/profiles/minecraft/Notch with different names.

Steps to Reproduce:
1.  Reach https://api.mojang.com/users/profiles/minecraft/ + Notch or different name
2. At the same time reach https://api.mojang.com/users/profiles/minecraft/ + Notch or different name

Observed Results:
There is a chance that you will get 429 respones code.

Expected Results:
I would love to see increased rate limit, some way to avoid the errors or no 429 errors.

This is the same.