# Automating renewal failed

**URL:** <https://community.letsencrypt.org/t/automating-renewal-failed/68277>\
**Category:** Server\
**Created:** [August 2, 2018, 4:36am UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277 "2018-08-02T04:36:22Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![luiscm0609](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@luiscm0609](https://community.letsencrypt.org/u/luiscm0609)\
**Post date:** [August 2, 2018, 4:36am UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/1 "2018-08-02T04:36:22Z")

</div>

I have two certificate. The firts certificate with two domain: [domian1.com](http://domian1.com), [domain2.com](http://domain2.com), and the last certificate with one domain: [domain3.com](http://domain3.com).  
I used the command for automating renewal: sudo certbot renew --dry-run  
But it show successfull only for the last certificate with one domain.

Attepmting to renew cert ([domain1.com](http://domain1.com)) from /etc/letsencrypt/renewal/domain1.com.conf produced and unexpected error :Failed authorization procedure. [domain2.com](http://domain2.com) (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [http://domain2.com/.well-know/acme-challenge/256wzkkmcdkmckdmckdncj:](http://domain2.com/.well-know/acme-challenge/256wzkkmcdkmckdmckdncj:)

I have correct permission on [domain1.com](http://domain1.com), [domain2.com](http://domain2.com) and [domain3.com](http://domain3.com) directories.

Thanks

---

<div class="post-metadata">

**Author:** ![stevenzhu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/stevenzhu/32/18864_2.png) [@stevenzhu](https://community.letsencrypt.org/u/stevenzhu)\
**Post date:** [August 2, 2018, 12:43pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/2 "2018-08-02T12:43:08Z")

</div>

Hi,

Please share us your domain names and full error message (without radiation), this will help us analyize the true errors…

Thank you

---

<div class="post-metadata">

**Author:** ![luiscm0609](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@luiscm0609](https://community.letsencrypt.org/u/luiscm0609)\
**Post date:** [August 2, 2018, 6:18pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/3 "2018-08-02T18:18:22Z")

</div>

Hi Steven

This is my domain in the first certificate: [mail.nube22.com](http://mail.nube22.com), [mail.enlanuve.com](http://mail.enlanuve.com) and the last certificate is [mx01.nube22.com](http://mx01.nube22.com)

This is the error message in the last certificate:

* * *

Processing /etc/letsencrypt/renewal/mail.nube22.com.conf

* * *

Cert not due for renewal, but simulating renewal for dry run  
Plugins selected: Authenticator webroot, Installer None  
Starting new HTTPS connection (1): [acme-staging-v02.api.letsencrypt.org](http://acme-staging-v02.api.letsencrypt.org)  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for [mail.nube22.com](http://mail.nube22.com)  
http-01 challenge for [mail.enlanuve.com](http://mail.enlanuve.com)  
Waiting for verification…  
Cleaning up challenges  
Attempting to renew cert ([mail.nube22.com](http://mail.nube22.com)) from /etc/letsencrypt/renewal/mail.nube22.com.conf produced an unexpected error: Failed authorization procedure. [mail.enlanuve.com](http://mail.enlanuve.com) (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [http://mail.enlanuve.com/.well-known/acme-challenge/sBtyUThD-0nF0ItGKf-G6CvJ942XCMp0WrWK50Efdms:](http://mail.enlanuve.com/.well-known/acme-challenge/sBtyUThD-0nF0ItGKf-G6CvJ942XCMp0WrWK50Efdms:) "

404 Not Found
# Not Found
\<p". Skipping. The following certs could not be renewed: /etc/letsencrypt/live/mail.nube22.com/fullchain.pem (failure)
* * *

\*\* DRY RUN: simulating ‘certbot renew’ close to cert expiry  
\*\* (The test certificates below have not been saved.)

The following certs were successfully renewed:  
/etc/letsencrypt/live/mx01.nube22.com/fullchain.pem (success)

The following certs could not be renewed:  
/etc/letsencrypt/live/mail.nube22.com/fullchain.pem (failure)  
\*\* DRY RUN: simulating ‘certbot renew’ close to cert expiry  
\*\* (The test certificates above have not been saved.)

* * *

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

- The following errors were reported by the server:

Thanks

---

<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:** [August 2, 2018, 6:24pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/4 "2018-08-02T18:24:54Z")

</div>

Hi @luiscm0609

> [@luiscm0609](#):
>
> This is my domain in the first certificate: [mail.nube22.com](http://mail.nube22.com), [mail.enlanuve.com](http://mail.enlanuve.com)

you have created a correct certificate yesterday:

[https://transparencyreport.google.com/https/certificates/EwTXd12NfYYtLdrOHedTk%2FGK%2FTB8srFR0pSyL7RPj6M%3D](https://transparencyreport.google.com/https/certificates/EwTXd12NfYYtLdrOHedTk%2FGK%2FTB8srFR0pSyL7RPj6M%3D)

> [mail.enlanuve.com](http://mail.enlanuve.com)  
> [mail.nube22.com](http://mail.nube22.com)

---

<div class="post-metadata">

**Author:** ![luiscm0609](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@luiscm0609](https://community.letsencrypt.org/u/luiscm0609)\
**Post date:** [August 2, 2018, 6:29pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/5 "2018-08-02T18:29:04Z")

</div>

Hi JuergenAuer

Yes I do, I have a correct certificate.  
My problem is when a run the automating renewal: certbot renew --dry-run.  
I want to put it in automatic renewal so I do not worry afterwards.

Thanks

---

<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:** [August 2, 2018, 6:45pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/6 "2018-08-02T18:45:34Z")

</div>

> [@luiscm0609](#):
>
> My problem is when a run the automating renewal: certbot renew --dry-run.  
> I want to put it in automatic renewal so I do not worry afterwards.

There is another thread:

> [@Deploy scripts function verify in dry-run mode](https://community.letsencrypt.org/t/deploy-scripts-function-verify-in-dry-run-mode/68327/2):
>
> H…

With the info, that dry-run doesn't support some hooks.

Perhaps rerun the complete command (which created the certificate yesterday) and use the stage system (there is a certbot option). There is an own limit.

---

<div class="post-metadata">

**Author:** ![luiscm0609](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@luiscm0609](https://community.letsencrypt.org/u/luiscm0609)\
**Post date:** [August 2, 2018, 6:55pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/7 "2018-08-02T18:55:08Z")

</div>

I’m a little confused. I thought that command: certbot renew --dry-run is for run automatic renewal certificate but I realize this command is only a test to verify that renewal will be successful.

Anyway why I get the error.

I don’t use hook in my directory renewal.

Thanks

---

<div class="post-metadata">

**Author:** ![luiscm0609](https://avatars.discourse-cdn.com/v4/letter/l/f1d935/32.png) [@luiscm0609](https://community.letsencrypt.org/u/luiscm0609)\
**Post date:** [August 2, 2018, 7:19pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/8 "2018-08-02T19:19:25Z")

</div>

Hi guys:

I found the problem why the command: certbot renew --dry-run it gave me error.  
I create my ceriticate for domian: [mail.nube22.com](http://mail.nube22.com) that was host on directory /var/www/. I then I change the directory to /home/mail but do not modify the renewal file /etc/letsencrypt/renewal/mail.nube22.com.conf. When I update the directory in the renewal file the command: certbot renew --dry-run run successful.

Thanks

---

<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:** [September 1, 2018, 7:19pm UTC](https://community.letsencrypt.org/t/automating-renewal-failed/68277/9 "2018-09-01T19:19:32Z")

</div>

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