Kottizen

Thank you for testing and sharing your results!

Glad to hear it seems to be working better! We have done a major rework of the backend layer serving skins, including the cache. If you are able to repeat your test in about a week's time and share your results here in the bug tracker, that would be much appreciated.

Thank you for running the commands and providing screenshots of the output. The error message you received when using Invoke-WebRequest on sessionserver.mojang.com is expected, as the status code of that request is 4xx. You did receive a reply ({ "path": "/" }), which looks promising.

At the time of running the command, were you able to connect to a Minecraft server? If no, could you please run the command again as soon as you notice that you aren't able to connect to a Minecraft server? If yes, could you please open a ticket with customer support in which you reference this bug ticket, and provide the publicly facing IP address that you are using? You can use e.g. https://ifconfig.me/ to find out your publicly facing IP address.

If you don't have curl on your system, and/or if you prefer to use PowerShell, could you please try with Invoke-WebRequest?

Thank you! Are you sure that it is authserver.mojang.com that is the issue for you? Could it be sessionserver.mojang.com instead? If you have a recent version of Windows, curl might be available. Could you please try this?

$ nslookup sessionserver.mojang.com
$ curl -v 'https://sessionserver.mojang.com'

Can you please visit http://s3.amazonaws.com/aws-cloudfront-testing/JsCustomerTesting.html, enter 11162901711 as "Optional reference ID", push the "Test" button and reply to me with the response header ("More Details")? If you feel uncomfortable sharing those details in this bug tracker, feel free to send me an e-mail message at [email protected].

Thank you for the update and for the screenshots. We are actively looking into this.

If you try now again, does it work? Regardless of if it works or not, can you please run

$ nslookup authserver.mojang.com

in a terminal emulator of your choise again and give us the results?

Thank you for providing an example, @unknown. We are still working on resolving that issue, which is referenced as WEB-4566 in this bug tracker.

I think we are talking about two different issues that have resulted in some skins being unavailable. This issue, about a sudden disappearance of skins, has been resolved. The other issue, WEB-4566, about skins that come and go due to caching, has not yet been resolved. Rest assured we are working on sorting that out!

This has been resolved. All skins should now be available through http(s)?://textures.minecraft.net/texture/[...] again.

The logo images have been adjusted.

Other issues have had a higher priority, which is why this issue has not yet been resolved. The plan is to have this fixed at latest by 31 December 2022.

Thank you. The certificate has now been updated, as well as the link in the footer of this bug tracker.