Hi,
it looks like this is happening because your server is blocking requests to hidden directories (that start with a dot). You need to tweak your configuration to make sure that the .well-known directory is whitelisted.
A similar problem is discussed here: https://github.com/letsencrypt/acme-spec/issues/221
Can you check your configuration and adjust that? And please make sure to give me a heads up afterwards, whether it works or not. 🙂
Hey Felix
I’ve tried (and googled!) a lot of these variations, none of them worked unfortunately 🙁
More details here: http://superuser.com/questions/1099926/lets-encrypt-digitalocean-nginx-wordpress-installation-getting-a-403 Do you have any other pointers I could look at?
The thing is unless the challenge file is actually missing, this seems to be a server issue unrelated to the plugin directly, especially since you get a 403 when trying to access the URL. Unfortunately I’m not a server expert, so I can’t help you here (I would if I could!).
Have you verified that there are files in that directory after trying to run the certificate generation process?
You’re right, sorry about that!
I think I solved it now, by doing it via EasyEngine…so far so good. Should we close this?
Okay, I’m glad to hear that! 🙂
Hi @ernesto50, would you share the solution?
Hey there!
I basically had EasyEngine installed already and then used this: https://easyengine.io/docs/lets-encrypt/ – fairly easy!
Unfortunately I am using Mercury Vagrant (HGV) Deployment Playbook and can’t use that solution.
But yeah, thanks! I might get some idea how to solve it too.
