# Renewal Problem

**URL:** <https://community.letsencrypt.org/t/renewal-problem/112180>\
**Category:** Help\
**Created:** [February 3, 2020, 11:08am UTC](https://community.letsencrypt.org/t/renewal-problem/112180 "2020-02-03T11:08:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![chewiesw](https://avatars.discourse-cdn.com/v4/letter/c/7993a0/32.png) [@chewiesw](https://community.letsencrypt.org/u/chewiesw)\
**Post date:** [February 3, 2020, 11:08am UTC](https://community.letsencrypt.org/t/renewal-problem/112180/1 "2020-02-03T11:08:52Z")

</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: [nchanga.com](http://nchanga.com)

I ran this command:certbot certonly -a webroot --webroot-path=/usr/share/nginx/html -d [nchanga.com](http://nchanga.com) -d [www.nchanga.com](http://www.nchanga.com) -d [mail.nchanga.com](http://mail.nchanga.com)

It produced this output:

root@mail:/etc/letsencrypt/renewal# certbot certonly -a webroot --webroot-path=/usr/share/nginx/html -d [nchanga.com](http://nchanga.com) -d [www.nchanga.com](https://protect-eu.mimecast.com/s/57i3Cz7QoT8LWmoUBRDEe?domain=nchanga.com) -d [mail.nchanga.com](https://protect-eu.mimecast.com/s/yIQ2CrmB6fw9QDlHzRT_4?domain=mail.nchanga.com)  
Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Cert is due for renewal, auto-renewing…  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for [nchanga.com](http://nchanga.com)  
http-01 challenge for [www.nchanga.com](https://protect-eu.mimecast.com/s/57i3Cz7QoT8LWmoUBRDEe?domain=nchanga.com)  
http-01 challenge for [mail.nchanga.com](https://protect-eu.mimecast.com/s/yIQ2CrmB6fw9QDlHzRT_4?domain=mail.nchanga.com)  
Using the webroot path /usr/share/nginx/html for all unmatched domains.  
Waiting for verification…  
Cleaning up challenges  
Failed authorization procedure. [nchanga.com](http://nchanga.com) (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [https://mail.nchanga.com/.well-known/acme-challenge/IRvxHWEAZHs934Vi7vR0KJj3lXiN7u\_PgvBNIs\_dbgs](https://protect-eu.mimecast.com/s/kmdACAMWxfrYp1AcOCl3d?domain=mail.nchanga.com) [[155.93.238.213](https://protect-eu.mimecast.com/s/PKchCwK2li0plR3CKXDfI?domain=155.93.238.213): “\r\n404 Not Found\r\n\<body bgcolor=“white”\>\r\n

# 404 Not Found
\r\n
* * *
”, [www.nchanga.com](https://protect-eu.mimecast.com/s/57i3Cz7QoT8LWmoUBRDEe?domain=nchanga.com) (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [https://mail.nchanga.com/.well-known/acme-challenge/Qd5qQvnsrT5esk4XCix03iHpcf4fTC3Tq1q2MQiCX9w](https://protect-eu.mimecast.com/s/PPpLCBPOyCPoWl5s76rvj?domain=mail.nchanga.com) [[155.93.238.213](https://protect-eu.mimecast.com/s/PKchCwK2li0plR3CKXDfI?domain=155.93.238.213): “\r\n404 Not Found\r\n\<body bgcolor=“white”\>\r\n
# 404 Not Found
\r\n
* * *
”, [mail.nchanga.com](https://protect-eu.mimecast.com/s/yIQ2CrmB6fw9QDlHzRT_4?domain=mail.nchanga.com) (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [https://mail.nchanga.com/.well-known/acme-challenge/Q3KdIu1Ns7yugBE9ehXhbb-DTHKKVxMGKAbuODMi–8](https://protect-eu.mimecast.com/s/Nqy9CDQ6AijPYOlinecBY?domain=mail.nchanga.com) [[155.93.238.213](https://protect-eu.mimecast.com/s/PKchCwK2li0plR3CKXDfI?domain=155.93.238.213): “\r\n404 Not Found\r\n\<body bgcolor=“white”\>\r\n
# 404 Not Found
\r\n
* * *
”

IMPORTANT NOTES:

- The following errors were reported by the server:

Domain: [nchanga.com](http://nchanga.com)  
Type: unauthorized  
Detail: Invalid response from  
[https://mail.nchanga.com/.well-known/acme-challenge/IRvxHWEAZHs934Vi7vR0KJj3lXiN7u\_PgvBNIs\_dbgs](https://protect-eu.mimecast.com/s/kmdACAMWxfrYp1AcOCl3d?domain=mail.nchanga.com)  
[[155.93.238.213](https://protect-eu.mimecast.com/s/PKchCwK2li0plR3CKXDfI?domain=155.93.238.213): “\r\n404 Not  
Found\r\n\<body bgcolor=“white”\>\r\n

# 404 Not Found
\r\n
* * *
”

Domain: [www.nchanga.com](https://protect-eu.mimecast.com/s/57i3Cz7QoT8LWmoUBRDEe?domain=nchanga.com)  
Type: unauthorized  
Detail: Invalid response from  
[https://mail.nchanga.com/.well-known/acme-challenge/Qd5qQvnsrT5esk4XCix03iHpcf4fTC3Tq1q2MQiCX9w](https://protect-eu.mimecast.com/s/PPpLCBPOyCPoWl5s76rvj?domain=mail.nchanga.com)  
[[155.93.238.213](https://protect-eu.mimecast.com/s/PKchCwK2li0plR3CKXDfI?domain=155.93.238.213): “\r\n404 Not  
Found\r\n\<body bgcolor=“white”\>\r\n

# 404 Not Found
\r\n
* * *
”

Domain: [mail.nchanga.com](https://protect-eu.mimecast.com/s/yIQ2CrmB6fw9QDlHzRT_4?domain=mail.nchanga.com)  
Type: unauthorized  
Detail: Invalid response from  
[https://mail.nchanga.com/.well-known/acme-challenge/Q3KdIu1Ns7yugBE9ehXhbb-DTHKKVxMGKAbuODMi–8](https://protect-eu.mimecast.com/s/Nqy9CDQ6AijPYOlinecBY?domain=mail.nchanga.com)  
[[155.93.238.213](https://protect-eu.mimecast.com/s/PKchCwK2li0plR3CKXDfI?domain=155.93.238.213): “\r\n404 Not  
Found\r\n\<body bgcolor=“white”\>\r\n

# 404 Not Found
\r\n
* * *
”

To fix these errors, please make sure that your domain name was  
entered correctly and the DNS A record(s) for that domain  
contain(s) the right IP address.

My web server is (include version): nginx

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

My hosting provider, if applicable, is: n/a

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):

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

The strange thing this was working for ages, auto-renewing like clockwork. Nothing has changed.

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [February 3, 2020, 11:19am UTC](https://community.letsencrypt.org/t/renewal-problem/112180/2 "2020-02-03T11:19:17Z")

</div>

Hi @chewiesw

> [@chewiesw](#):
>
> http-01 challenge for [nchanga.com](http://nchanga.com)  
> http-01 challenge for [www.nchanga.com](https://protect-eu.mimecast.com/s/57i3Cz7QoT8LWmoUBRDEe?domain=nchanga.com)  
> http-01 challenge for [mail.nchanga.com](https://protect-eu.mimecast.com/s/yIQ2CrmB6fw9QDlHzRT_4?domain=mail.nchanga.com)  
> Using the webroot path /usr/share/nginx/html for all unmatched domains.

simple answer: If webroot doesn't work, your webroot is wrong.

Checking your first domain there are redirects to mail... [https://check-your-website.server-daten.de/?q=nchanga.com](https://check-your-website.server-daten.de/?q=nchanga.com)

What says

```nohighlight
nginx -T

```

---

<div class="post-metadata">

**Author:** ![chewiesw](https://avatars.discourse-cdn.com/v4/letter/c/7993a0/32.png) [@chewiesw](https://community.letsencrypt.org/u/chewiesw)\
**Post date:** [February 3, 2020, 11:57am UTC](https://community.letsencrypt.org/t/renewal-problem/112180/3 "2020-02-03T11:57:20Z")

</div>

Wow thanks for the quick response. You are indeed correct my webroot was wrong. I managed to generate a new cert. Will auto-renew no resume working?

Thank you

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [February 3, 2020, 2:58pm UTC](https://community.letsencrypt.org/t/renewal-problem/112180/4 "2020-02-03T14:58:11Z")

</div>

> [@chewiesw](#):
>
> Will auto-renew no resume working?

Check your Certbot config files. There the new webroot should be visible.

---

<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:** [March 4, 2020, 2:58pm UTC](https://community.letsencrypt.org/t/renewal-problem/112180/5 "2020-03-04T14:58:15Z")

</div>

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