Closed
Bug 1503340
Opened 7 years ago
Closed 7 years ago
Expired certificate on srihash.org
Categories
(Infrastructure & Operations :: SSL Certificates, task)
Infrastructure & Operations
SSL Certificates
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: francois, Assigned: ericz)
Details
The certificate for https://www.srihash.org/ has expired and since that site uses HSTS, it's currently impossible to access it.
| Assignee | ||
Updated•7 years ago
|
Assignee: server-ops-webops → eziegenhorn
| Assignee | ||
Comment 1•7 years ago
|
||
This app is hosted on the self-service Heroku platform hence we did not know the cert was expiring for www.srihash.org -- we do not monitor it. I was however able to login to Heroku and switch it to a Let's Encrypt cert which has the benefits of being free and auto-renewing. I do not yet see the cert presented to my browser, looks like the old one is being cached still, but once that clears out it should be good to go. I'll keep watching it to make sure the new cert takes hold.
| Assignee | ||
Comment 2•7 years ago
|
||
And the new cert:auto type created a new endpoint named octagonal-bitterroot-5voyy4z5vfx344u7b2ws622e.herokudns.com is why it wasn't updating. I removed the old one and pointed DNS at the new endpoint and now it works for me. It looks like DNS is still propagating publicly so I'll wait a few and verify that looks good too.
| Reporter | ||
Comment 3•7 years ago
|
||
It's working again for me now. Thanks Eric!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•