Renewal of certificate and create new certificate is not working

Help
1

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: mx.pweb.ch

I ran this command: certbot --apache -d mx.pweb.ch

It produced this output:
root@mx:/etc/apache2/sites-available# certbot --apache -d mx.pweb.ch
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Requesting a certificate for mx.pweb.ch
Performing the following challenges:
http-01 challenge for mx.pweb.ch
Waiting for verification...
Challenge failed for domain mx.pweb.ch
http-01 challenge for mx.pweb.ch
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

My web server is (include version): Apache/2.4.62 (Debian)

The operating system my web server runs on is (include version): Debian 11

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

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

2

Welcome @pweb

A "404" (Not Found) error is unusual with the certbot --apache option.

This usually indicates something wrong with your Apache config. Or possibly using some extensions in Apache that Certbot does not recognize (this is rare).

Would you please show output of below command. This is good place to start to debug

sudo apache2ctl -t -D DUMP_VHOSTS
4 Likes
3

Thanks @MikeMcQ

It looks like the error was made at ISP which had a misconfiguration with nameservers. They have updated their configuration and now it works. I was abel to get a new certificate.

3 Likes
4

That's odd. The IP in the public DNS right now is the same as shown in the error message above. I am not sure how changing nameservers would have made a difference.

But, glad you got a cert.

4 Likes
5

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