# Renewal of certificate and create new certificate is not working

**URL:** <https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193>\
**Category:** Help\
**Created:** [December 13, 2024, 6:34am UTC](https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193 "2024-12-13T06:34:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pweb](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@pweb](https://community.letsencrypt.org/u/pweb)\
**Post date:** [December 13, 2024, 6:34am UTC](https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193/1 "2024-12-13T06:34:10Z")

</div>

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](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:

- The following errors were reported by the server:

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

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [December 13, 2024, 3:04pm UTC](https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193/2 "2024-12-13T15:04:10Z")

</div>

> [@pweb](#):
>
> I ran this command: certbot --apache -d mx.pweb.ch

> [@pweb](#):
>
> Detail: 213.221.224.206: Invalid response from  
> [http://mx.pweb.ch/.well-known/acme-challenge/jthli9q7n3lG2aI5h9NFvqWuQOpqJiLuEGtdDlky76g:](http://mx.pweb.ch/.well-known/acme-challenge/jthli9q7n3lG2aI5h9NFvqWuQOpqJiLuEGtdDlky76g:)  
> 404

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

```nohighlight
sudo apache2ctl -t -D DUMP_VHOSTS

```

---

<div class="post-metadata">

**Author:** ![pweb](https://avatars.discourse-cdn.com/v4/letter/p/838e76/32.png) [@pweb](https://community.letsencrypt.org/u/pweb)\
**Post date:** [December 14, 2024, 5:51am UTC](https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193/3 "2024-12-14T05:51:41Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [December 14, 2024, 12:19pm UTC](https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193/4 "2024-12-14T12:19:50Z")

</div>

> [@pweb](#):
>
> It looks like the error was made at ISP which had a misconfiguration with nameservers.

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.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [January 13, 2025, 12:20pm UTC](https://community.letsencrypt.org/t/renewal-of-certificate-and-create-new-certificate-is-not-working/230193/5 "2025-01-13T12:20:14Z")

</div>

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