GitHub Community
GitHub Pages SSL Certificate Expiration #22398
-
|
Hello, I have a GitHub Page with a custom domain, that stopped working today, with error NET::ERR_CERT_DATE_INVALID. It appears the SSL certificate has expired with this error in the browser. How do I regenerate this SSL cert? I could find nothing in the GitHub docs about this. Subject: www.vrfm.io Issuer: Let’s Encrypt Authority X3 Expires on: Jan 6, 2021 Current date: Jan 6, 2021 PEM encoded chain: The repository itself (vrfm-chevalier/vrfm-chevalier.github.io) still functions as normal. Any suggestions on how to fix this certificate error? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
You might want to reach the support team, since SSL certificates are handled by GitHub itself. GitHub SupportThere’s a section specifically for HTTPS certificates issues. You could also use services like CloudFlare. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I sent a help request already. The Settings section of the repo has been showing this for about 24 hours now. So I assume it’s a server-side error on their part. TLS certificate is being provisioned. This may take up to 15 minutes to complete. 1 of 3 Certificate Request Error: Certificate provisioning will retry automatically in a short period, please be patient. |
Beta Was this translation helpful? Give feedback.
-
|
I got a reply from a very helpful support rep. It turns out ALL CNAME records should point to the repo and you should not chain CNAME calls. e.g. don’t CNAME your www to your apex domain. Instead CNAME to your repo just like your apex entry. The redirects prevent certificate generation. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info. So does that mean my CNAME should only include the repo url? As in ‘‘GitHub - APB-LDN/APB-LDN.github.io: Personal website of Arthur P.B. LAUDRAIN’’? It should not include the custom domain name? |
Beta Was this translation helpful? Give feedback.
I got a reply from a very helpful support rep. It turns out ALL CNAME records should point to the repo and you should not chain CNAME calls. e.g. don’t CNAME your www to your apex domain. Instead CNAME to your repo just like your apex entry. The redirects prevent certificate generation.