Good afternoon guys, just a quick question. I have recently updated certbot on all my servers so that the changes to authorisation will not effect my cron renewals. However, on two of my servers, after updating to v 0.29 the version is displayed correctly when querying the version. However, on others after updating and querying the version is still displays v 0.27 which is not correct. Further efforts to update it results in saying v 0.29 is already installed.
See imgBB link below, Is this a bug or is the correct version really not installed?
No problem, just as a side note: I'm not a expert when it comes to server commands so I'm going on a whim with what you're suggesting. This is what I get:
> > [root@itmserver-three ~]# rpm -qa | grep -iE "(letsencrypt|certbot)"
> certbot-0.25.1-1.el7.noarch
> python2-certbot-dns-google-0.25.1-1.el7.noarch
> python2-certbot-0.27.1-1.el7.noarch
> python2-certbot-apache-0.29.1-1.el7.noarch
> [root@itmserver-three ~]# which -a certbot
> /usr/bin/certbot
You have 0.25, 0.27 and 0.29 installed simultaneously, somehow.
If it was me I would try to basically remove all of them and start again, but @bmw might have some input about how you got here and what the best way to fix it is.
Ahh I see, I can see why this might be an issue then. Thank you for your aid, would it be possible to just remove the older versions and keep 0.29 without having to re-do the whole lot?
My only concern is that the removal of the older packages doesn’t accidentally remove dependencies used by the newer version (they shouldn’t, but who knows with this kind of thing ).
You can try it, not exactly sure what will happen.
You can uninstall all of them and your certificates and renewal settings should always be preserved in /etc/letsencrypt, but you can take a backup of that directory if paranoid.
If someone could shed some light on how to remove certbot from my server that would be grand, done some searches and they mostly relate to removing certificates rather than the program itself.
What’s going on here is Certbot is broken up into multiple components and only some of them have upgraded. This is fine in theory, but you should be able to upgrade them all to the latest version without removing them first by running something like:
Thank you for your reply, I executed what you recommended, however upon querying the verison I'm now faced with this:
Traceback (most recent call last):
File "/usr/bin/certbot", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 3011, in
parse_requirements(requires), Environment()
File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 626, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: acme>=0.29.0
As a side note: I run this first on one of my servers that was successfully showing v 0.29 and running the recommended command resulted in no errors.
Looks like you’ve found a bug in the packages being offered by EPEL. The package should depend on python2-acme version 0.29.0 or greater but it does not. I’ll report this to the package maintainers.
You can just run yum update to update all of packages on your system which is a good idea unless you have an explicit reason not to do so. Alternatively, you can just update the acme package by running yum update python2-acme and try running Certbot again.
).