-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heroku: Need to run the task twice #15
Comments
From reading the code, the challenge won't get stored if there's a |
Actually I just got this in production without the key present. There's really few actionable information in the log. |
Wait. It works only after I run it a second time. Weird. |
I wonder if running |
Hey joallard, I'm getting the same error that you were originally getting (Invalid key authorization: 1 parts). Any advice on how to get it to go away? Already tried running it twice:)
From heroku logs, I can see that I'm getting close, but it looks like it's not rendering the cert.
Error from letsencrypt_plugin: |
Also, I have noticed that the query |
Hi, |
Just tried that. No luck. |
@jack-mcgrath any updates with this? |
Nope, ended up doing the letsencrypt installation process manually. |
Anecdotally: upped to 0.0.8, ran the command to make a new cert, ran fine on first try |
I was working on this tonight and maybe I am not clear on something. When I generate Ok, thought about this for a minute and may go this route. http://www.beardedhacker.com/blog/2014/10/20/load-private-key-to-heroku/ I didn't think I wanted a private key checked into version control, but the instructions were not clear on this for me. |
I've got the following log
The community post, Manual Method: Invalid key authorization: 1 parts suggests a typo, but I doubt this is the case here.
In trying to tackle this, I'm left wondering what went wrong. Maybe a few more log lines showing what challenge we store would be helpful?
The text was updated successfully, but these errors were encountered: