SHA256 hash of the TOS has changed

[thomastweets]

With the update to the Let’s Encrypt Subscriber Agreement today (v.1.1.1) the SHA256 hash has changed to 6373439b9f29d67a5cd4d18cbc7f264809342dbf21cb2ba2fc7588df987a6221
I can create a pull request to change line 894/895 of simp_le.py, however, I am not sure whether this covers all of it (and I am not deep into the topic).

[LeoFidjeland]

Having this issue as well, cannot create any new certs at all.

Please approve the PR asap.

And thanks for all the great work :)

[andresmrm]

Also got same error here.

@LeoFidjeland : As an workaround you can pass parameter:
--tos_sha256 6373439b9f29d67a5cd4d18cbc7f264809342dbf21cb2ba2fc7588df987a6221.
At least here it worked.

[madshargreave]

+1, my app is down because I cannot renew my certificate. Any help is greatly appreciated

[amiryal]

To the best of my understanding, this issue only affects new registrations, and it can be worked around by using --tos_sha256 6373439..., as suggested by @andresmrm above. If using an existing (already registered) account key, then no changes are necessary. Correct?

[thomastweets]

@amiryal True! However, some other software that makes use of simp_le does not allow to specify this parameter. (e.g. https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion or https://github.com/dokku/dokku-letsencrypt). I am working on a forked docker image of https://github.com/JrCs/docker-letsencrypt-nginx-proxy-companion to have a work-around for now as I indeed need to do new registrations with simp_le.

[thomastweets]

Here we go: https://hub.docker.com/r/thomastweets/docker-letsencrypt-nginx-proxy-companion/

[LeoFidjeland]

Awesome, thanks so much @thomastweets! Works perfectly!

You saved the day!!

[vrozkovec]

Is this project still maintained?

[chicks-net]

@vrozkovec -- the author has been inactive on github since June. Maybe google has been keeping him busy.

[Thor77]

Does anyone have contact to the maintainer?
If not, does anyone plan to create a organization for this project and start maintaining it again?

[chicks-net]

I gave up and I've migrated to acme.sh.

[wiz78]

If you want to workaround the problem, you can comment a couple of lines in simp_le/venv/lib/python/site-packages/acme/messages.py:

        #if not set(canon_jobj).issubset(self._REGISTERED_TYPES): # <-- this line (should be 140)
            # TODO: acme-spec is not clear about this: 'It is a JSON
            # dictionary, whose keys are the "resource" values listed
            # in {{https-requests}}'z
         #   raise ValueError('Wrong directory fields') # <-- and this one

[amiryal]

@wiz78 the right way to do it is to upgrade the acme library to a later version, as implemented by this fork of simp_le. If you would like, you may suggest your change to ACME upstream.

[wiz78]

@amiryal you're right. Mine was meant to be a dirty hack, since I was under the impression that the whole project had been abandoned.

[amiryal]

Glad to help inform people about the more maintained fork. :)