Cert revoked on chocolatey.org

[saminaltamimi]

Checklist

• I confirm there are no unresolved issues reported on the Chocolatey Status page.
• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

What is Expected?

I expect to be sent to the chocolatey home page.

How Did You Get This To Happen?

1. go to chocolatey.org

System Details

• Operating System:
• Windows PowerShell version:
• Chocolatey CLI Version:
• Chocolatey Licensed Extension version:
• Chocolatey License type:
• Terminal/Emulator:

Installed Packages

n/a

Output Log

n/a

Additional Context

No response

Tasks

Beta Give feedback

No tasks being tracked yet.

[saminaltamimi]

Same thing with community.chocolatey.org

[JPRuskin]

Thank you for letting us know. We're investigating and trying to fix this immediately.

[pauby]

Thanks for raising the issue.

There is a bit of a back-story to this, which I won't bore you with. To give a little context, we were made aware that GoDaddy had made a mistake on our certificate late on Friday, and the revocation was to take place after 72 hours (tomorrow). By that time, we would have a new certificate and this issue would never have appeared. It seems like the revocation was performed early.

As a TL;DR, we are aware of this, we're as unhappy as you are, and we are working on this right now.

[pauby]

This has now been resolved with multiple people confirming it is now working for them as normal. Thank you for your patience in this. We apologise for any inconvenience.

[saminaltamimi]

Thanks for raising the issue.

There is a bit of a back-story to this, which I won't bore you with. To give a little context, we were made aware that GoDaddy had made a mistake on our certificate late on Friday, and the revocation was to take place after 72 hours (tomorrow). By that time, we would have a new certificate and this issue would never have appeared. It seems like the revocation was performed early.

As a TL;DR, we are aware of this, we're as unhappy as you are, and we are working on this right now.

Personally, I'm not a big fan of GoDaddy and choose to use certbot and Let's Encrypt. But personal politics aside, thanks for the information and speedy resolution.