-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
"TOS hash mismatch" when using acme / simp_le / letsencrypt #17455
Comments
@fpletz @abbradar @bobvanderlinden Hi guys; if any of you know what's going on here, it'd be greatly appreciated. From what I can tell, the Terms of Service are out of date for nixpkgs's version of letsencrypt - and this makes the service pretty much unusable. If you have any ideas about how we can fix this, I'll be happy to investigate further and make a fix. |
Luckily only happens when creating a new account, so renews are not affected. Thanks for reporting. Fixed. 🍻 |
@fpletz Awesome; thanks for the very fast fix! I'm wondering if there's a more permanent way to solve this - being unable to deploy new servers whenever letsencrypt releases a new TOS seems a bit fragile. Maybe we could add a configuration option to set the TOS hash on the command line when invoking simp_le? |
That's a good idea. Also as we're right before releasing 16.09 we should add that option before the release so NixOS users can easily update the hash themselves if needed. |
Hi! Even if the new configuration option to set the TOSH hash would only appear in |
@dsferruzza Thanks for the reminder. I'll look at it. The only potential problem is that |
@fpletz any news? If someone need a fix, just add the following snippet to your configuration to override the
Then you can use the But I hope the patch will soon be available in |
@dsferruzza Ah, thanks for testing that! In that case I'll simply backport that patch. |
Fixes #17455. Also see kuba/simp_le#114. (cherry picked from commit e55aa50)
Ok, backported. Will be in the 16.03 channel soon. I'll keep this issue open because I want an to add an option for 16.09 to specify the TOS hash in the |
Confirmed to work on |
@fpletz are you still planning on doing this in time for 16.09? |
@fpletz what are actionables here for 16.09? |
Fixes NixOS#17455. Also see kuba/simp_le#114. (cherry picked from commit e55aa50)
We won't implement this for now because we need to replace simp_le anyway. |
This is happening again? |
That fix worked for me. I've no idea if it breaks anything else for others. |
Fixes NixOS#17455. Also see kuba/simp_le#114. (cherry picked from commit e55aa50)
Issue description
ACME certificates cannot be provisioned automatically, even though
letsencrypt
run in manual mode succeeds.Steps to reproduce
This seems to occur whenever allocating a new certificate, and possibly when renewing one.
Technical details
The text was updated successfully, but these errors were encountered: