dokku-letsencrypt: adding certificate to second application failing at verification

  • dokku 0.5.4 with dokku-letsencrypt 53385105bc6ed1fb4049b7b4f5b1a7184dd53cb1
  • Ubuntu 14.04.4 LTS

letsencrypt app1 worked great for the first app, but on the second app, letsencrypt app2 fails at the verification stage:

2016-04-15 04:13:20,170:ERROR:acme.challenges:267: Unable to reach http://app2.apps.example.com/.well-known/acme-challenge/FdhXO8u3IWsE7VNqZZXphq-JeHWcFycEMy-uu4uveh4: hostname 'app2.apps.example.com' doesn't match 'app1.apps.example.com'
2016-04-15 04:13:20,170:WARNING:__main__:1292: app2.apps.example.com was not successfully self-verified. CA is likely to fail as well!

Any ideas? Is this related to dokku 0.5 compat?

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 28 (13 by maintainers)

Most upvoted comments

For future reference, I ran into this issue because I was using https://github.com/heroku/heroku-buildpack-static with the https_only option set to true, meaning that when the ACME server hit the challenge URL with HTTP it was being redirected to the HTTPS version.

All seems to be working now. Thanks! Almost gave up until I realized I missed the line about the leftover DOKKU_DOCKERFILE_PORTS entry.