# Error - renew SSL certificate whith certbot

**URL:** <https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559>\
**Category:** Help\
**Created:** [January 31, 2024, 4:15pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559 "2024-01-31T16:15:22Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 4:15pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/1 "2024-01-31T16:15:22Z")

</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. [crt.sh | 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: [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)

I ran this command: certbot renew

It produced this output: Saving debug log to C:\Certbot\log\letsencrypt.log

* * *

Processing C:\Certbot\renewal\642f07948b0f.sn.mynetname.net.conf

* * *

Renewing an existing certificate for [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:  
Domain: [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)  
Type: unauthorized  
Detail: 181.198.213.18: Invalid response from [http://642f07948b0f.sn.mynetname.net/.well-known/acme-challenge/sPnMDVr-AqDfLKD\_Ux8qrQjIbOi\_-LK\_OJFH\_589wdQ:](http://642f07948b0f.sn.mynetname.net/.well-known/acme-challenge/sPnMDVr-AqDfLKD_Ux8qrQjIbOi_-LK_OJFH_589wdQ:) 404

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Failed to renew certificate [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net) with error: Some challenges have failed.

* * *

All renewals failed. The following certificates could not be renewed:  
C:\Certbot\live\642f07948b0f.sn.mynetname.net\fullchain.pem (failure)

* * *

1 renew failure(s), 0 parse failure(s)  
Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): I dont know about this.

The operating system my web server runs on is (include version): Windows Server 2016 Standard

My hosting provider, if applicable, is: I dont know about this.

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): I dont know about this.

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

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 4:17pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/2 "2024-01-31T16:17:46Z")

</div>

We use laragon for laravel backend api, and is for flutter/android for frontend.

---

<div class="post-metadata">

**Author:** ![linkp](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/linkp/32/60089_2.png) [@linkp](https://community.letsencrypt.org/u/linkp)\
**Post date:** [January 31, 2024, 4:30pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/3 "2024-01-31T16:30:23Z")

</div>

> [@JOSENAVAS46](#):
>
> Windows Server 2016

> [@JOSENAVAS46](#):
>
> certbot 1.18.0

While that is a bit older version of certbot, rather than update it, you are going to want to find a new ACME client. Certbot is dropping its Windows support.

> [@Certbot Discontinuing Windows Beta Support in 2024](https://community.letsencrypt.org/t/certbot-discontinuing-windows-beta-support-in-2024/208101):
>
> F…

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:03pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/4 "2024-01-31T17:03:10Z")

</div>

thanks, im going to update, if i need more help, please dont leave me, (sorry for my english)

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:07pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/5 "2024-01-31T17:07:59Z")

</div>

I update it, to Certbot 2.8.0, now i run this comand  
certbot renew -v  
and that gime me this:  
certbot renew -v  
Saving debug log to C:\Certbot\log\letsencrypt.log

* * *

Processing C:\Certbot\renewal\642f07948b0f.sn.mynetname.net.conf

* * *

Certificate is due for renewal, auto-renewing...  
Plugins selected: Authenticator webroot, Installer None  
Renewing an existing certificate for [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)  
Performing the following challenges:  
http-01 challenge for [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)  
Waiting for verification...  
Challenge failed for domain [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)  
http-01 challenge for [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:  
Domain: [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)  
Type: unauthorized  
Detail: 181.198.213.18: Invalid response from [http://642f07948b0f.sn.mynetname.net/.well-known/acme-challenge/U2vTH3FtdNI6fWIdJxkdGbgAZej6PCRTlj7S-OaarsE:](http://642f07948b0f.sn.mynetname.net/.well-known/acme-challenge/U2vTH3FtdNI6fWIdJxkdGbgAZej6PCRTlj7S-OaarsE:) 404

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Cleaning up challenges  
Failed to renew certificate [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net) with error: Some challenges have failed.

* * *

All renewals failed. The following certificates could not be renewed:  
C:\Certbot\live\642f07948b0f.sn.mynetname.net\fullchain.pem (failure)

* * *

1 renew failure(s), 0 parse failure(s)  
Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details.

---

<div class="post-metadata">

**Author:** ![linkp](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/linkp/32/60089_2.png) [@linkp](https://community.letsencrypt.org/u/linkp)\
**Post date:** [January 31, 2024, 5:12pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/6 "2024-01-31T17:12:41Z")

</div>

You miss the important part. You need to find another ACME client to replace Certbot. Certbot is dropping support for Windows.

You may also want to debug HTTP access to your webserver.

[https://letsdebug.net/](https://letsdebug.net/)

---

<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:** [January 31, 2024, 5:14pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/7 "2024-01-31T17:14:43Z")

</div>

What shows?:  
`httpd -t -D DUMP_VHOSTS`

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:16pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/8 "2024-01-31T17:16:40Z")

</div>

```nohighlight
VirtualHost configuration:
*:80 is a NameVirtualHost
 default server Laragon (C:/laragon/etc/apache2/sites-enabled/00-default.conf:29)
 port 80 namevhost Laragon (C:/laragon/etc/apache2/sites-enabled/00-default.conf:29)
 port 80 namevhost AdmMovilApi.test (C:/laragon/etc/apache2/sites-enabled/auto.AdmMovilApi.test.conf:4)
      wild alias *.AdmMovilApi.test
 port 80 namevhost apiapolo2021.test (C:/laragon/etc/apache2/sites-enabled/auto.apiapolo2021.test.conf:4)
      wild alias *.apiapolo2021.test
*:8282 is a NameVirtualHost
 default server Laragon (C:/laragon/etc/apache2/sites-enabled/00-default.conf:35)
 port 8282 namevhost Laragon (C:/laragon/etc/apache2/sites-enabled/00-default.conf:35)
 port 8282 namevhost AdmMovilApi.test (C:/laragon/etc/apache2/sites-enabled/auto.AdmMovilApi.test.conf:14)
        wild alias *.AdmMovilApi.test
 port 8282 namevhost apiapolo2021.test (C:/laragon/etc/apache2/sites-enabled/auto.apiapolo2021.test.conf:14)
        wild alias *.apiapolo2021.test

```

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:18pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/9 "2024-01-31T17:18:47Z")

</div>

Can you please recommend one to me?

---

<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:** [January 31, 2024, 5:20pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/10 "2024-01-31T17:20:04Z")

</div>

There is no vhost to cover the name being requested:

> [@JOSENAVAS46](#):
>
> My domain is: [642f07948b0f.sn.mynetname.net](http://642f07948b0f.sn.mynetname.net)

You should have a working HTTP site **before** you try to secure it.

---

<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:** [January 31, 2024, 5:21pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/11 "2024-01-31T17:21:09Z")

</div>

What shows?:  
`certbot certificates`

---

<div class="post-metadata">

**Author:** ![linkp](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/linkp/32/60089_2.png) [@linkp](https://community.letsencrypt.org/u/linkp)\
**Post date:** [January 31, 2024, 5:23pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/12 "2024-01-31T17:23:09Z")

</div>

I don't use Windows so I cannot reccomend one. I can share a link to a page that lists options. You will need to evaluate and decide on your own or with the guidance from members here who use Windows.

> **[ACME Client Implementations - Let's Encrypt](https://letsencrypt.org/docs/client-options/)**
>
> Last updated: Jul 22, 2023 | See all Documentation Let’s Encrypt uses the ACME protocol to verify that you control a given domain name and to issue you a certificate. To get a Let’s Encrypt certificate, you’ll need to choose a piece...

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:24pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/13 "2024-01-31T17:24:13Z")

</div>

`Saving debug log to C:\Certbot\log\letsencrypt.log`

```nohighlight
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
  Certificate Name: 642f07948b0f.sn.mynetname.net
    Serial Number: 49099d7d9091251fc53f355bae3593c6241
    Key Type: RSA
    Domains: 642f07948b0f.sn.mynetname.net
    Expiry Date: 2024-01-26 07:35:17+00:00 (INVALID: EXPIRED)
    Certificate Path: C:\Certbot\live\642f07948b0f.sn.mynetname.net\fullchain.pem
    Private Key Path: C:\Certbot\live\642f07948b0f.sn.mynetname.net\privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

```

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:24pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/14 "2024-01-31T17:24:43Z")

</div>

oh, thanks, im goint to check

---

<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:** [January 31, 2024, 5:25pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/15 "2024-01-31T17:25:16Z")

</div>

How did you get that cert?

Please show the renewal config file for it:

> [@JOSENAVAS46](#):
>
> `C:\Certbot\renewal\642f07948b0f.sn.mynetname.net.conf`

---

<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:** [January 31, 2024, 5:25pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/16 "2024-01-31T17:25:18Z")

</div>

There are also specific examples given in the thread posted earlier. Look at the "Off Ramps" section on this page

> [@Certbot Discontinuing Windows Beta Support in 2024](https://community.letsencrypt.org/t/certbot-discontinuing-windows-beta-support-in-2024/208101):
>
> F…

---

<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:** [January 31, 2024, 5:26pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/17 "2024-01-31T17:26:22Z")

</div>

On Windows systems, I've used "`https://CertifyTheWeb.com/`" without any issues 🙂

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:27pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/18 "2024-01-31T17:27:32Z")

</div>

its my jobs server, not mine, im a intern, and they send me to solve this

---

<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:** [January 31, 2024, 5:29pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/19 "2024-01-31T17:29:47Z")

</div>

Ok, I understand.

> [@rg305](#):
>
> Please show the renewal config file for it:
> 
> > [@JOSENAVAS46](#):
> >
> > `C:\Certbot\renewal\642f07948b0f.sn.mynetname.net.conf`

---

<div class="post-metadata">

**Author:** ![JOSENAVAS46](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/josenavas46/32/77416_2.png) [@JOSENAVAS46](https://community.letsencrypt.org/u/JOSENAVAS46)\
**Post date:** [January 31, 2024, 5:30pm UTC](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559/20 "2024-01-31T17:30:23Z")

</div>

```nohighlight
# renew_before_expiry = 30 days
version = 1.18.0
archive_dir = C:\Certbot\archive\642f07948b0f.sn.mynetname.net
cert = C:\Certbot\live\642f07948b0f.sn.mynetname.net\cert.pem
privkey = C:\Certbot\live\642f07948b0f.sn.mynetname.net\privkey.pem
chain = C:\Certbot\live\642f07948b0f.sn.mynetname.net\chain.pem
fullchain = C:\Certbot\live\642f07948b0f.sn.mynetname.net\fullchain.pem

# Options used in the renewal process
[renewalparams]
account = 22a91d0747dd70730851089cdfa05d13
authenticator = webroot
server = https://acme-v02.api.letsencrypt.org/directory
[[webroot_map]]
642f07948b0f.sn.mynetname.net = C:\laragon\www\apiapolo2021\public

```

[Next page](https://community.letsencrypt.org/t/error-renew-ssl-certificate-whith-certbot/212559.md?page=2)
