TOS hash mismatch, cannot create any new certs

[LeoFidjeland]

This issue in simp_le seems to cause all new cert generation to fail.

kuba/simp_le#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!!!

[thomastweets]

As a workaround: https://hub.docker.com/r/thomastweets/docker-letsencrypt-nginx-proxy-companion/ (see also kuba/simp_le#114)

[LeoFidjeland]

@thomastweets works perfectly thanks a million!!

[JrCs]

Update done.

Closed by 7b00e3f

[kachkaev]

Thanks a lot for reacting to this so quickly @JrCs!

Here's the ToS diff (if anyone is interested in what they sign):
https://letsencrypt.org/documents/LE-SA-v1.0.1-v1.1.1-diff.docx

More links to letsencrypt documents:
https://letsencrypt.org/repository/

[dotellie]

Am I the only one who's still getting this?

[faultylee]

I was seeing the same message yesterday when I was adding a new host, though the cert generated properly. I guess it's non fatal since it's "INFO".

[JrCs]

It must work now with the new version

[dotellie]

After countless of seemingly hopeless attempts to get this working, it somehow fixed itself after a (second) reboot of the host and all the containers.

[peXed]

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.

[paolomainardi]

Same problem here.

[1beb]

Can confirm that pulling the newest version and restarting worked for me.

docker pull jrcs/docker-letsencrypt-nginx-proxy-companion 

[fradeve]

I'm using image: 'jrcs/letsencrypt-nginx-proxy-companion:latest' and I still get this.

[mlaitinen]

Same here. @fradeve I got this working by setting an environment variable ACME_TOS_HASH to value cc88d8d9517f490191401e7b54e9ffd12a2b9082ec7a1d4cec6101f9f1647e7b. Don't know if this is a kosher solution.

[fradeve]

That fixed it! Amazing, thanks :)

[rgruesbeck]

Same here.

[bfayers]

@mlaitinen Where am i supposed to set this envvar?

[buchdag]

@bfayers on the letsencrypt-nginx-proxy-companion container

https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion#optional-container-environment-variables

[bfayers]

I got it :)

[krystalcode]

Where can we be getting the latest hash? It seems to have changed again ...

TOS hash mismatch. Found: cc88d8d9517f490191401e7b54e9ffd12a2b9082ec7a1d4cec6101f9f1647e7b.

[buchdag]

@krystalcode #277 #282

[xandermar]

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.

[herejia]

As of e47e065463db I just ran docker rm my-container-name and docker pull jrcs/letsencrypt-nginx-proxy-companion and everything went fine

[pattonwebz]

I am unsure how long this has been a problem in my setup but I ran into it today adding a new container.

Getting latest image as of today fixes it for me.

docker pull jrcs/letsencrypt-nginx-proxy-companion then restart the service.

[dblock]

dokku plugin:update letsencrypt is probably the better first thing to try, no? With 0.8.8 I got past that error but hit dokku/dokku-letsencrypt#149.