# Certificate renewal failure

**URL:** <https://community.letsencrypt.org/t/certificate-renewal-failure/125918>\
**Category:** Help\
**Created:** [June 16, 2020, 4:11am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918 "2020-06-16T04:11:39Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jondslade](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jondslade](https://community.letsencrypt.org/u/jondslade)\
**Post date:** [June 16, 2020, 4:11am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/1 "2020-06-16T04:11:39Z")

</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: romanava.com.au

I ran this command: ./certbot-auto certonly --webroot -w /var/www/html/ -d romanava.com.au -d www.romanava.com.au

It produced this output:  
Do you want to expand and replace this existing certificate with the new  
certificate?

* * *

(E)xpand/©ancel: E  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for romanava.com.au  
http-01 challenge for www.romanava.com.au  
Using the webroot path /var/www/html for all unmatched domains.  
Waiting for verification…  
Challenge failed for domain www.romanava.com.au  
Challenge failed for domain romanava.com.au  
http-01 challenge for www.romanava.com.au  
http-01 challenge for romanava.com.au  
Cleaning up challenges  
Some challenges have failed.  
IMPORTANT NOTES:

- The following errors were reported by the server:  
Domain: www.romanava.com.au  
Type: unauthorized  
Detail: Invalid response from  
[https://www.romanava.com.au/.well-known/acme-challenge/\_DNFlrRSLMWuan4AGOLbfVx7REWe0-I355GhoSdqTQY](https://www.romanava.com.au/.well-known/acme-challenge/_DNFlrRSLMWuan4AGOLbfVx7REWe0-I355GhoSdqTQY)  
[34.87.236.192]: “\n\<html lang=“en-AU”  
class=“no-js” amp=”"\>\<meta charset=“UTF-8”\>\<meta  
name=“viewport” content=“width=device-”  
Domain: romanava.com.au  
Type: unauthorized  
Detail: Invalid response from  
[https://www.romanava.com.au/.well-known/acme-challenge/7-BUefFhIbFuA57JisnlBOCBsTN411CmTe4xfCP9hKo](https://www.romanava.com.au/.well-known/acme-challenge/7-BUefFhIbFuA57JisnlBOCBsTN411CmTe4xfCP9hKo)  
[34.87.236.192]: “\n\<html lang=“en-AU”  
class=“no-js” amp=”"\>\<meta charset=“UTF-8”\>\<meta  
name=“viewport” content=“width=device-”  
To fix these errors, please make sure that your domain name was  
entered correctly and the DNS A/AAAA record(s) for that domain  
contain(s) the right IP address.

My web server is (include version): Apache

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

My hosting provider, if applicable, is: Google Cloud

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.5.0

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 16, 2020, 4:50am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/2 "2020-06-16T04:50:36Z")

</div>

The challenges failed.  
I see that you used `--webroot -w /var/www/html/` for those names.  
Please show the vhost config for those names.

---

<div class="post-metadata">

**Author:** ![jondslade](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jondslade](https://community.letsencrypt.org/u/jondslade)\
**Post date:** [June 16, 2020, 5:32am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/3 "2020-06-16T05:32:09Z")

</div>

This is not my usual area. I am not sure how to obtain/show the vhost config within Google Cloud.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 16, 2020, 7:14pm UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/4 "2020-06-16T19:14:39Z")

</div>

It seems to be running Apache web server, so it should not be too complicated.  
Start with:  
`apachctl -S`

Why did you use `--webroot -w /var/www/html/` ?

---

<div class="post-metadata">

**Author:** ![jondslade](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jondslade](https://community.letsencrypt.org/u/jondslade)\
**Post date:** [June 17, 2020, 6:28am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/5 "2020-06-17T06:28:27Z")

</div>

I get the following response to: apachctl -S  
-bash: apachctl: command not found

I used that webfoot command, as I am trying to find similar issues in the support forum for renewing your SSL certificate on Google Cloud.

> [@Renew certbot ssl on Google Cloud](https://community.letsencrypt.org/t/renew-certbot-ssl-on-google-cloud/109323/4):
>
> H…

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 17, 2020, 6:31am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/6 "2020-06-17T06:31:32Z")

</div>

Sorry I mistyped that - missing an E  
try:  
`apachectl -S`

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 17, 2020, 6:32am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/7 "2020-06-17T06:32:18Z")

</div>

> [@jondslade](#):
>
> I used that webfoot command, as I am trying to find similar issues in the support forum for renewing your SSL certificate on Google Cloud.

The webroot must match the actual web ROOT used in your system.

---

<div class="post-metadata">

**Author:** ![jondslade](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jondslade](https://community.letsencrypt.org/u/jondslade)\
**Post date:** [June 17, 2020, 6:54am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/8 "2020-06-17T06:54:17Z")

</div>

I typed in: apachectl -S  
I now (still) get: -bash: apachectl: command not found

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [June 17, 2020, 6:57am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/9 "2020-06-17T06:57:35Z")

</div>

Must be a older version…  
Try:  
`httpd -S`

---

<div class="post-metadata">

**Author:** ![jondslade](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jondslade](https://community.letsencrypt.org/u/jondslade)\
**Post date:** [June 17, 2020, 7:22am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/10 "2020-06-17T07:22:04Z")

</div>

Thank you for your help. I was able to fix the problem with notes from another thread on the renewal via the Bitnami version of Wordpress.

---

<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:** [July 17, 2020, 7:22am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/125918/11 "2020-07-17T07:22:06Z")

</div>

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