Bug 10837 - errors.yoctoproject.org fails to load with https
Summary: errors.yoctoproject.org fails to load with https
Status: RESOLVED FIXED
Alias: None
Product: Website
Classification: Infrastructure
Component: web-content (show other bugs)
Version: Production
Hardware: x86 Multiple
: Low enhancement
Target Milestone: Q1
Assignee: Michael Halstead
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-12-21 10:17 UTC by Jussi Kukkonen
Modified: 2018-11-09 15:51 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jussi Kukkonen 2016-12-21 10:17:44 UTC
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...
Comment 1 Michael Halstead 2016-12-21 16:39:01 UTC
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?
Comment 2 Michael Halstead 2016-12-21 16:40:26 UTC
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.
Comment 3 Jussi Kukkonen 2016-12-22 09:18:31 UTC
(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.
Comment 4 Joshua Lock 2016-12-22 10:13:09 UTC
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.
Comment 5 Maxin B. John 2016-12-22 11:57:33 UTC
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)
Comment 6 Joshua Lock 2016-12-22 16:03:27 UTC
(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!
Comment 7 Michael Halstead 2018-11-09 15:51:55 UTC
https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ is available now thanks to LetsEncrypt.