please tell me how? i struggle almost 1 week to solve this sh*t =(
i recieve this message despite https://decoder.link/sslchecker/new.litportal.ru/443
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 21
Requesting a certificate for new.litportal.ru
Performing the following challenges:
http-01 challenge for new.litportal.ru
Waiting for verification...
Challenge failed for domain new.litportal.ru
http-01 challenge for new.litportal.ru
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: new.litportal.ru
Type: unauthorized
Detail: 91.215.42.110: Invalid response from https://litportal.ru/.well-known/acme-challenge/B7Kq2lvWYsEJi_OCm20-2SBY0fWDooUUoB0WGfxsPrg: 404
Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.
Cleaning up challenges
Some challenges have failed.
@tradewater I moved your posts into their own thread. Many times the same error message is caused by different reasons. It is better to debug them separately.
If you had posted in Help section first you would have been shown the form below. Please answer as much as you can. I removed questions you already answered
=============================================================================
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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of Certbot is (use certbot --version):
4 Likes
I just noticed the 21 which means you might have a large nginx config. You may need to add --nginx-sleep-seconds 5 to your command (or at least something larger than 1)
From the Certbot docs:
--nginx-sleep-seconds NGINX_SLEEP_SECONDS
Number of seconds to wait for nginx configuration changes to apply when reloading. (default: 1)
3 Likes
My web server is (include version): 192.168.166.176 (+ ddosguard balancer 31.44.83.199)
The operating system my web server runs on is (include version): ubuntu 20.04.6 LTS
My hosting provider, if applicable, is:
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, cli only
The version of Certbot is (use certbot --version): certbot 1.21.0
unfortunately didn't help =( but thank you
It looks like your ddos-guard server handles HTTP port 80 requests and redirects to several other URLs. That is supported although not ideal. It would be best to pass through the URL with /.well-known/acme-challenge/(token) to your nginx server for validation of your domain.
But, following all the redirects from your ddos-guard I eventually see an HTTP 403 error that says:
Checking your browser before accessing
Please wait a few seconds. Once this check is complete, the website will open automatically<
A Let's Encrypt server is making this HTTP request and does not interact with any scripting. Your system must reply with the proper challenge token.
Is there a way for you to send the HTTP requests directly to your nginx?
I am also puzzled. You got a cert for new.litportal.ru on Dec9 and your system uses it. What have you changed since then? Did you use this same certbot --nginx method then?
3 Likes
no, i just used "certbot" and selected "21" which is new.litportal.ru
i tried to remove an DNS "A" record " *.litportal.ru ", need some time to check if it worth it
But you must have also chosen the --nginx method either on command line or by Certbot prompting because we saw this:
You don't have to wait to try Let's Encrypt after that change. It does not cache DNS queries per the TTL. It looks at your authoritative DNS servers directly.
What is different now?
1 Like
But you must have also chosen the --nginx method either on command line or by Certbot prompting because we saw this:
no i didn't chose --nginx for the first time, i did it lately. Anyway it's not working
You got a cert for
new.litportal.ruon Dec9 and your system uses it. What have you changed since then?
that's the point. i did nothing, first time i tried to make a cert by "certbot" command without any options, just selected the domain, after that i see the actual certificate despite it was an error. im confused, i think its because our DNS, i found 1 more path for this domain and it leads to yandex DNS server. trying to solve this puzzle
for now, i've found that i had to add an A record to yandex dns master, and i was successful with releasing certificate..i think we can close this conv. in case i'll open new one
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.