Install error

Vico

Member
Hi there!, I´m trying to install like on the previous versions and I´m getting an error with the last one.
I´m installing from your EC2 AMI, everything fine, but then calling certbot get this error:

[ec2-user@ip-XXXXXXXXXXXXXX- tools]$ ./certbot-auto certonly --debug
Sorry, I don't know how to bootstrap Certbot on your operating system!
You will need to bootstrap, configure virtualenv, and run pip install manually.
Please see https://letsencrypt.readthedocs.org/en/latest/contributing.html#prerequisites
for more info.


I´m slightly worried about because I have 8 servers runing that needs a let´s encypt renew, can´t find the way to do this so I´m installing everything from the start, but find this!!!.
Thanks in advance Max!
Vico
 

Vico

Member
Someone knows the lines to perform a cerbot clean install directly to the server? I mean, from cerbot to my servers like:

"ssh -i "cerbotpleasehelp!" ec2-user@Ireallyneedhelp"....
"sudo yum localinstall -y cerbothelpmeorIdie....

Someone?
 

Max

Administrator
Staff member
Certbot can be installed on the server using the following commands:

1. Enable access to the EPEL repository on your server:

Code:
sudo yum install epel-release
2. Once the repository has been enabled, you can obtain the Certbot package:

Code:
sudo yum install certbot
The Certbot Let’s Encrypt client is now installed and ready to use.
You can verify your installation by asking for the version number of Certbot:

Code:
certbot --version
 

Vico

Member
Max, super sorry I had to left this for other work. But now I have to keep all this servers running.
I´m fighting to get a success with the renew but can´t fix this.


I tried a new install of certbot-auto
Tried deleting everythig also the /opt/eff.org/certbot folder
Everything returns me the same:

[root@ip-172-31-37-118 tools]# ./certbot-auto certonly --debug
Error: couldn't get currently installed version for /opt/eff.org/certbot/venv/bin/letsencrypt:
Traceback (most recent call last):
File "/opt/eff.org/certbot/venv/bin/letsencrypt", line 7, in <module>
from certbot.main import main
File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/certbot/main.py", line 2, in <module>
from certbot._internal import main as internal_main
File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/certbot/_internal/main.py", line 10, in <module>
import josepy as jose
File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/josepy/__init__.py", line 44, in <module>
from josepy.interfaces import JSONDeSerializable
File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/josepy/interfaces.py", line 7, in <module>
from josepy import errors, util
File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/josepy/util.py", line 7, in <module>
import OpenSSL

File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in <module>
from OpenSSL import crypto, SSL
File "/opt/eff.org/certbot/venv/local/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 12, in <module>
from cryptography import x509
ImportError: No module named cryptography


Thanks in advance master!
 

Vico

Member
The thing that is saving my ass is the only way I found:
Reinstall WCS from the May 2020 version 5.2.629, there when I call Cerbot it auto update to Cerbot 1.8 (Last version) and everything flows as allways
 

Vico

Member
Thanks Max, will try. Anyway pleeeeeese keep the 5.2.629 with the AMIs at AWS, is saving my life by the moment
 

Max

Administrator
Staff member
You can always choose previous AMI version while launching an instance
1600852354046.png
 
Top