# CentOS 7 setup missing python pieces

**URL:** <https://community.letsencrypt.org/t/centos-7-setup-missing-python-pieces/6077>\
**Category:** Help\
**Created:** [December 7, 2015, 7:21am UTC](https://community.letsencrypt.org/t/centos-7-setup-missing-python-pieces/6077 "2015-12-07T07:21:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jared\_Busch](https://avatars.discourse-cdn.com/v4/letter/j/b9e5f3/32.png) [@Jared\_Busch](https://community.letsencrypt.org/u/Jared_Busch)\
**Post date:** [December 7, 2015, 7:21am UTC](https://community.letsencrypt.org/t/centos-7-setup-missing-python-pieces/6077/1 "2015-12-07T07:21:12Z")

</div>

I have a [full setup thread](http://mangolassi.it/topic/7127/setting-up-letsencrypt-on-a-centos-7-nginx-proxy) over on the [Mangolassi.it community](http://mangolassi.it) but here is the tl;dr

I ran into an error almost immediately.  
`./letsencrypt-auto --help` resulted in this.

```
Complete!
Creating virtual environment...
Updating letsencrypt and virtual environment dependencies...../root/.local/share/letsencrypt/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
./root/.local/share/letsencrypt/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
.

```

Searching here did not turn up anything specific about this, but I did find a thread about Python 2.7 and Centos 6. Comparing the workaround for that (prior to CentOS 6 being supported again). I noticed that not all the Python pieces that the workaround noted were install on my box, `python-tools` and `python-pip`.

I reverted my VM and then added those to the yum install for git. Now Let’s Encrypt build correctly.

```
[root@nginxproxy letsencrypt]# ./letsencrypt-auto --help
Updating letsencrypt and virtual environment dependencies.......
Running with virtualenv: /root/.local/share/letsencrypt/bin/letsencrypt --help

  letsencrypt [SUBCOMMAND] [options] [-d domain] [-d domain] ...

The Let's Encrypt agent can obtain and install HTTPS/TLS/SSL certificates. By
default, it will attempt to use a webserver both for obtaining and installing
the cert. Major SUBCOMMANDS are:

  (default) run Obtain & install a cert in your current webserver
  certonly Obtain cert, but do not install it (aka "auth")
  install Install a previously obtained cert in a server
  revoke Revoke a previously obtained certificate
  rollback Rollback server configuration changes made during install
  config_changes Show changes made to server config during installation
  plugins Display information about installed plugins

Choice of server plugins for obtaining and installing cert:

  --apache Use the Apache plugin for authentication & installation
  --standalone Run a standalone webserver for authentication
  (nginx support is experimental, buggy, and not installed by default)
  --webroot Place files in a server's webroot folder for authentication

OR use different plugins to obtain (authenticate) the cert and then install it:

  --authenticator standalone --installer apache

More detailed help:

  -h, --help [topic] print this message, or detailed help on a topic;
						the available topics are:

   all, automation, paths, security, testing, or any of the subcommands or
   plugins (certonly, install, nginx, apache, standalone, webroot, etc)

[root@nginxproxy letsencrypt]#
```