# Certificate not renewing

**URL:** <https://community.letsencrypt.org/t/certificate-not-renewing/129807>\
**Category:** Help\
**Created:** [July 30, 2020, 11:29am UTC](https://community.letsencrypt.org/t/certificate-not-renewing/129807 "2020-07-30T11:29:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Equil](https://avatars.discourse-cdn.com/v4/letter/e/ecccb3/32.png) [@Equil](https://community.letsencrypt.org/u/Equil)\
**Post date:** [July 30, 2020, 11:29am UTC](https://community.letsencrypt.org/t/certificate-not-renewing/129807/1 "2020-07-30T11:29:25Z")

</div>

My domain is:  
[comhost.equillex.ru](http://comhost.equillex.ru)

I ran this command:  
certbot-auto renew --post-hook “/usr/sbin/apachectl restart”

It produced this output:  
Waiting for verification…  
Challenge failed for domain [comhost.equillex.ru](http://comhost.equillex.ru)  
http-01 challenge for [comhost.equillex.ru](http://comhost.equillex.ru)  
Cleaning up challenges  
Attempting to renew cert ([comhost.equillex.ru](http://comhost.equillex.ru)) from /etc/letsencrypt/renewal/comhost.equillex.ru.conf produced an unexpected error: Some challenges have failed… Skipping.  
All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/comhost.equillex.ru/fullchain.pem (failure)

* * *

All renewal attempts failed. The following certs could not be renewed:  
/etc/letsencrypt/live/comhost.equillex.ru/fullchain.pem (failure)

* * *

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

My web server is (include version):  
apache 2.4.37  
The operating system my web server runs on is (include version):  
CentOS Linux 8.2.2004  
My hosting provider, if applicable, is:  
my server  
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):  
1.6.0

For some time, the update was standard, but on July 12 everything broke.  
There were no changes to the system settings.

---

<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:** [July 30, 2020, 11:33am UTC](https://community.letsencrypt.org/t/certificate-not-renewing/129807/2 "2020-07-30T11:33:44Z")

</div>

Hi @Equil

> [@Equil](#):
>
> For some time, the update was standard, but on July 12 everything broke.  
> There were no changes to the system settings.

that's wrong. You have created that bug.

> [http://comhost.equillex.ru/](http://comhost.equillex.ru/)

> # Bad Request
> 
> Your browser sent a request that this server could not understand.  
> Reason: You're speaking plain HTTP to an SSL-enabled server port.  
> Instead use the HTTPS scheme to access this URL, please.

Please fix your error.

Your port 80 is a https port, so it's impossible to use that port regular. May be a wrong port forwarding port 80 extern -\> port 443 intern.

---

<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:** [August 29, 2020, 11:33am UTC](https://community.letsencrypt.org/t/certificate-not-renewing/129807/3 "2020-08-29T11:33:53Z")

</div>

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