Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on renewal on Ubuntu 16.04 #47

Closed
AjkP opened this issue Feb 4, 2018 · 4 comments
Closed

Error on renewal on Ubuntu 16.04 #47

AjkP opened this issue Feb 4, 2018 · 4 comments
Labels

Comments

@AjkP
Copy link

AjkP commented Feb 4, 2018

I am trying to run renewal manually, to see if it's actually running and unfortunately it's erring :/

When running:
sudo /opt/certbot/certbot-auto renew --quiet --no-self-upgrade

Im getting the following stacktrace:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 2363, in <module>
    main()
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 719, in main
    symlink=options.symlink)
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 988, in create_environment
    download=download,
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 918, in install_wheel
    call_subprocess(cmd, show_stdout=False, extra_env=env, stdin=SCRIPT)
  File "/usr/lib/python3/dist-packages/virtualenv.py", line 812, in call_subprocess
    % (cmd_desc, proc.returncode))
OSError: Command /opt/eff.org/certbot/venv/bin/python2.7 - setuptools pkg_resources pip wheel failed with error code 1

It seems to be related to certbot issue #2883.

@M-Devloo
Copy link

M-Devloo commented Oct 17, 2018

This problem is still active for Certbot. (17/10/2018)

Currently there is no straight solution for Ubuntu 16.04, only workarounds.

Package
When installing the 'latest' letsencrypt through apt-get will give you still Version 0.4.1-1 (Release March 2016) while the latest version is already v0.27.1 (time of writing of this post), it is mandatory to install it through source.

When running it from source, it will give you the above error. Meaning if you perform a fresh deploy, your certificates will never be renewed. (It will silently fail)

According to the Certbot site, it is suggested to install the Certbot PPA for Ubuntu 16.04

https://certbot.eff.org/lets-encrypt/ubuntuxenial-nginx (Nginx example)

The PPA could be one version behind (Testing on a baremetal Ubuntu 16.04 machine, it is version 0.26.1)

It should be possible to add this through the "apt_repository" ansible command

(https://docs.ansible.com/ansible/latest/modules/apt_repository_module.html)

A new task could install this PPA when Ubuntu 16.04 is detected as OS.
This could be reused for Ubuntu 18.04 as well. (Although it will fail on a clean machine, see my post below)

Source
As stated in the issue #2883, exporting LC_ALL & LC_CTYPE environment variable will fix the issue and allows you to continue forward. Although this means that you have to execute this for every fresh server.
It could also be added to a playbook task, but as stated, it is just a workaround.

@M-Devloo
Copy link

Package Ubuntu 18.04
For Ubuntu 18.04, i have also noticed that another bug is open when installing it from the default packages (certbot/certbot#6362). Meaning for a fresh install the command sudo add-apt-repository universe will have to be added, else the installation will fail due to 'unmet dependencies'

Although i haven't tried it installing from source for Ubuntu 18.04 yet.

@stale
Copy link

stale bot commented Mar 6, 2020

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label Mar 6, 2020
@stale
Copy link

stale bot commented Apr 5, 2020

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.

@stale stale bot closed this as completed Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants