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.
An unexpected error occurred:
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/
My web server is (include version): nginx
The operating system my web server runs on is (include version): Ubuntu 16.04.5 LTS
My hosting provider, if applicable, is: I am admin and developer fot the site
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
An unexpected error occurred:
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/
I do not see path /.well-known/acme-challenge in my system
It is not possible to reset the rate limits. I recommend you use our staging environment while you are debugging your setup to avoid hitting these rate limits.
I'm glad to hear you solved your problem.
I don't think this is a fair comment and would ask you to revisit our community guidelines. @JuergenAuer is a volunteer and was engaging earnestly to try and help you with your problems.
The thread that you linked to does mention that the user's configuration file was long, but apperas to concludes that the problem with the nginx configuration was that it was lacking
In order to use certbot --webroot, your existing web server has to be capable of serving the static challenge files from the specified webroot location. If its configuration prevents that, its configuration has to be changed in order to use --webroot.
