GH Pages endless "DNS Check in Progress" #37200
Replies: 7 comments 1 reply
-
I think this is just another post-Microsoft rough edge in a sea of rough edges that will likely never get fixed. I have several sites with valid HTTPS in Custom Domains that are stuck on |
Beta Was this translation helpful? Give feedback.
-
Response #2 |
Beta Was this translation helpful? Give feedback.
-
Does your server has a valid ssl certificate ? |
Beta Was this translation helpful? Give feedback.
-
My page also has the "DNS Check in Progress" marker, however I can access it with https, what is using a valid, signed certificate. |
Beta Was this translation helpful? Give feedback.
-
i'm also experiencing this issue, with a domain purchased through google workstation and hosted by enom.com .. |
Beta Was this translation helpful? Give feedback.
-
Same issue. Endless checking. It's been working fine for the past few years, but in the last few weeks it's been acting up. |
Beta Was this translation helpful? Give feedback.
-
maybe Copilot suggestions can help It's hard to say for sure without more information, but here are a few things you can check:
If you've checked all of these things and are still having issues, it might be worth reaching out to GitHub Support for assistance. They can check the status of your Pages site from their end and may be able to provide more insight into what's going wrong. |
Beta Was this translation helpful? Give feedback.
-
I had a custom domain that worked over http:, even though it kept giving the DNS check messages on the repo's Pages page. I tried turning on enforce https:, but that never really worked since the Pages still had the message, and it broke the site.
I turned off Pages for over a week, and just turned it back on, after triple checking my DNS records. Same error.
Is this repo just borked on the GitHub internals side somehow? Or did I indeed mess up my DNS records? I'm hoping to not have to fork into a new repo name to get Pages working. I'm suspicious, because this happened once with another throwaway site: one repo got stuck on the DNS check, and would never correct itself. dig shows the domain has the correct A records.
ShaneCurcuru/slides@d34041a
Beta Was this translation helpful? Give feedback.
All reactions