Solving the "Attempting to parse the version" problem

Help
1

Good morning!

I hope someone can help me with a couple of questions regarding the information below.

  • How is it possible to have a config file with the version 1.9.0 and two more with the version 0.38.0 when my certbot version is 0.31.0 (and I just made apt-get update and upgrade to make sure I was using the last one).

  • Is it safe to delete these 3 configuration files that certbot complains about? I wonder if then a new but correctly versioned configuration file is going to be generated when I do another renew or I'm going to break something.
    (or if not by deleting them, how should I fix these files?)

I don't think it's relevant but fyi, this certbot is installed in an nginx docker container with all the files mounted to the host, necessary ports exposed and so on.

My domain is: backoffice.moblesciurans.com, codi.coop

I ran this command: certbot certificates

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Attempting to parse the version 1.9.0 renewal configuration file found at /etc/letsencrypt/renewal/backoffice.moblesciurans.com.conf with version 0.31.0 of Certbot. This might not work.
Attempting to parse the version 0.38.0 renewal configuration file found at /etc/letsencrypt/renewal/codi.coop.conf with version 0.31.0 of Certbot. This might not work.
Attempting to parse the version 0.38.0 renewal configuration file found at /etc/letsencrypt/renewal/gitea.codi.coop.conf with version 0.31.0 of Certbot. This might not work.

Found the following certs:
Certificate Name: activitats.lesguardcoop.cat
Domains: activitats.lesguardcoop.cat
Expiry Date: 2021-03-30 11:16:49+00:00 (VALID: 53 days)
Certificate Path: /etc/letsencrypt/live/activitats.lesguardcoop.cat/fullchain.pem
Private Key Path: /etc/letsencrypt/live/activitats.lesguardcoop.cat/privkey.pem
Certificate Name: backoffice.moblesciurans.com
Domains: backoffice.moblesciurans.com
Expiry Date: 2021-02-21 11:32:16+00:00 (VALID: 16 days)
Certificate Path: /etc/letsencrypt/live/backoffice.moblesciurans.com/fullchain.pem
Private Key Path: /etc/letsencrypt/live/backoffice.moblesciurans.com/privkey.pem
Certificate Name: codi.coop
Domains: codi.coop
Expiry Date: 2021-03-13 22:01:48+00:00 (VALID: 36 days)
Certificate Path: /etc/letsencrypt/live/codi.coop/fullchain.pem
Private Key Path: /etc/letsencrypt/live/codi.coop/privkey.pem
Certificate Name: equip.lesguardcoop.cat
Domains: equip.lesguardcoop.cat
Expiry Date: 2021-03-30 11:18:44+00:00 (VALID: 53 days)
Certificate Path: /etc/letsencrypt/live/equip.lesguardcoop.cat/fullchain.pem
Private Key Path: /etc/letsencrypt/live/equip.lesguardcoop.cat/privkey.pem
Certificate Name: gitea.codi.coop
Domains: gitea.codi.coop
Expiry Date: 2021-03-13 22:01:56+00:00 (VALID: 36 days)
Certificate Path: /etc/letsencrypt/live/gitea.codi.coop/fullchain.pem
Private Key Path: /etc/letsencrypt/live/gitea.codi.coop/privkey.pem
Certificate Name: noucens.escoltes.org
Domains: noucens.escoltes.org
Expiry Date: 2021-04-22 09:49:46+00:00 (VALID: 76 days)
Certificate Path: /etc/letsencrypt/live/noucens.escoltes.org/fullchain.pem
Private Key Path: /etc/letsencrypt/live/noucens.escoltes.org/privkey.pem
Certificate Name: www.codi.coop
Domains: www.codi.coop
Expiry Date: 2021-03-30 09:52:22+00:00 (VALID: 53 days)
Certificate Path: /etc/letsencrypt/live/www.codi.coop/fullchain.pem
Private Key Path: /etc/letsencrypt/live/www.codi.coop/privkey.pem

My web server is (include version): nginx/1.19.6

The operating system my web server runs on is (include version): Debian GNU/Linux 10

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 0.31.0

1 Like
2

If you used (the new deprecated) certbot-auto at any point, it's possible. certbot-auto has long offered much newer versions of Certbot than have ever been available from the Debian stable apt repositories.

Ditto if you used the Certbot snap (which is now the recommended installation method for Debian FWIW).

Ditto if you used the Certbot Docker images.

These complaints are only warnings.

In general, you can disregard the warning unless it causes Certbot to crash, or you are relying on some feature from a newer version of Certbot.

2 Likes
3

Thank you very much!

Yes it was because of certbot-auto, then.

It's not crashing, so I'll let them alone and ignore the warnings.

Thanks again, that was so helpful :slight_smile:

El dv., 5 de febr. 2021, 10:51, _az via Let's Encrypt Community Support <letsencrypt@discoursemail.com> va escriure:

2 Likes
4

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