# Attempting to parse the version 0.24.0 renewal configuration file found with version 0.14.2 of Certbot

**URL:** <https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993>\
**Category:** Help\
**Created:** [May 16, 2018, 7:20am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993 "2018-05-16T07:20:03Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 16, 2018, 7:20am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/1 "2018-05-16T07:20:03Z")

</div>

Hello!

I run command: sudo certbot --apache -d xxx sitename

And result:

This log line repeated 12 times all my https pages:

Attempting to parse the version 0.24.0 renewal configuration file found at /etc/letsencrypt/renewal/xxxx.conf with version 0.14.2 of Certbot. This might not work.

And final log lines are:  
Obtaining a new certificate  
Performing the following challenges:  
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA.

1. Do I get new certificate correctly when current certificates end?
2. What should I do to get new certificate to my current http page?  
I have site http conf file /etc/apache2/sites-available/xxx.conf  
and symbol link /etc/apache2/sites-enabled/xxx.conf -\> …/sites-available/xxx.conf

Yours Timo

---

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 16, 2018, 8:08am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/2 "2018-05-16T08:08:31Z")

</div>

Please tell me what shoud I do

- Do I get new certificates correctly when current certificates end?
- How I can get to my current http page certificate?
- Can I manually do something?

Must I update certbot ? I have python 2.7.6 and Ubuntu Server LTS 14.04

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [May 16, 2018, 8:13am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/3 "2018-05-16T08:13:46Z")

</div>

There seem to be two issues.

1. Your Certbot has somehow downgraded itself from 0.24 to 0.14. Or maybe you used `certbot-auto` previously?
2. Your Certbot is trying to use TLS-SNI, which has been disabled: [IMPORTANT: What you need to know about TLS-SNI validation issues](https://community.letsencrypt.org/t/important-what-you-need-to-know-about-tls-sni-validation-issues/50811)

You should be able to solve both problems by just upgrading Certbot back to the current version, you can use the Certbot Ubuntu PPA: [https://certbot.eff.org/lets-encrypt/ubuntutrusty-apache](https://certbot.eff.org/lets-encrypt/ubuntutrusty-apache)

Once you do that, running your command should just work. Using `--apache` should automatically install the certificate to your Apache virtual hosts, and it should also automatically renew.

---

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 16, 2018, 9:51am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/4 "2018-05-16T09:51:12Z")

</div>

“Or maybe you used certbot-auto previously?”  
Yes I use certbot-auto. My certbot version has years be 0.14.  
So I wonder if there something went wrong with current working certificates  
if I run:  
sudo add-apt-repository ppa:certbot/certbot  
sudo apt-get update

---

<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:** [May 16, 2018, 10:16am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/5 "2018-05-16T10:16:09Z")

</div>

Or maybe there are more than one installation:  
`find / -name certbot`  
`which certbot`  
`find / -name certbot-auto`  
`which certbot-auto`

---

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 17, 2018, 9:37am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/6 "2018-05-17T09:37:30Z")

</div>

I run those commands and result is here:  
I think there is just one installation  
or do I understand right?

root:~# find / -name certbot  
/usr/share/doc/certbot  
/usr/bin/certbot  
/usr/lib/python2.7/dist-packages/certbot  
/opt/eff.org/certbot  
/opt/eff.org/certbot/venv/bin/certbot  
/opt/eff.org/certbot/venv/lib/python2.7/site-packages/certbot  
/etc/cron.d/certbot  
/home/xxx/.local/share/letsencrypt/bin/certbot  
/home/xxx/.local/share/letsencrypt/lib/python2.7/site-packages/certbot

root:~# which certbot  
/usr/bin/certbot

root:~# find / -name certbot-auto  
/root/certbot-auto

root:~# which certbot-auto  
root:~#

Just one question is my mind. https certificate is  
new even certbot version has been old long time.  
So old version certbot-auto works right. I just can get  
totally new certificate for new site with this old version.

So I just run  
sudo apt-get install --only-upgrade certbot  
and I can get new certificate for new site?

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [May 17, 2018, 9:46am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/7 "2018-05-17T09:46:24Z")

</div>

You currently have two installations:

- `/root/certbot-auto`, which is a portable version of Certbot that is based on a shell script and upgrades itself automatically.
- `certbot`, which is installed from package repositories and upgrades are managed by the package manager.

Both installations will use the same certificate and renewal settings from `/etc/letsencrypt`, so you don’t need to worry about that.

In the past, you’ve obviously been using `certbot-auto`. I would suggest that you continue to use it for your new certificates, by running `/root/certbot-auto` instead of `certbot`.

If you wish, you can switch to `certbot` from package repositories instead, but you need to ensure that you install it from the PPA, as documented, or you will have an old version that might not work so well.

---

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 17, 2018, 10:07am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/8 "2018-05-17T10:07:04Z")

</div>

So I get new cerificate for new site just

sudo certbot-auto --apache -d xxx sitename

One question is:  
Ubuntu 14.04 LTS which i use End of Life date April 2019  
So after that I need to update it example  
Ubuntu 18.04 LTS. To get new certificates.  
Is that right? Or do certbot-auto get new  
certificates after that?  
I just had about one year time to prepare that changes.

Or do certbot-auto works correclty after April 2019.  
This https certificate refreshing is only outside thing in my  
websites.

---

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 17, 2018, 11:20am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/9 "2018-05-17T11:20:14Z")

</div>

So please tell me if you can: Do certbot-auto works Ubuntu 14.04 LTS after april 2019?

Thanks responses which you have give 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:** [May 17, 2018, 1:11pm UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/10 "2018-05-17T13:11:13Z")

</div>

Certbot will not stop working after April 2019.  
Ubuntu will stop providing updates after April 2019.

Two things:

1. Do you have a cron job to update your certs? if so, show that command.
2. When running certbot-auto it is best to do so from the same directory where it is located (/root/ in your case).

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [May 17, 2018, 6:43pm UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/11 "2018-05-17T18:43:11Z")

</div>

In particular, since `certbot-auto` probably won’t be in your `PATH`, you’ll need to specify a directory in the shell, which could be done with something like `sudo /root/certbot-auto` or `cd /root; sudo ./certbot-auto`.

---

<div class="post-metadata">

**Author:** ![timo](https://avatars.discourse-cdn.com/v4/letter/t/c4cdca/32.png) [@timo](https://community.letsencrypt.org/u/timo)\
**Post date:** [May 18, 2018, 5:04am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/12 "2018-05-18T05:04:48Z")

</div>

> Do you have a cron job to update your certs? if so, show that command.

cron job is done: /root/certbot-auto renew --quiet

ok so. sudo /root/certbot-auto --apache -d xxx sitename  
give me new certtificate for new site.

---

<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:** [June 17, 2018, 5:12am UTC](https://community.letsencrypt.org/t/attempting-to-parse-the-version-0-24-0-renewal-configuration-file-found-with-version-0-14-2-of-certbot/61993/13 "2018-06-17T05:12:28Z")

</div>

Closed on June 17, 2018, 5:12am UTC

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