Letsencrypt-auto just checks dependencies, nothing more

Help
1

Hello, I just cloned letsencrypt and ran it on my Debian 6 server running apache. All it seems to do is check dependencies and quits:

root@:~/letsencrypt# ./letsencrypt-auto --apache Bootstrapping dependencies for Debian-based OSes... Hit http://security.debian.org squeeze/updates Release.gpg Ign http://security.debian.org/ squeeze/updates/main Translation-en Ign http://security.debian.org/ squeeze/updates/main Translation-en_US Hit http://security.debian.org squeeze/updates Release Hit http://ftp.vserver-on.de squeeze Release.gpg Ign http://ftp.vserver-on.de/debian/ squeeze/contrib Translation-en Ign http://ftp.vserver-on.de/debian/ squeeze/contrib Translation-en_US Ign http://ftp.vserver-on.de/debian/ squeeze/main Translation-en Ign http://ftp.vserver-on.de/debian/ squeeze/main Translation-en_US Ign http://ftp.vserver-on.de/debian/ squeeze/non-free Translation-en Ign http://ftp.vserver-on.de/debian/ squeeze/non-free Translation-en_US Hit http://ftp.vserver-on.de squeeze Release Hit http://security.debian.org squeeze/updates/main Sources Hit http://security.debian.org squeeze/updates/main i386 Packages Hit http://ftp.vserver-on.de squeeze/main Sources Hit http://ftp.vserver-on.de squeeze/contrib Sources Hit http://ftp.vserver-on.de squeeze/non-free Sources Hit http://ftp.vserver-on.de squeeze/main i386 Packages Hit http://ftp.vserver-on.de squeeze/contrib i386 Packages Hit http://ftp.vserver-on.de squeeze/non-free i386 Packages Reading package lists... Done No LSB modules are available. No libaugeas0 version is available that's new enough to run the Let's Encrypt apache plugin... Reading package lists... Done Building dependency tree Reading state information... Done libaugeas0 is already the newest version. ca-certificates is already the newest version. dialog is already the newest version. gcc is already the newest version. libffi-dev is already the newest version. libssl-dev is already the newest version. python-dev is already the newest version. python is already the newest version. python-virtualenv is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. WARNING: Python 2.6 support is very experimental at present... if you would like to work on improving it, please ensure you have backups and then run this script again with the --debug flag!

I saw the line No libaugeas0 version is available that's new enough to run the Let's Encrypt apache plugin... and I got:

root@:~/letsencrypt# apt-get install libaugeas0 Reading package lists... Done Building dependency tree Reading state information... Done libaugeas0 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

So I really don’t know what’s going on here. I even tried using the certonly method, same deal. Can anyone help?

2

Relevant line from your output:

Append --debug to the command to use letsencrypt with Python 2.6 (which is shipped with Debian 6.0).

The language could probably be a bit more obvious here; I'll try to think of something and open a PR.

3

That's the main clue / information.

The client isn't really designed for python 2.6 You could use the --debug flag ( it works for some people ) or you could upgrade to python 2.7 ( the route I'd personally go)

1 Like
4

It’s worth noting that upgrading Python should be done carefully on older distributions because a lot of system packages depend on 2.6 specifically. I don’t personally use Debian 6.0 so unfortunately I can’t provide more than this warning.

Squeeze LTS support will end in February 2016 anyway, so maybe upgrading your OS would be an option.

5

Wait, really? Things actually depend on Python2.6? I would think they would be depending on Python 2.anything.

6

I’m not sure if they specifically target 2.6 as in that particular version of the language (I wasn’t being very clear), but maybe something else that changed in the ecosystem between 2.6 and 2.7. There’s some update-alternatives voodoo you need to do to get it working, apparently.

8

Thanks for the help, guys, the --debug flag was the hint I needed to get it working. I couldn’t use the --apache plugin because reasons, but I was able to use the certonly and standalone method to get a cert chain generated and up and running. I’ve been toying with the idea of upgrading my OS, but my server is a vserver from a semi-sketchy provider and I’ve already upgraded it from Debian 5 to 6, so the thought of risking an upgrade from 6 to 8 makes my head hurt, though it’s probably what I need to do.