part of the "ourincrediblejourney" meme(?) is that they actually need to shut down the product. that could still happen but until then it's not really a "fuck you" to its customers if the app still works.
Shutting down the product is one way a company can qualify for ourincrediblejourney. I would argue that another way is the "we're being acquired by $RANDOM, so thanks for all your personal data!" track.
That's step 2; usually happens months after step 1 (and the bingo marks are all there: "we are joining X, do not fear, what a journey"), proferred here.
Have you used this recently? I just tried it 3 times, and every step succeeds until after I've successfully completed step 4, then step 5 displays a failure message that tells me to go back to Step 1 again.
I didn't realize you were the author! I figured out that I made a mistake by using the same key pair for Steps 1 and 2. The LetsEncrypt API returned an error that told me to use a different key for the CSR, and once I did that it worked.
Reading back through your instructions, I don't know how you could be more clear that ACCOUNT.KEY and DOMAIN.KEY should be different. It's just my fault for not reading slowly enough. :)
Thanks a bunch for making this tool, it made everything simple.
I don't get it. What is the domain key here?
I tried to read the instructions but all of it said that the signing should be done with account private key.
Ok I got confused because tried to simultaneously read how to make the certificate using Amazon AWS documentation, and seems I skipped one crucial part.
Did you figure it out? You need two different keys: the account.key and the domain.key. For most of the steps you will use the account.key to sign, but the Certificate Signing Request will use the domain.key to sign.
