acme-companion: TOS hash mismatch, cannot create any new certs
This issue in simp_le seems to cause all new cert generation to fail.
https://github.com/kuba/simp_le/issues/114
When it has been fixed, I suppose a new docker image needs to be built?
2016-08-01 22:23:40,877:INFO:requests.packages.urllib3.connectionpool:756: Starting new HTTPS connection (1): letsencrypt.org
TOS hash mismatch. Found: 6373439b9f29d67a5cd4d18cbc7f264809342dbf21cb2ba2fc7588df987a6221.
Thanks for all the great work!!!
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 10
- Comments: 24 (3 by maintainers)
I can confirm that using the latest version (as of 2 DEC 2017) solves the TOS issue. I stopped/deleted my Letsencrypt container and image. I ran ‘docker-compose up -d’ pulling the latest image and the problem went away.
Hello! Is the problem back again? Will the issue come always after an TOS change?
I get the error:
TOS hash mismatch. Found: 6373439b9f29d67a5cd4d18cbc7f264809342dbf21cb2ba2fc7588df987a6221.This is with a fresh image.Where can we be getting the latest hash? It seems to have changed again …
TOS hash mismatch. Found: cc88d8d9517f490191401e7b54e9ffd12a2b9082ec7a1d4cec6101f9f1647e7b.Same here. @fradeve I got this working by setting an environment variable
ACME_TOS_HASHto valuecc88d8d9517f490191401e7b54e9ffd12a2b9082ec7a1d4cec6101f9f1647e7b. Don’t know if this is a kosher solution.Update done.
Closed by 7b00e3f
Can confirm that pulling the newest version and restarting worked for me.
dokku plugin:update letsencryptis probably the better first thing to try, no? With 0.8.8 I got past that error but hit https://github.com/dokku/dokku-letsencrypt/issues/149.I’m using
image: 'jrcs/letsencrypt-nginx-proxy-companion:latest'and I still get this.