hello, cerbot renew is stuck its seems timeout but all of them is reachable from ping
Please provide more information.
ping works, but does ping6? Or HTTP or HTTPS connections? From the Internet?
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.
My domain is:
I ran this command:
It produced this output:
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):
here is the domain https://chat.ondr.co
https://updates-1.chat.ondr.co to updates-9.chat.ondr.co is not connecting
it works on browser and ping hosted on digital ocean
i did certbot renew
it only works on main domain not updates so i did
sudo certbot certonly --standalone -d chat.ondr.co -d
updates-0.chat.ondr.co -d updates-1.chat.ondr.co -d updates-
.chat.ondr.co -d updates-3.chat.ondr.co -d updates-4.chat.on
r.co -d updates-5.chat.ondr.co -d updates-6.chat.ondr.co -d
updates-7.chat.ondr.co -d updates-8.chat.ondr.co -d updates-
.chat.ondr.co -d updates-10.chat.ondr.co ```
it shows timeout so i tested
``` sudo certbot certonly --standalone -d chat.ondr.co -d
updates-0.chat.ondr.co -d updates-1.chat.ondr.co -d updates-
.chat.ondr.co -d updates-3.chat.ondr.co -d updates-4.chat.on
r.co -d updates-5.chat.ondr.co -d updates-6.chat.ondr.co -d
updates-7.chat.ondr.co -d updates-8.chat.ondr.co -d updates-
.chat.ondr.co -d updates-10.chat.ondr.co --staging ```
certbot renew command seems to renew
but the error IS NET ERR COMMON NAME INVALID
I can connect to your site, but I would expect "certbot certonly --standalone
" to fail -- with a different error -- while Nginx is running.
Could you provide more information? In particular, exactly what commands you ran, and exactly what output they produced?
working now with http only challenge
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.