[GH-ISSUE #581] Bad certificate on www.conventionalcommits.org #4924

Closed
opened 2026-05-02 23:33:54 -05:00 by GiteaMirror · 10 comments
Owner

Originally created by @tirithen on GitHub (Apr 17, 2024).
Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/581

The website www.conventionalcommits.org has a bad certificate (Swedish in screenshot, but error should be obvious)

Skärmbild från 2024-04-17 14-17-12

Originally created by @tirithen on GitHub (Apr 17, 2024). Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/581 The website www.conventionalcommits.org has a bad certificate (Swedish in screenshot, but error should be obvious) ![Skärmbild från 2024-04-17 14-17-12](https://github.com/conventional-commits/conventionalcommits.org/assets/245811/a34f2105-a059-4e74-9578-5587fd478862)
Author
Owner

@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.

<!-- gh-comment-id:2061737955 --> @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.
Author
Owner

@gmli-eu commented on GitHub (Apr 18, 2024):

The website is down
image

<!-- gh-comment-id:2063377817 --> @gmli-eu commented on GitHub (Apr 18, 2024): The website is down ![image](https://github.com/conventional-commits/conventionalcommits.org/assets/3688770/3e635b6b-bb5a-4329-8d23-082f144dcf87)
Author
Owner

@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.

<!-- gh-comment-id:2063602684 --> @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.
Author
Owner

@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

<!-- gh-comment-id:2063870952 --> @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](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**
Author
Owner

@mowies commented on GitHub (Apr 18, 2024):

Thanks for the hint! :)
I think we'll wait and stay on the original URL though

<!-- gh-comment-id:2063877486 --> @mowies commented on GitHub (Apr 18, 2024): Thanks for the hint! :) I think we'll wait and stay on the original URL though
Author
Owner

@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.0 page.

<!-- gh-comment-id:2064186499 --> @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](https://github.com/conventional-commits/conventionalcommits.org/blob/master/content/v1.0.0/index.md) is the `v1.0.0` page.
Author
Owner

@bcoe commented on GitHub (Apr 19, 2024):

I just clicked renew on the certificate, I'm not sure what's happening here.

<!-- gh-comment-id:2067096400 --> @bcoe commented on GitHub (Apr 19, 2024): I just clicked renew on the certificate, I'm not sure what's happening here.
Author
Owner

@aaraney commented on GitHub (Apr 19, 2024):

@bcoe, the server's cert is a wildcard netlify cert Common Name: *.netlify.app and the alt names are netlify.app and *.netlify.app. I hope that is helpful.

<!-- gh-comment-id:2067117930 --> @aaraney commented on GitHub (Apr 19, 2024): @bcoe, the server's cert is a wildcard netlify cert `Common Name: *.netlify.app` and the alt names are `netlify.app` and `*.netlify.app`. I hope that is helpful.
Author
Owner

@bcoe commented on GitHub (Apr 19, 2024):

Netlify had timed out renewing the letsencrypt certificate and I had to manually click a button.

<!-- gh-comment-id:2067148099 --> @bcoe commented on GitHub (Apr 19, 2024): Netlify had timed out renewing the letsencrypt certificate and I had to manually click a button.
Author
Owner

@amarjandu commented on GitHub (Apr 19, 2024):

@bcoe thanks for your support! Appreciate you!

<!-- gh-comment-id:2067173704 --> @amarjandu commented on GitHub (Apr 19, 2024): @bcoe thanks for your support! Appreciate you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#4924