https://vespa.ai has a self signed or invalid cert about vespa HOT 4 CLOSED

Thank you for your input @harryjackson.

We are currently serving vespa.ai out of GitHub Pages and they, unfortunately, do not (properly) support HTTPS for custom domains as we cannot add our own certificate.

We may look at a different serving option in the future or can hope GitHub will add support for this. For now, I am afraid we will have to do with plain, insecure HTTP.

Best regards,
Frode Lundgren
Director of Engineering, Vespa Services

from vespa.

Since closing this issue, GitHub has started issuing Let's Encrypt certificates for all GitHub Pages custom domains. https://docs.vespa.ai now has a valid certificate, but https://vespa.ai still use the generic GitHub certificate. Will continue to keep an eye on this.

from vespa.

Just found that the reason we don't have valid certificate for apex domain (vespa.ai) is that GitHub have changed what A records to use to get Let's Encrypt certificate.

From https://help.github.com/articles/troubleshooting-custom-domains/#custom-domains-configured-with-a-records:

If you configured your custom domain using an A record, your A record must point to one of the following IP addresses for HTTPS to work:

• 185.199.108.153
• 185.199.109.153
• 185.199.110.153
• 185.199.111.153

I have updated the A records for vespa.ai:

$ dig +noall +answer vespa.ai
vespa.ai.		583	IN	A	185.199.111.153
vespa.ai.		583	IN	A	185.199.108.153
vespa.ai.		583	IN	A	185.199.109.153
vespa.ai.		583	IN	A	185.199.110.153

I have removed and re-added custom domain (vespa.ai) to GitHub pages hoping this would trigger certificate generation.

from vespa.

Confirmed that SSL certificate for https://vespa.ai is now valid:
https://www.digicert.com/help/?host=vespa.ai

from vespa.