-
Notifications
You must be signed in to change notification settings - Fork 38
Update certs #1051
Comments
Looks like our steps are:
From: https://devcenter.heroku.com/articles/automated-certificate-management#migrating-from-ssl-endpoint |
Now that i look at it I think that means we're already on Heroku SSL? If so upgrading should be as simple as
|
Wonder why our common name is gittip.co |
I think that was a mistake and I meant for it to be gratipay.com. |
Alright from what I can see, we're currently on "Heroku SSL" so we're already completely setup for Heroku's "Automated Certificate Management". Their instructions say:
So I think our next step is to hit "I've done this" |
Alright. Research done for gratipay.com, I say we wait till after lunch and then hit the button so we can watch it. Next up: grtp.co |
Added a checklist at the top |
I'm good to go, @clone1018. 👍 |
Actually, we're comparing
|
Mine:
|
Confirmed via |
Spot-checked with |
I'm going to start this now via the Heroku Web UI |
From IRL convo: we can remove |
I'm seeing the new cert live on gratipay.com:
|
Next steps are moving Common Name to gratipay.com and removing gittip.org and www.gittip.org from our Heroku |
www.gittip.org and gittip.org have been removed. We're now: |
Okay grtp.co is potentially solved at gratipay/grtp.co#173 |
Now I'm thinking about MaxCDN. It's a pain in the butt to generate certs locally, reset FTP passwords, upload well-known files and then upload and change certs. I propose we instead switch to their Shared SSL feature.
I'm not seeing us controlling our certificate type. The migration path is to disable SNI and enable Shared SSL |
Sounds good to me, @clone1018. I say go for it. |
It turns out that MaxCDN has a nice hoverstate on the button mentioning that the Shared SSL product cannot work with your own custom domain and you must use their provided domain, eg Gonna start the DNS TXT validation process tomorrow or tonight after the 5K (doubtful) |
DNS for grtp.co happening in gratipay/grtp.co#174 ... |
Done for grtp.co in gratipay/grtp.co#174. Also done for |
Not needed now that Heroku has released automated certificate management. gratipay/inside.gratipay.com#1051
Not needed now that Heroku has released automated certificate management. gratipay/inside.gratipay.com#1051
Deployed, closing! |
90 days is almost up! Time for our first (zero-indexed ;) Let's Encrypt! refresh. This is an urgent priority next week, because I'm gone the week after and our certs expire on the 11th.
The text was updated successfully, but these errors were encountered: