I’m trying to set up an SSL certificate for a staging website that resides on the monkeymind.ltd domain.
I first attempted to create the certificate using the “sudo certbot --apache” command but this returns the “failed authorization procedure” (http-01) error.
After doing some extensive reading I have followed the common advice of creating the “.well-known/acme-challenge/” directories (with 755 permissions in the webroot) and placed a test file to see if it is available in a browser. This (http://monkeymind.ltd/.well-known/acme-challenge/test.txt) still returns a 404 and I’m unsure how to address the problem.
After that I tried to use the “sudo certbot certonly --webroot -w /var/www/html” command. This produces the same issue.
I’ve tried various permutations of the commands and from what I understand things are set up correctly (which clearly isn’t the case!). And now when I try to create the certificate again I encounter the rate limit error: “There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/”
So my questions are:
- Is this limit 24 hours? I assume there isn’t any way of doing “dummy test” to avoid the limit or to stop the problem reoccurring if I still cannot fix during my testing?
- How can I ensure access is possible to the /.well-known/acme-challenge directory (to fix the 404 issue)?
- Is there any other Apache configuration settings that I should double check?
I will do what I can to provide any terminal responses where possible, but with the rate limit, I’m somewhat hand-tied at the moment. But I have the letsencrypt logs if that helps?
Just for some background… this is a DigitalOcean droplet that was created by duplicating the production droplet (running Apache on Ubuntu 16.04). After that, I just amended the ServerName in the apache config to reflect the correct IP address.