certbot est décédé. .. Au contraire, le certificat de communication https qui fonctionnait dans l'environnement de production a été soudainement détruit et il était difficile de le renvoyer, il s'agit donc d'un mémorandum.
ruby 2.5.7 Rails 5.2.3 AWS ec2 nginx puma
cd ~
rm -r -f certbot
git clone https://github.com/certbot/certbot.git
cd certbot/
chmod a+x certbot-auto
sudo ./certbot-auto --nginx --debug
* Tout ce que vous avez à faire est de répondre oui
Traceback (most recent call last):
File "<stdin>", line 27, in <module>
File "<stdin>", line 19, in create_venv
File "/usr/lib64/python2.7/subprocess.py", line 185, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib64/python2.7/subprocess.py", line 172, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib64/python2.7/subprocess.py", line 394, in __init__
errread, errwrite)
File "/usr/lib64/python2.7/subprocess.py", line 1047, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
alternatives --set python /usr/bin/python2.7
pkg_resources.DistributionNotFound: The 'virtualenv==15.1.0' distribution was not found and is required by the application
sudo pip uninstall virtualenv
pip install virtualenv==15.1.0
pkg_resources.DistributionNotFound: The 'pip==9.0.3' distribution was not found and is required by the application
sudo easy_install pip == 9.0.3
https://yoshinorin.net/2018/09/10/letsencrypt-cannot-update/
Recommended Posts