Skip to content

Github Pages isn't hosting my organization's page #22373

Github Pages isn't hosting my organization's page #22373
Dec 10, 2021 · 12 answers

Hello, I have uploaded the build of a Gatsby.js website to Github Pages that you can see in this repo https://github.com/Exsite-Studio/Exsite-Studio

And configured the pages settings in the repo as you can see in the screenshot attached

In the past, the website was working properly. But, right now it’s not even accessible at exsite-studio.github.io

Any help would be appreciated!

Thanks!

Hello @amrsekilly!

Your certificate has not been provisioned yet because your DNS is improperly configured.

You will need to remove the record for 162.255.119.208. This is not a Pages IP.

Once fixed, your TLS certificate should provision just fine.

Replies

12 suggested answers

I can access it, it will just take time when you update it,

0 replies

take note also that at this time, it’s http not https,

0 replies

Thanks, @jdevstatic!

Also, the SSL certificate provisioning is taking too long, it has been in this state for the past week. Any idea how I can fix this issue?

Thanks!

0 replies

is this correct information? namecheap.com also issues the certificate, so I think, they are the one responsible for that.

0 replies

the other factor is where you are hosting your domain, like, is it AWS? or any other hosting platform, because from WHOIS, the domain is already registered

0 replies

I bought the domain from NameCheap and configured the DNS records to point to Github pages, in the past Github Pages were providing the SSL certificate. But right now, it’s showing this pending state for the SSL certificate. @jdevstatic

0 replies

These are my DNS records on NameCheap @jdevstatic

0 replies

take a look at this :

the complete issue is here

  <a href="https://github.com/isaacs/github/issues/1675" target="_blank" rel="noopener nofollow ugc">github.com/isaacs/github</a>

GitHub Pages: Generate SSL certificate for www subdomain when a custom domain is set to an apex (and vice versa)

<div class="github-info">
  <div class="date">
    opened <span class="discourse-local-date" data-format="ll" data-date="2019-10-11" data-time="15:28:00" data-timezone="UTC">03:28PM - 11 Oct 19 UTC</span>
  </div>

    <div class="date">
      closed <span class="discourse-local-date" data-format="ll" data-date="2021-07-20" data-time="22:11:19" data-timezone="UTC">10:11PM - 20 Jul 21 UTC</span>
    </div>

  <div class="user">
    <a href="https://github.com/jakejarvis" target="_blank" rel="noopener nofollow ugc">
      <img alt="jakejarvis" src="https://user-images.githubusercontent.com/47092464/181070621-dfc3f3d8-ac30-4802-9e36-bf3168d44bed.jpeg" class="onebox-avatar-inline" width="20" height="20">
      jakejarvis
    </a>
  </div>
</div>

<div class="labels">
    <span style="display:inline-block;margin-top:2px;background-color: #B8B8B8;padding: 2px;border-radius: 4px;color: #fff;margin-left: 3px;">
      pages
    </span>
</div>

There's a _loooooong_ discussion over at https://github.community/t5/GitHub-Pages/Does-GitHub-Pages-Support-HTTPS-for-www-and-subdomains/td-p/7116 about this — incorrectly marked as "solved," of course.

When setting a custom domain on a GitHub Pages repo to a root domain, like example.com, a Let's Encrypt certificate for it is generated when Enforce HTTPS is enabled (obviously). But there is absolutely no way to have www.example.com redirect to the root/apex domain example.com with a valid SSL certificate as well.

It absolutely sucks having to add yet another service into the mix just to get https://www.example.com to redirect to https://example.com without showing a certificate warning. It seems like a pretty safe assumption that if someone enters an apex domain then they'll want www to mirror it/redirect to it — wanting different content at @ and www is a super rare edge case (and probably accidental if it does occur, to be honest).

Certain domain registrars and/or DNS providers can do this for free (Google Domains, Cloudflare, etc.) but I'd love to keep things consistent re: hosting...and, of course, my personal DNS provider and many others charge extra for this.

Please add www as an alt name on the LE certificate by default if the user inputs an apex domain as the custom domain!

0 replies

and I think, if ever it’s still not working, you can ping him, he is a moderator here in GitHub Community who has the direct access to the backend,

0 replies

Thanks @jdevstatic I already configured the www CNAME, but I’m still waiting for the TLS Certificate provisioning

0 replies

Hello @amrsekilly!

Your certificate has not been provisioned yet because your DNS is improperly configured.

You will need to remove the record for 162.255.119.208. This is not a Pages IP.

Once fixed, your TLS certificate should provision just fine.

0 replies
Answer selected

Thank you so much, @yoannchaude!! That fixed the issue!

0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
General
Labels
None yet
3 participants