Certbot 0.18.0 Appears not to be working with Webmin Because of New Install Path

Dear Community,

since th elast upgrade of the server that is uptodate will all is module now, Letsencrypt is no more working and showing an error when trying to create a certificate.

this is Webmin Virtualmin 6.00.gpl that is being used on a CentOS Linux 7.4.1708

here are the errors:

Requesting a certificate for dsd.fr, www.dsd.fr from Let’s Encrypt …
… request failed : Web-based validation failed :
Traceback (most recent call last):
File “/bin/letsencrypt”, 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: cryptography>=1.2
DNS-based validation failed :
Traceback (most recent call last):
File “/bin/letsencrypt”, 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: cryptography>=1.2

Does anyone know what the problem is?

Many Thanks

Marc

Please include the complete command that you ran and the version of LE/certbot

hello,

I don’t enter any command, I just click on the Request Certificate button in the Webmin page:
Virtualmin > server configuration > manage SSL certificate > Let’s Encrypt

Marc

hi @marclaurent

It’s best to log this with the webmin forums or support

As they write the client they are best suited to help you

Andrei

Thanks,

I’ll try that and will let you know

Marc

Hello again,

browsing around the forums i did find this

they say that “Letsencrypt changed their install path which breaks all software that used LE in the past”

and the date when it happended is more or less the same date as it did stop to work for me in Virtualmin in middle of this month

is this true that Letsencrypt changed some paths?

Marc

yes they did in version 0.18.0

it wasn't as easy to find as i thought. If webmin (i am not sure) have hard coded like ISPCOnfig this will cause issues with certbot 0.18.0

you can specify to install a specific version of cerbot by using pip install certbot==0.17.0 for example

Andrei

this was also outlined with the correct path in the article you shared :wink:

ISPconfig released a fix script for their code so as suggested before now that you have all the facts go talk to webmin about what you are experiencing

A) Seeing if they already have a fix
B) Seeing if they have any recommendations.

It's not that I am trying to blow off. I am trying to get you to spend your time in a place where can best assist you.

Andrei

my version of cerbot is

certbot	A free, automated certificate authority client	Running latest 0.18.1-1.el7	Installed
python2-certbot	Python 2 libraries used by certbot	Running latest 0.18.1-1.el7	Installed

No idea if Webmin and Virtualmin are hardcoding the path or not…

I have outlined the course of action to take in the post above

I am not going to assist any further

Andrei

Hello,

I just solved the problem. Certbot is using a lot of dependencies and it seems the upgrade manager of Webmin/Virtualmin didn’t keep everything up to date despite what it was displaying.

I did only update the server manually with the command : yum -y update

It did upgrade and replace a few dependencies
Installed:
python-gobject-base.x86_64 0:3.22.0-1.el7 python2-cryptography.x86_64 0:1.7.2-1.el7 python2-psutil.x86_64 0:2.2.1-2.el7
python2-pyasn1.noarch 0:0.1.9-7.el7

Dependency Installed:
python-idna.noarch 0:2.4-1.el7 python-ipaddress.noarch 0:1.0.16-2.el7

Replaced:
pygobject3-base.x86_64 0:3.14.0-3.el7 python-cryptography.x86_64 0:0.8.2-1.el7 python-psutil.x86_64 0:2.2.1-1.el7
python-pyasn1.noarch 0:0.1.6-2.el7

then to be sure I did reboot the ssl server as well as the apach server and now everything is again working fine…

Thanks Andrei for you help anyway, I hope this will help someone to read this post

Marc

1 Like

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