-
Select Topic AreaBug BodySo I recently got a new domain and I went to verify it but I kept running into this screen with a unicorn. I was sure I set all of the A/TXT records correctly so I waited, and then today I checked these discussions and saw one about the incident with GitHub Pages. It was marked as resolved so I am making a new discussion for this. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Hey @Gemdation! Thanks for reaching out 👋 If you're having trouble verifying your custom domain, the following documentation might help you identify and fix potential configuration issues: Troubleshooting custom domains and GitHub Pages. It provides detailed guidance for cases like this, including DNS verification and domain conflicts with other repositories. Hope this helps! 😊 |
Beta Was this translation helpful? Give feedback.
No, this was not about troubleshooting. It was rather about the server error (503?) that happened earlier.