[DOCS-13724] Expired SSL root cert on docs.mongodb.com Created: 22/Jun/20 Updated: 06/Jan/23 Resolved: 06/Jan/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Jeroen Ooms | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 33 weeks, 2 days ago |
| Description |
DescriptionA few weeks ago, one of the major SSL root certificates expired. Serving an expired root certificate raises an SSL error in some HTTP clients (but not in most browsers). For example in the latest MacOS Catalina: curl https://docs.mongodb.com/ Note that it is not the docs.mongodb.com cert that has expired, but one of the intermediate certificates that your server is sending in the SSL chain. The solution is simple: edit your webserver conf to remove the expired CA cert from the bundle. You don't need to replace it with anything, because all clients trust this vendor by default in their own CA bundle. For more info see here: https://support.sectigo.com/articles/Knowledge/Sectigo-AddTrust-External-CA-Root-Expiring-May-30-2020
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |