Yup, still having issues. Amazon Linux wants you to be explicit with the versions, but Let’s Encrypt is making tons of assumptions without checking for alternatives (e.g.
Looking at the script, it checks only
/usr/bin/python2 - which by default points to 2.6 on AWS. Here’s how my folder structure looks at the moment…
pip -> /etc/alternatives/pip
pip-python -> pip-2.6
python -> /etc/alternatives/python
python2 -> python2.6
python2-config -> python2.6-config
python-config -> /etc/alternatives/python-config
python-config2 -> python2.6-config
python-pip -> pip-2.6
virtualenv -> /etc/alternatives/virtualenv
Also, I should point out that all the symlink alternatives on my system (python, pip, virtualenv) use the Python 2.7 versions.
Beyond that though, is the way the script checks the OS. Amazon Linux stores it’s system information in
/etc/system-release-cpe for human and machine readability, respectively.
I’d modify the
./letsencrypt-auto file directly to use the correct version of python, but I’m not sure if I’ll run into other problems later… and there’s not much in the way of documentation for configuring it manually (or whether that’s even really an option).
But aside from the python issue, I still need to make the installer recognize my OS. In theory, the Red Hat version should be able to work fine on Amazon Linux, but I’d prefer confirmation before I spend the time setting up a test server to experiment on.