Could not access the challenge file for the hosts/domains: example.nl,
www.example.nl. Let's Encrypt requires every domain/host be publicly
accessible. Make sure that a valid DNS record exists for example.nl,
www.example.nl and that they point to this server's IP. If you don't want
these domains in your SSL certificate, then remove them from `site_hosts`.
See https://roots.io/trellis/docs/ssl for more details.
Letsencrypt is basically saying your domain is not pointing to your server. You need a real domain pointing to your server in order to letsencrypt to validate that you own this domain, and give you the certificate.
If you setup your domain correctly, this may be a DNS propagation problem, in this case you just have to wait.
I’m having this exact same problem. DNS is pointed correctly, all dns propagation sites show the correct ip, pinging the domain from different locations results in the correct IP, yet LE says it cannot find my site(s).
I didn’t change anything. The new server provision I had the site and home url set as https, and ssl set as true using letsencrypt. It just worked this time. I would recommend a fresh server provision, and go from there?
roots/trellis#565 enables Trellis to transition existing http sites to https. This update may resolve some issues that led to the error message Could not access the challenge file
Existing servers. If you try the Trellis update above on a server that has already been provisioned with the prior version of Trellis (i.e., on a server that already has an Nginx conf set up), you should first run:
One thing to note if using AWS EC2, make sure you add HTTP and HTTPS to the Security Group for inbound traffic. It will show you the same error if not.