Closed Bug 1362568 Opened 9 years ago Closed 9 years ago

WARNING - treeherder.mozilla.org SSL Cert Expires 6-1-17

Categories

(Infrastructure & Operations :: SSL Certificates, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joeyk, Assigned: emorley)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4781])

No description provided.
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4781]
Assignee: server-ops-webops → jkrejci
CC Ed; this is hosted in Heroku.
I'm inclined to try out Heroku's automatic let's encrypt based service, ACM: https://devcenter.heroku.com/articles/automated-certificate-management#migrating-from-heroku-ssl-with-your-own-certificate I'll try with stage first, soon.
Assignee: jkrejci → emorley
Please let us know how it goes; there shouldn't be any obstacles.
Depends on: 1363814
I've filed a treeherder component bug (bug 1363814) for converting Treeherder stage and prod to Heroku ACM. Stage is now switched (pretty slick process - am impressed), will wait a bit before doing prod to stagger the expiry date in case of issues when the auto-renewal comes up in 90 days.
Group: mozilla-employee-confidential
Prod now switched over to the new cert in bug 1363814. $ heroku certs:auto --app treeherder-prod === Automatic Certificate Management is enabled on treeherder-prod Certificate details: Common Name(s): treeherder.mozilla.org Expires At: 2017-08-09 20:25 UTC Issuer: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Starts At: 2017-05-11 20:25 UTC Subject: /CN=treeherder.mozilla.org SSL certificate is verified by a root authority. Domain Status ────────────────────── ────── treeherder.mozilla.org OK
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.