Allow HTTPS to access the hackergarten website

[McPringle]

No description provided.

[madmas]

You just need to accept that certificate ;-)

No, seriously, I did a little google on this:

• https://konklone.com/post/github-pages-now-sorta-supports-https-so-use-it
• https://sheharyar.me/blog/free-ssl-for-github-pages-with-custom-domains/
• Add HTTPS support to Github Pages including custom domains isaacs/github#156

Unfortunately, what I understood, SSL is not fully supported for custom domains.
Also, as we do not have any login, SSL would be nice, but does not look crucial to me ;-)

[madmas]

This might bring some movement to this issue: https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

[McPringle]

That could be a topic for the May Hackergarten in Basel…

[madmas]

According to

• https://help.github.com/articles/securing-your-github-pages-site-with-https/
• https://help.github.com/articles/troubleshooting-custom-domains/#https-errors

we need to add an CAA DNS record entry: https://letsencrypt.org/docs/caa/

I'll see that I talk to the right people about that.

[sclassen]

+1

[McPringle]

Who has access to the DNS record of hackergarten.net? We should work on this soon, some actual browsers warn the user that hackergarten.net is not safe to visit…

[madmas]

Working on it, reached out to the Hackergarten initiator @HamletDRC :)

[HamletDRC]

I can edit the DNS entry. Which of these do I need to modify?

        <option value="">-- Select below --</option>
        <option value="NSV">Private Nameserver</option>
        <option value="NSA">NS Record</option>
        <option value="MX">MX Record</option>
        <option value="CNAME">CNAME Alias</option>
        <option value="A">A Record</option>
        <option value="TXT">TXT/SPF Record</option>
        <option value="DKIM">DKIM Record</option>
        <option value="DMARC">DMARC Record</option>

[HamletDRC]

There is also an option to enable "Let's Encrypt Free SSL".

[HamletDRC]

(this is hosted at Dotster)

[HamletDRC]

OK, I changed the nameservers to point at the Dotster name servers and then enabled the Free SSL.
The nameservers had been dns1.canoo.ch and dns2.canoo.ch

I suspect that the website might be broken once the DNS records update 👍

[madmas]

@HamletDRC thanks a lot for looking into this :)

I think according to https://help.github.com/articles/setting-up-an-apex-domain/ you need to setup a "A Record" to those IP adresses:

    185.199.108.153
    185.199.109.153
    185.199.110.153
    185.199.111.153

HTTPS via the hoster will not work, but it can be provided from github, then: https://help.github.com/articles/securing-your-github-pages-site-with-https/

[HamletDRC]

I changed the nameservers to point back to Canoo to bring the website back. Please note that because of the way name servers work, it may take up to 24 hours for your changes to take effect.
After the http domain is back then I'll update these A records.

[madmas]

@HamletDRC using you providers DNS is the way to go, as the A record would be created and served from there. Migrating away from Canoo's DNS is what we should do (see my email ;-) ).

[madmas]

At Hackergarten Basel July 2019 we actually had the chance to sit together and work on this. Should be solved as soon as DNS updates are through :)

[McPringle]

Works like a charm! Cool stuff!

[madmas]

Finally solved, yay :D 💃