search

substrakt / letsencrypt-heroku

Make any Heroku application secure in just a couple of minutes.
https://substrakt.com/heroku-ssl-me-weve-come-a-long-way/
MIT License
524 stars 19 forks source link

Stuck on Heroku certificate deployment #16

Closed backspace closed 7 years ago

backspace commented 8 years ago

Hey, thanks for your work on this. I’m happy that the moment of free and easy SSL is approaching.

It seems like my installation isn’t working properly, as it never progresses beyond the Deploying certificate to Heroku stage. I’ve looked at the data in Redis but don’t see anything helpful there. I can see that CloudFlare has some ACME-related TXT records, which seems like a good sign.

When I run heroku _certs:info it says there are no certificates, which I think wouldn’t be the case if the process succeeded?

Let me know if I can provide any debugging information.

Also, I have a side question about something in the documentation:

It doesn't currently add the CNAME records to CloudFlare once the SSL certificate has been generated.

Would the CNAME just be an alias for applicationname.herokuapp.com?

maxehmookau commented 8 years ago

Ok, so your second query first (it's easier), that's correct. Although it won't be in that form as the SNI plugin on Heroku overrides the DNS entries. Just keep an eye on it.

As for that first issue, that's puzzling. Chances are it's failing somewhere in the process and then not attaching the cert. By the looks of it, it's added the TXT record so the verification has worked as the cert has been generated. Are you 100% sure your Heroku API key is correct? That seems like the most likely cause of failure currently.

backspace commented 8 years ago

hmm, well just in case, I revoked the token and created a new one. On my first attempt, I got this error:

Error creating new cert :: Authorizations for these names not found or expired: chromatin.ca

I tried again, and the same thing happened where it never progressed beyond in_progress an “Deploying certificate to Heroku”

reverofevil commented 7 years ago

Same issue. Just hangs on "Deploying certificate to Heroku". TXT is already there. There were at least two Heroku tokens in the process and no "Heroku API keys". @maxehmookau, what do you mean?

samknight commented 7 years ago

I'm having the same issue here and currently looking for the cause.

samknight commented 7 years ago

Try creating a new oauth user to the account and adding the token to the ENV config. This worked for me but may not have been the same issue.