Provider
MetabaseIncident detail
Issue with SSL certificates
Timeline window
to
Get alerted the next time Metabase breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We're investigating an issue in our cloud with certificate management that's causing browsers to receive incorrect certificates
Resolved
Ingress controller certificates are now back to normal. You should be able to get the correct certificate in the browser now. We're very sorry for the inconvenience, we'll publish a retrospective about the issue in the next few days.
Resolved
Summary
On Thursday Nov 9th the default certificate for the external Nginx ingress was replaced with a dummy certificate. Users attempting to reach their hosted instances would get an invalid certificate error. This was due to a misconfiguration in the new CI for releasing our helm charts that used the internal Nginx ingress values files for the external Nginx ingress.
Impact
All hosted customers not using custom domains were affected.
How was the root cause diagnosed?
We identified that the values were properly set in the values files. We Investigated the CI steps to determine why the correct values were not set. It was determined that the wrong values files were being used for external Nginx ingress.
How we’ll make this not happen again?
- Update staging and production value files to match.
- Add alert to pagerduty for non-custom domains (catch alerts faster)
Keep exploring
More from Metabase
Neighboring incidents on Metabase's timeline and the rest of their record on OutageDeck.