#403 response from UUID lookup

1 messages · Page 1 of 1 (latest)

midnight notch
#

I have a problem with NPC Skins when i try to load skins by their names from Namemc website i get always this type of message. (First Image "Could not load skin from the specified username")

When i try to use a png file i dont get any error but the skin doesnt load it stays the same as i would use @none

Also when i try to reload plugin i get a message saying Server returned HTTP response code: 403 for URL:

And then a red message from the plugin saying there is something wrong with UUID Fetcher or something

Also when i start the server i get this type of yellow message but idk if it is for this plugin or SkinRestorer one

All this happened when i switched from 1.21.4 Folia to 1.21.5 Folia (i Downloaded newest version of plugin for 1.21.5)

Screenshot_7.png Screenshot_8.png Screenshot_9.png
#

I can send full log of the server if needed

spring lodge
#

Linked Mojira issue were commented on recently (today) which would confirm this is a wider issue.

image.png
#

I also get 403 whilst connecting to the API.

[user@void-pc ~]$ curl https://api.mojang.com/users/profiles/minecraft/Grabsky
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>Microsoft-Azure-Application-Gateway/v2</center>
</body>
</html>

Other URL works fine however. But I don't think we can really change it because I think this part is handled by MineSkin Client which we depend on.

[user@void-pc ~]$ curl https://api.minecraftservices.com/minecraft/profile/lookup/name/Grabsky
{
  "id" : "6bd3cf88763545318eb1cfe527c858b8",
  "name" : "Grabsky"
}
spring lodge
#

I was wrong. This request happens in FancyNpcs and not in MineSkin Client, meaning we might be able to fix it by switching from api.mojang.com to api.minecraftservices.com.
I don't know what's the difference between these two, so will ping @dense anchor as he has more knowledge on this topic.

midnight notch
#

Okay, thank you so much for your time 4936peepolove

If there is anything i can provide just let me know

dense anchor
#

Hmm

#

If yes, I can switch to it

#

If that doesn't work, I can make it use MineSkin for username/uuid skins too. I just chose the mojang api for that, because the rate limit was higher

midnight notch
spring lodge
#

I think it's the same, yes

#

403 response from UUID lookup

dense anchor
#

Ok I’m not home today, so I’ll change it tomorrow

dense anchor
#

Dev build is on it's way

#

It should be fixed there

dense anchor
#

It would be great, if you let me know, if it works

midnight notch
#

So sorry i was taking nap after a long day i had today, i will try it and let you know in about 5 minutes or less

#

PNG Files from directory works fine (Fixed)
Skin names through namemc website works fine (Fixed)

And no console errors at all
Thank you so much for your help 4936peepolove

spring lodge
dense anchor
#

Okay cool

#

I'll see if I can fix some other issues tomorrow and then release a hotfix

spring lodge
#

Alright

#

Domain is registered by Microsoft, I verified just to make sure.

dense anchor
#

I wonder if MineSkin also experienced problems, but they probably been using the new url for quite a while already

spring lodge
#

I checked mineskin client repo and could not find it

#

but their backend need to connect to Mojang services so maybe

#

Which, well, could explain some occasional issues

#

(Assuming they use the "outdated" endpoint)

dense anchor
#

Maybe one of them is used as fallback or something

#

And why tf is everyone writing their backend in typescript?