3 ms·
If your site is configured with A records, you’ll need to change the IPs it’s pointing to before you’ll be able to get a cert: 185.199.108.153 185.199.109.153
by Spazer 8y ago
If your site is configured with A records, you’ll need to change the IPs it’s pointing to before you’ll be able to get a cert:
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
From: https://help.github.com/articles/setting-up-an-apex-domain/ https://help.github.com/articles/setting-up-an-apex-domain/
EDIT: You’ll also need to remove and re-add the domain in the repository settings after doing that too to trigger it to request a cert.
- myroon5 8y agoCan you expand on how to perform the steps added in your edit? Thanks!
- Spazer 8y agoGo to the GitHub pages section of the repo settings, delete your domain name from the custom domain input, hit save, then add it back and save again. If it’s still not working after that the you can contact support and they can press a button on the back end to trigger a cert request.
- toshimaru 8y agoThis worked for me! thanks!
- myroon5 8y agoDidn't work for me. Might have something to do with the fact that I also have a CNAME file in my repo. I'll reach out to support
- skluck 8y agoHow long have you waited? For a while (After updating to their new IPs and enabling/disabling custom domain) it said it was unavailable, but then after 60-90 minutes both of my repos are now in "Not yet available for your site because the certificate has not finished being issued" state. I guess I'll have a better idea tomorrow if it worked or not but for now I'm hoping this is just my repos working their way through github's cert queue. * I also have CNAME files in my projects.
- mitsudomoe8 8y agoCould you please update us once it's done? I have got exactly the same issue.