validation fails and no files in /html for well-known path

[hgezim]

I can't get this to work :(

The validation fails:

docker logs nginx-letsencrypt
Sleep for 3600s
2018/01/29 18:08:04 Generated '/app/letsencrypt_service_data' from 7 containers
2018/01/29 18:08:04 Running '/app/update_certs'
2018/01/29 18:08:04 Watching docker events
/etc/nginx/certs/stats.ziprecipes.net /app
2018/01/29 18:08:04 Contents of /app/letsencrypt_service_data did not change. Skipping notification '/app/update_certs'
Reloading nginx docker-gen (using separate container nginx-gen)...
Creating/renewal stats.ziprecipes.net certificates... (stats.ziprecipes.net)
2018-01-29 18:08:05,601:INFO:simp_le:1538: Retrieving Let's Encrypt latest Terms of Service.
2018-01-29 18:08:07,165:WARNING:simp_le:1371: --email was not provided; ACME CA will have no way of contacting you.
2018-01-29 18:08:14,905:INFO:simp_le:1455: Generating new certificate private key
2018-01-29 18:08:19,981:ERROR:simp_le:1421: 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? Are all your domains accessible from the internet? Please check your domains' DNS entries, your host's network/firewall setup and your webserver config. If a domain's DNS entry has both A and AAAA fields set up, some CAs such as Let's Encrypt will perform the challenge validation over IPv6. If you haven't setup correct CAA fields or if your DNS provider does not support CAA, validation attempts after september 8, 2017 will fail.  Failing authorizations: https://acme-v01.api.letsencrypt.org/acme/authz/ZM4Rd9OlZ-Pml7Ch75_ReZcSK6-slJTCfw23PYeeBNc
Challenge validation has failed, see error log.

And the html dir that's supposed to map to .well-known/acme-challenge/ is empty.

Any help would be immensely appreciated.

[pierreozoux]

Sorry, We don't use this much, I put it there, I tested it, it worked, but I don't maintain it.
Maybe @almereyda can shime and help?
I know @almereyda use this setup, or the one that is forked from.

Then once we figured out how to solve, let's remove this folder, and point the libre.sh page to the right folder.

[unteem]

closing issue as we are archiving this repo, we are not maintaining it anymore

An nginx implementation for libre.sh will be pushed to https://lab.libreho.st/libre.sh