Beta sticky thread - add updating client info

With the beta sticky at, might want to also add official instructions for updating the letsencrypt client while perserving the /etc/letsencrypt/accounts :slight_smile:

1 Like

Edited: Got confirmation letsencrypt-auto doesn’t update itself, just dependencies.

1 Like

with latest letsencrypt-auto changes Using the webroot domain verification method how does one update the client for beta invitees ?

@bmw @jsha ?

is it just wiping the virtualenv out and reinstall ?

i.e. my virtualenv was at /root/tools/letsencrypt so for me on CentOS 6.7 with python2.7 ?

cd /root/tools
rm -rf /root/tools/letsencrypt
git clone
cd letsencrypt
sed -i "s|--python python2|--python python2.7|" letsencrypt-auto
./letsencrypt-auto --agree-dev-preview --server

Just rerunning it should update the client.

but @jcjones above confirmed that won’t auto update itself ?

If you take a look at the source code, you’ll see that the letsencrypt-auto script updates the dependencies and letsencrypt itself every time it’s run. (I actually think it’s a bit excessive. Wouldn’t it be enough to check once every hour or so?)
The letsencrypt-auto script itself isn’t updated but I don’t think that it’ll change much unless letsencrypt’s dependencies change.

Ups, then it’s probably just a git pull?.

Client dev to the rescue! Okay. letsencrypt-auto is a wrapper script around the letsencrypt program. Every time the script is run, it does the following:

  1. If your Python virtual environment is not present (stored at ~/.local/share/letsencrypt on most systems), it updates/installs necessary OS dependencies (dialog, python, etc.) and sets up the virtual environment.
  2. Updates the Python dependencies and letsencrypt itself. This happens on every run.

The letsencrypt-auto script itself is never updated. If you’d like to get a fresh version of this script, simply do a git pull. This should rarely be necessary, but if we make changes such as adding Python 2.6 support to letsencrypt-auto, you would need to do a git pull to get the changes.

1 Like

thanks @bmw so to cover our bases for updates a simple run within git cloned directory for

cd letsencrypt
git pull
./letsencrypt-auto --agree-dev-preview --server

should do it ?

might be one for official manual and beta invitee sticky thread :slight_smile:

Yep that’d do it! Our OS dependencies will never be updated, but that’s not likely to ever be a problem. Even if it is, keeping your system up to date would solve it.

1 Like

I put it in the beta sticky! Thanks!

1 Like

cheers @bmw @jcjones :+1: