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.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
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 my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.27.1
Let’t Encrypt can get renewal with private IP? this IP can not connect from outsite.
Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can’t work. You need a running webserver (http) and an open port 80. If it’s a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it’s a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge.
To use http-01 validation, you need a running webserver and an open port 80.
Isn’t this the machine with the public ip 22.214.171.124? Instead, is it a second machine? That can’t work. If you use webroot, certbot must be able to write in the /.well-known/acme-challenge subdirectory.
This machine have private ip (172.xx.xx.xx) and public ip (126.96.36.199)
If at local hosts (172.xx.xx.xx bitbucket.its-lab.net) and access to bitbucket.its-lab.net.
It’s work for me. (config port 80 and port 443 done)