mirror of
https://github.com/conventional-commits/conventionalcommits.org.git
synced 2026-05-24 16:40:58 -05:00
Bad certificate on www.conventionalcommits.org #204
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/conventionalcommits.org#204
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tirithen on GitHub (Apr 17, 2024).
The website www.conventionalcommits.org has a bad certificate (Swedish in screenshot, but error should be obvious)
@amarjandu commented on GitHub (Apr 17, 2024):
plz fix this i cant remember any of the commit conventions by heart because my little brain is full of memes.
@gmli-eu commented on GitHub (Apr 18, 2024):
The website is down
@rjaegers commented on GitHub (Apr 18, 2024):
For projects that do link-validation as part of their ci-system this can actually break builds. We point to the conventional commits website in our contributing guideline and our linter fails with a broken link.
Would be really great if someone could take a look what's going on with the certificate.
@dudil commented on GitHub (Apr 18, 2024):
@tirithen / @rjaegers / @mowies - if this is critical to your CI/CD tools you can access the website using the Netlify provided URL:
https://tender-babbage-1fbb34.netlify.app.
I'm not part of the team here, but happen to see the same and by looking into the DNS records found this is the provided URL by Netlify which is always secured
@mowies commented on GitHub (Apr 18, 2024):
Thanks for the hint! :)
I think we'll wait and stay on the original URL though
@aaraney commented on GitHub (Apr 18, 2024):
@amarjandu and really anyone else who can't access the site, it looks like it is generated from static markdown files that are in this repo. For example, here is the
v1.0.0page.@bcoe commented on GitHub (Apr 19, 2024):
I just clicked renew on the certificate, I'm not sure what's happening here.
@aaraney commented on GitHub (Apr 19, 2024):
@bcoe, the server's cert is a wildcard netlify cert
Common Name: *.netlify.appand the alt names arenetlify.appand*.netlify.app. I hope that is helpful.@bcoe commented on GitHub (Apr 19, 2024):
Netlify had timed out renewing the letsencrypt certificate and I had to manually click a button.
@amarjandu commented on GitHub (Apr 19, 2024):
@bcoe thanks for your support! Appreciate you!