Page MenuHomeMiraheze

AddTrust External Root Certificate Expired
Closed, ResolvedPublic

Description

Per https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA03l00000117LT, our AddTrust External CA root certificate expired.

This has caused a site-wide outage starting 10:51 UTC

Event Timeline

RhinosF1 triaged this task as Unbreak Now! priority.May 30 2020, 11:28

How much time before the error will go away?

We’re working on it now. We can’t give an exact time yet.

2 Hours?

We can’t say. We are testing a solution.

Please do not ask us when it will be fixed. If we have any news, we will let users know.

We are now attempting to deploy a workaround for the issue. We will let you know when this is complete.

Will it fail? I think not.

Hopefully not.

Note to everyone: Please keep general discussion to our discord or IRC. We will update you as we can but constant comments are not helpful.

Here's the reason why "We have identified the cause of the errors, which is the expiration of the "AddTrust External CA Root" certificate."

RhinosF1 renamed this task from Error 503 to AddTrust External Root Certificate Expired.May 30 2020, 12:39
RhinosF1 updated the task description. (Show Details)

I’ve updated the title to reflect the situation. We are working get the issue resolved.

Okay. How can you fix the expired add trust external root?

Okay. How can you fix the expired add trust external root?

We are working on it and will publish an incident report with information later.

If you have discord, go to discord.is/miraheze and I’ll talk to you in real-time. We also have #miraheze on Freenode.

Well done to SRE, the issue has been resolved.

Incident Start: 11:51:04
Incident Over: 14:23:00
Total Time: 2 hours and 31 mins

(in UTC+1)

Responding SRE: @Reception123, @John and @Southparkfan (incident lead)

Dislike token is for the incident occurring to begin with... although I will say "good job"/"like" to those who resolved it.

Dislike token is for the incident occurring to begin with...

All incidents aren’t good but we were not aware of the issue until icinga started alerting so nothing we could have done.

although I will say "good job"/"like" to those who resolved it.

I’m sure everyone will appreciate it.