• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Warnings when installing Let's encrypt on Ubuntu 14.04

LaurentR2D2

Plesk Certified Professional
Plesk Certified Professional
Hello,

When I try yo install Let's encrypt extension on Ubuntu Trusty, and le-installer is launched, I get this warning :

Creating virtual environment...
Updating letsencrypt and virtual environment dependencies...
/usr/local/psa/var/modules/letsencrypt/venv.8oGbY/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:315: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning.
SNIMissingWarning

Looking at the webpage mentioned above, I see that it's a problem of Python's version, and that to fix that I should install pyOpenSSL (python3-openssl package under Ubuntu). Is it enough just to install this package, or should I do something else after ? I've read that when pyOpenSSL is installed using "pip" command :

To use the Python OpenSSL bindings instead, you’ll need to install the required packages:

$ pip install pyopenssl ndg-httpsclient pyasn1

If cryptography fails to install as a dependency, make sure you have libffi available on your system and run pip install cryptography.

Once the packages are installed, you can tell urllib3 to switch the ssl backend to PyOpenSSL with inject_into_urllib3():

import urllib3.contrib.pyopenssl
urllib3.contrib.pyopenssl.inject_into_urllib3()

Now you can continue using urllib3 as you normally would.
 
I've still tried to install a certificate on a domain, and I get an error message. I don't know if it is related to the warning above :

Erreur: Échec de l'installation du certificat SSL Let's Encrypt : Failed letsencrypt execution: Traceback (most recent call last):
File "/opt/psa/var/modules/letsencrypt/venv/bin/letsencrypt", line 11, in <module>
sys.exit(main())
File "/usr/local/psa/var/modules/letsencrypt/venv.8oGbY/local/lib/python2.7/site-packages/letsencrypt/main.py", line 658, in main
"--strict-permissions" in cli_args)
File "/usr/local/psa/var/modules/letsencrypt/venv.8oGbY/local/lib/python2.7/site-packages/letsencrypt/le_util.py", line 105, in make_or_verify_dir
os.makedirs(directory, mode)
File "/usr/local/psa/var/modules/letsencrypt/venv.8oGbY/lib/python2.7/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/opt/psa/var/modules/letsencrypt/etc'
 
I've still tried to install a certificate on a domain, and I get an error message. I don't know if it is related to the warning above :

I've solved this problem. Watching all the errors messages, I've created the necessary folders with the good ownership. Now I have a certificate. I just need an answer for my first post :)

Thank you
 
Hi LaurentR2D2,

"normally", it should be sufficient to upgrade Python to > 2.7.11, so your choice to upgrade to Python 3 "should" solve your first warning.
Why the "" in the sentence? Well, there are always possible errors/issues/situations, where you have to add additional commands, but we can not guess them all, so I quoted some words in my answer. :)
 
Back
Top