-
-
Save johnfraney/62b1dc5ccddd2c8a7358 to your computer and use it in GitHub Desktop.
Dokku LetsEncrypt output when app has dokku-http-auth enabled also
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2016-02-24 17:41:05,311:INFO:__main__:1202: Generating new account key | |
2016-02-24 17:41:07,094:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:07,348:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:07,471:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:07,668:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): letsencrypt.org | |
2016-02-24 17:41:08,404:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:08,542:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:08,707:INFO:requests.packages.urllib3.connectionpool:207: Starting new HTTP connection (1): mydomain.com | |
2016-02-24 17:41:08,778:WARNING:__main__:1292: mydomain.com was not successfully self-verified. CA is likely to fail as well! | |
2016-02-24 17:41:08,802:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:08,929:INFO:__main__:1302: Generating new certificate private key | |
2016-02-24 17:41:09,379:INFO:requests.packages.urllib3.connectionpool:758: Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
2016-02-24 17:41:09,492:ERROR:__main__:1260: CA marked some of the authorizations as invalid, which likely means it could not access http://example.com/.well-known/acme-challenge/X. Did you set correct path in -d example.com:path or --default_root? Is there a warning log entry about unsuccessful self-verification? Are all your domains accessible from the internet? Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/3M-VDus9ONzj0LelmM6Y1JNQZAKN6kdO5xVRqe7WQd4 | |
Challenge validation has failed, see error log. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment