"python setup.py egg_info" failed with error code 1 in /tmp/pip-build-NktBcn/ConfigArgParse

hi,
trying to install and getting the following, any ideas ? thanks

Updating letsencrypt and virtual environment dependencies…/root/.local/share/letsencrypt/lib/python2.6/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.6/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
Command “python setup.py egg_info” failed with error code 1 in /tmp/pip-build-NktBcn/ConfigArgParse

I believe this is likely due to being on a shared plan or something along those lines. I’m facing the same issue – can’t run sudo or su, so I can’t get letsencrypt-auto to run correctly.

I tried talking to my hosting company, and the best they could offer is to upgrade my plan from my current $2.50 or so per month to $20 per month. I’m not about to do this, as it’d be cheaper for me to just buy a new SSL cert every month. :stuck_out_tongue:

I’d like to know if there’s a work-around for this situation. I’ve read that authentication happens by running a process, etc. but I’m hoping that some sort of work-around is found for this. For an example, using the /.well-known folder like keybase.io uses to authenticate.

@web9: You’re using python 2.6 but the LE client needs at least python 2.7. The developers are already working on fixing that: https://github.com/letsencrypt/letsencrypt/pull/1257

@TacoBot: You might want to take a look at this topic. You can also run letsencrypt as a normal user with “-a manual”, it should then tell you what to do.

I have only just started to look at letsencrypt and have been using Fedora and had the same error. In my case I tried running ./letsencrypt-auto --verbose which revealed it stopped on a missing file during compilation.

I solved the error onmy system by installing the rpm-build package.

E.g. dnf install -y rpm-build

This allowed ./letsencrypt-auto to run without error, so it could be worth investigating if something similar may apply in your case.

–philip.

I had the same issue in Fedora 23.
The specifiy error was:

Collecting cffi>=1.1.0 (from cryptography>=0.7->letsencrypt)
  Using cached cffi-1.3.0.tar.gz 
    Complete output from command python setup.py egg_info:
    gcc: Fehler: /usr/lib/rpm/redhat/redhat-hardened-cc1: Datei oder Verzeichnis nicht gefunden
    gcc: Fehler: /usr/lib/rpm/redhat/redhat-hardened-cc1: Datei oder Verzeichnis nicht gefunden

The previous suggested installing of the package "rpmbuild" (dnf install -y rpm-build) solved the issue for me as well.
Thanks for sharing your solution!