https://errors.yoctoproject.org : " This site can’t be reached errors.yoctoproject.org unexpectedly closed the connection. " Not sure if it should use https but it wouldn't hurt to support it: I spent a few minutes wondering why the site won't load...
As far as I know errors.yoctoproject.org has never been available via https://. It doesn't appear that the site requires TLS for any reason. Can you provide more information about the reason for trying to connection via https?
If it's just to support https everywhere I think that's a fine reason and will plan for it but if there is a specific need I'd like to know.
(In reply to comment #1) > Can you provide more information about the reason for trying to connection > via https? I didn't even realize it was https until after a little debugging. I just tried to load errors.yoctoproject.org and got an undecipherable error message... Why the browser decided to use https I don't know. Maybe I had another yoctoproject.org URL open and just edited the URL? I filed a bug since Joshua asked me to, maybe wouldn't have otherwise.
I wasn't sure if errors.yp.o had ever been available via https. I think it's a good goal to have https everywhere at some point but far from our sysadmin priority.
This is most likely due to a typo in Yocto SWAT wiki page: https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team which provides a link to https://errors.yoctoproject.org (Corrected to http:// now)
(In reply to comment #5) > This is most likely due to a typo in Yocto SWAT wiki page: > https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team > > which provides a link to https://errors.yoctoproject.org (Corrected to > http:// now) My fault, thanks for fixing the link!
https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ is available now thanks to LetsEncrypt.