Re-Install certificate after a fresh server configuration

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: cookwp.studio

I ran this command: sudo certbot certonly --webroot -w /var/www/cookwp.studio/public_html/ -d cookwp.studio -d www.cookwp.studio

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for cookwp.studio
http-01 challenge for www.cookwp.studio
Using the webroot path /var/www/cookwp.studio/public_html for all unmatched domains.
Waiting for verification…
Challenge failed for domain cookwp.studio
Challenge failed for domain www.cookwp.studio
http-01 challenge for cookwp.studio
http-01 challenge for www.cookwp.studio
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

My web server is (include version): VPS server

The operating system my web server runs on is (include version): CentOS 7

My hosting provider, if applicable, is: AdminVPS.ru

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 1.3.0

Are you sure that webroot path is correct?

What does Nginx’s error.log say?

Could “ddos-guard”, whatever that is, be blocking the requests?

Is that IP address correct?

What about using “sudo certbot --nginx” or “sudo certbot certonly --nginx” instead of the webroot plugin?

(P.S.: It’s not related to this issue, but your DNS service seems to have issues. It returns “refused” errors to some queries.)

1 Like

There was a typo in the website root path inside my site-config file. So sorry to bother.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.