Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
Visible Content: This site requires Javascript to work, please enable Javascript in your browser or use a browser with Javascript support
Checking a not existing file in /.well-known/acme-challenge, a http status 404 / Not Found is expected. Instead your server sends a http status 200 and text content:
This site requires Javascript to work, please enable Javascript in your browser or use a browser with Javascript support
So you should create an exception that your application ignores /.well-known/acme-challenge.
The response like you have received with an error is an indication of so called “bot protection” installed on your host. Usually that would be something like testcookie-nginx-module. Unfortunately, when Let’s Encrypt “verification agents” are trying to fetch the files, they are also seen as bots and they can’t retrieve the files.
In theory, some sort of whitelisting might help (as for example in the module mentioned), but you might have no access to that configuration, plus you would need to reliably specify the IP ranges Let’s Encrypt is using. In practice, probably the best way to avoid the issue is to use the DNS verification instead.