dokku-letsencrypt: Bug with latest letsencrypt image

Potentially related: https://github.com/alex/letsencrypt-aws/issues/30

root@dokku:~# dokku letsencrypt visualcosita
=====> Let's Encrypt visualcosita...
-----> Updating letsencrypt docker image...
latest: Pulling from m3adow/letsencrypt-simp_le
420890c9e918: Already exists
acbaf1e6012f: Pull complete
5f71a1a2d3dc: Pull complete
Digest: sha256:be1d7aca214d5277af18d7bf75a2bc78afa5a1eabf98aaa8a606c4ca2a7fdeb5
Status: Downloaded newer image for m3adow/letsencrypt-simp_le:latest
       done
-----> Enabling ACME proxy for visualcosita...
-----> Getting letsencrypt certificate for visualcosita...
        - Domain 'visualcosita.dokku.josediazgonzalez.com'
darkhttpd/1.11, copyright (c) 2003-2015 Emil Mikulic.
listening on: http://0.0.0.0:80/
2016-04-16 20:18:11,149:INFO:__main__:1207: Generating new account key
2016-04-16 20:18:11,830:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-04-16 20:18:11,999:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-04-16 20:18:12,192:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
2016-04-16 20:18:12,498:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): letsencrypt.org
2016-04-16 20:18:13,125:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Traceback (most recent call last):
  File "/simp_le-master/simp_le.py", line 1397, in main
    return main_with_exceptions(cli_args)
  File "/simp_le-master/simp_le.py", line 1382, in main_with_exceptions
    new_data(args, existing_data)
  File "/simp_le-master/simp_le.py", line 1283, in new_data
    for vhost in args.vhosts
  File "/simp_le-master/simp_le.py", line 1283, in <genexpr>
    for vhost in args.vhosts
TypeError: request_domain_challenges() got an unexpected keyword argument 'new_authzr_uri'

Unhandled error has happened, traceback is above

Debugging tips: -v improves output verbosity. Help is available under --help.
-----> Certificate retrieval failed!
-----> Disabling ACME proxy for visualcosita...
       done

Thoughts?

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 17 (10 by maintainers)

Commits related to this issue

Most upvoted comments

same with dokku 0.5.5 and lets encrypt plugin 0.7.1

its a bug in https://github.com/kuba/simp_le - submitted a pull request

https://github.com/kuba/simp_le/pull/100

OK, I’ve now set up the following:

  • There is now the dokkupaas/letsencrypt-simp_le image on Docker Hub set up as an automatic build for the dokku/docker-letsencrypt-simp_le GitHub repository.
  • I’ve set up a Huginn scenario to check kuba/simp_le for new commits every hour and trigger a re-build of dokkupaas/letsencrypt-simp_le if there are new simp_le commits – this should take care of updating dependencies in the future. Not sure how reliable my Huginn setup is since I’ve just started experimenting with it so bug me if this should ever fail.
  • dokku-letsencrypt now uses dokkupaas/letsencrypt-simple (d5c35d7)

I’ll keep sseemayer/letsencrypt-simp_le around both on Docker Hub and GitHub in order to not break things for people that don’t want to update yet and will remove this in a few weeks from now.

Done!

If you update dokku-letsencrypt you will now use my “fork” of letsencrypt-simp_le that has a rebuilt docker image with working dependencies.

@sseemayer may be worth us just maintaining the downstream dependencies if we don’t get this resolved in the next week.