-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The http://react.semantic-ui.com website is down #1429
Comments
Could be related to #1404. There have been isolated issues with the site over the last couple weeks. |
The issues outlined in #1404 seem to be different. The console error I am getting when trying to reach the site is: |
Confirming @brianespinosa 's finding: I get a 105 error (ERR_NAME_NOT_RESOLVED) as well. @ryan4888 , do you not see the same? |
I said it "could" be related. I hadn't investigated much at the time. Looks like I also get |
The |
Not sure what is up with the DNS, I've added a temporary github.io url for now. Images will be borked, but the most of the docs are usable: https://semantic-org.github.io/Semantic-UI-React We'll figure this out as soon as we're able. Thanks everyone! EDIT |
I've also updated the README.me and links on the repo home page with this information. |
For the record, the correct URL for temporary docs is https://semantic-org.github.io/Semantic-UI-React/ |
This is fixed now. It's my fault. I ported DNS over to cloudflare to try to setup SSL/HTTS a couple days ago. Cloudflare "imported" my DNS rules from existing records but somehow this one was lost. The CNAME is now setup again and everything should be working. |
OK, folks, docs are back up! I've removed the temporary docs warning from the README.md. I've also updated all doc site images to use our local images, fixing #1441. I've also updated all HTTP links to semantic-ui.com to use HTTPS so that they work with the new changes. If there are any more issues please let us know. Thanks much @jlukic. |
No description provided.
The text was updated successfully, but these errors were encountered: