dokku-letsencrypt: Let's Encrypt fails with `You must set at least one -d/--vhost`

Any ideas here? Of course the cert expires today. Not even revoke works - I’d appreciate any tips on getting nginx to disable the cert in the meantime. Just updated to the latest plugin version too.

# dokku letsencrypt:auto-renew aqueousband.com
=====> Auto-renew aqueousband.com...
=====> Let's Encrypt aqueousband.com...
-----> Updating letsencrypt docker image...
latest: Pulling from m3adow/letsencrypt-simp_le
Digest: sha256:be1d7aca214d5277af18d7bf75a2bc78afa5a1eabf98aaa8a606c4ca2a7fdeb5
Status: Image is up to date for m3adow/letsencrypt-simp_le:latest
       done
-----> Enabling ACME proxy for aqueousband.com...
-----> Getting letsencrypt certificate for aqueousband.com...
darkhttpd/1.11, copyright (c) 2003-2015 Emil Mikulic.
listening on: http://0.0.0.0:80/
You must set at least one -d/--vhost

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

Cert info:

# dokku certs:info aqueousband.com
-----> Fetching SSL Endpoint info for aqueousband.com...
-----> Certificate details:
=====> Common Name(s): 
=====>    aqueousband.com
=====>    aqueousband.com
=====> Expires At: Apr  5 04:28:00 2016 GMT
=====> Issuer: C=US, O=Lets Encrypt, CN=Lets Encrypt Authority X1
=====> Starts At: Jan  6 04:28:00 2016 GMT
=====> Subject: CN=aqueousband.com
=====> SSL certificate is self signed.

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 1
Comments: 30 (9 by maintainers)

Commits related to this issue

Use official dokku API for getting app domains Ref. #43, #44 With the changes in dokku 0.5, domain arguments for letstencrypt-simp_le were not constrtucted correctly anymore. This patch uses the off... — committed to dokku/dokku-letsencrypt by sseemayer 8 years ago

Most upvoted comments

I hit this issue recently. In this case, the fix was dokku plugin:update letsencrypt.

+10

ssssam on Oct 14, 2020

Same issue occurred for me recently. Fixed by dokku plugin:update letsencrypt followed by dokku letsencrypt:auto-renew

paulh-adion on Oct 19, 2020

@justspamjustin worked, thanks.

To be clear:

First run dokku domains:set APP_NAME APP_DOMAIN.COM

And then dokku letsencrypt APP_NAME.

Freika on Oct 16, 2017

I recently got this error. I initially set up my dokku to not use vhost subdomains. After running dokku domains:set <appname> <yourdomain>, I was able to run dokku letsencrypt <appname> successfully.

justspamjustin on Oct 16, 2017

@sseemayer Confirmed working dokku version 0.4.5

tudborg on Apr 6, 2016