Certbot-auto certificates fails while installing phyton packages with THESE PACKAGES DO NOT MATCH THE HASHES

I am also affected by this problem

Bootstrapping dependencies for Debian-based OSes... (you can skip this with --no-bootstrap)
Hit:1 http://archive.raspberrypi.org/debian stretch InRelease
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
augeas-lenses is already the newest version (1.8.0-1+deb9u1).
ca-certificates is already the newest version (20161130+nmu1+deb9u1).
gcc is already the newest version (4:6.3.0-4).
libaugeas0 is already the newest version (1.8.0-1+deb9u1).
libffi-dev is already the newest version (3.2.1-6).
libssl-dev is already the newest version (1.1.0j-1~deb9u1).
openssl is already the newest version (1.1.0j-1~deb9u1).
python is already the newest version (2.7.13-2).
python-dev is already the newest version (2.7.13-2).
python-virtualenv is already the newest version (15.1.0+ds-1).
virtualenv is already the newest version (15.1.0+ds-1).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Creating virtual environment...
Installing Python packages...
Had a problem while installing Python packages.

pip prints the following errors:
=====================================================
Collecting ConfigArgParse==0.14.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 7))
  Downloading https://files.pythonhosted.org/packages/55/ea/f0ade52790bcd687127a302b26c1663bf2e0f23210d5281dbfcd1dfcda28/ConfigArgParse-0.14.0.tar.gz
Collecting asn1crypto==0.24.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 9))
  Downloading https://files.pythonhosted.org/packages/ea/cd/35485615f45f30a510576f1a56d1e0a7ad7bd8ab5ed7cdc600ef7cd06222/asn1crypto-0.24.0-py2.py3-none-any.whl (101kB)
Collecting certifi==2019.3.9 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 12))
  Downloading https://files.pythonhosted.org/packages/60/75/f692a584e85b7eaba0e03827b3d51f45f571c2e793dd731e598828d380aa/certifi-2019.3.9-py2.py3-none-any.whl (158kB)
Collecting cffi==1.12.2 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 15))
  Downloading https://files.pythonhosted.org/packages/64/7c/27367b38e6cc3e1f49f193deb761fe75cda9f95da37b67b422e62281fcac/cffi-1.12.2.tar.gz (453kB)
Collecting chardet==3.0.4 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 44))
  Downloading https://files.pythonhosted.org/packages/bc/a9/01ffebfb562e4274b6487b4bb1ddec7ca55ec7510b22e4c51f14098443b8/chardet-3.0.4-py2.py3-none-any.whl (133kB)
Collecting configobj==5.0.6 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 47))
  Downloading https://files.pythonhosted.org/packages/64/61/079eb60459c44929e684fa7d9e2fdca403f67d64dd9dbac27296be2e0fab/configobj-5.0.6.tar.gz
Collecting cryptography==2.6.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 49))
  Downloading https://files.pythonhosted.org/packages/07/ca/bc827c5e55918ad223d59d299fff92f3563476c3b00d0a9157d9c0217449/cryptography-2.6.1.tar.gz (491kB)
Collecting enum34==1.1.6 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 71))
  Downloading https://files.pythonhosted.org/packages/c5/db/e56e6b4bbac7c4a06de1c50de6fe1ef3810018ae11732a50f15f62c7d050/enum34-1.1.6-py2-none-any.whl
Collecting funcsigs==1.0.2 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 76))
  Downloading https://files.pythonhosted.org/packages/69/cb/f5be453359271714c01b9bd06126eaf2e368f1fddfff30818754b5ac2328/funcsigs-1.0.2-py2.py3-none-any.whl
Collecting future==0.17.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 79))
  Downloading https://files.pythonhosted.org/packages/90/52/e20466b85000a181e1e144fd8305caf2cf475e2f9674e797b222f8105f5f/future-0.17.1.tar.gz (829kB)
Collecting idna==2.8 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 81))
  Downloading https://files.pythonhosted.org/packages/14/2c/cd551d81dbe15200be1cf41cd03869a46fe7226e7450af7a6545bfc474c9/idna-2.8-py2.py3-none-any.whl (58kB)
Collecting ipaddress==1.0.22 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 84))
  Downloading https://files.pythonhosted.org/packages/fc/d0/7fc3a811e011d4b388be48a0e381db8d990042df54aa4ef4599a31d39853/ipaddress-1.0.22-py2.py3-none-any.whl
Collecting josepy==1.1.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 87))
  Downloading https://files.pythonhosted.org/packages/23/46/30ac29742b03be92e05d1fd9048df6f0902bb0b3b042a7ea76a2b3c30f7e/josepy-1.1.0-py2.py3-none-any.whl (53kB)
Collecting mock==1.3.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 90))
  Downloading https://files.pythonhosted.org/packages/b2/50/664a70b87408bb6c14c1af2337efa64eb8d1af80c933531758b8fb41ec25/mock-1.3.0-py2.py3-none-any.whl (56kB)
Collecting parsedatetime==2.4 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 93))
  Downloading https://files.pythonhosted.org/packages/1d/48/ac8d4c6239437592852e951bcb9438dc585f80c29777c391aef69c67dc79/parsedatetime-2.4-py2-none-any.whl (40kB)
Collecting pbr==5.1.3 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 96))
  Downloading https://files.pythonhosted.org/packages/14/09/12fe9a14237a6b7e0ba3a8d6fcf254bf4b10ec56a0185f73d651145e9222/pbr-5.1.3-py2.py3-none-any.whl (107kB)
Collecting pyOpenSSL==19.0.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 99))
  Downloading https://files.pythonhosted.org/packages/01/c8/ceb170d81bd3941cbeb9940fc6cc2ef2ca4288d0ca8929ea4db5905d904d/pyOpenSSL-19.0.0-py2.py3-none-any.whl (53kB)
Collecting pyRFC3339==1.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 102))
  Downloading https://files.pythonhosted.org/packages/c1/7a/725f5c16756ec6211b1e7eeac09f469084595513917ea069bc023c40a5e2/pyRFC3339-1.1-py2.py3-none-any.whl
Collecting pycparser==2.19 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 105))
  Downloading https://www.piwheels.org/simple/pycparser/pycparser-2.19-py2.py3-none-any.whl (111kB)
Collecting pyparsing==2.3.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 107))
  Downloading https://files.pythonhosted.org/packages/de/0a/001be530836743d8be6c2d85069f46fecf84ac6c18c7f5fb8125ee11d854/pyparsing-2.3.1-py2.py3-none-any.whl (61kB)
Collecting python-augeas==0.5.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 110))
  Downloading https://files.pythonhosted.org/packages/41/e6/4b6740cb3e31b82252099994cea751c648b846aa7874343c31d68c2215be/python-augeas-0.5.0.tar.gz (90kB)
Collecting pytz==2018.9 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 112))
  Downloading https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7cd85cc7b9a75a490570d5a30c57622d34/pytz-2018.9-py2.py3-none-any.whl (510kB)
Collecting requests==2.21.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 115))
  Downloading https://files.pythonhosted.org/packages/7d/e3/20f3d364d6c8e5d2353c72a67778eb189176f08e873c9900e10c0287b84b/requests-2.21.0-py2.py3-none-any.whl (57kB)
Collecting requests-toolbelt==0.9.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 118))
  Downloading https://files.pythonhosted.org/packages/60/ef/7681134338fc097acef8d9b2f8abe0458e4d87559c689a8c306d0957ece5/requests_toolbelt-0.9.1-py2.py3-none-any.whl (54kB)
Collecting six==1.12.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 121))
  Downloading https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl
Collecting urllib3==1.24.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 124))
  Downloading https://files.pythonhosted.org/packages/62/00/ee1d7de624db8ba7090d1226aebefab96a2c71cd5cfa7629d6ad3f61b79e/urllib3-1.24.1-py2.py3-none-any.whl (118kB)
Collecting zope.component==4.5 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 127))
  Downloading https://files.pythonhosted.org/packages/97/e2/c785df1171f277ea93cc16bdcc112cb3ddfde1aeefbc401d46c49727f472/zope.component-4.5-py2.py3-none-any.whl (70kB)
Collecting zope.deferredimport==4.3 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 130))
  Downloading https://files.pythonhosted.org/packages/62/d2/e03e4b0c9103817e19d1ea577c1f7fb9b67e4c0397ca5127d377e1eafe0c/zope.deferredimport-4.3-py2.py3-none-any.whl
Collecting zope.deprecation==4.4.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 133))
  Downloading https://files.pythonhosted.org/packages/f9/26/b935bbf9d27e898b87d80e7873a0200cebf239253d0afe7a59f82fe90fff/zope.deprecation-4.4.0-py2.py3-none-any.whl
Collecting zope.event==4.4 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 136))
  Downloading https://files.pythonhosted.org/packages/c5/96/361edb421a077a4c208b4a5c212737d78ae03ce67fbbcd01621c49f332d1/zope.event-4.4-py2.py3-none-any.whl
Collecting zope.hookable==4.2.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 139))
  Downloading https://files.pythonhosted.org/packages/41/b5/378175b959565de41f45c775cdfbf8897aaeaf29a258b94e40bd2661ce46/zope.hookable-4.2.0.tar.gz
Collecting zope.interface==4.6.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 150))
  Downloading https://files.pythonhosted.org/packages/4e/d0/c9d16bd5b38de44a20c6dc5d5ed80a49626fafcb3db9f9efdc2a19026db6/zope.interface-4.6.0.tar.gz (150kB)
Collecting zope.proxy==4.3.1 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 180))
  Downloading https://files.pythonhosted.org/packages/7c/f5/e9ed65cdf8c93d24d7512ef89e21b241bc9ae75d90bc8608cc142f4c26f9/zope.proxy-4.3.1.tar.gz (43kB)
Collecting letsencrypt==0.7.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 200))
  Downloading https://files.pythonhosted.org/packages/fd/21/0c6f33829fadec8aca0c1ebb4d6f8101c05899356a58d1b2e506cb77cf18/letsencrypt-0.7.0-py2-none-any.whl
Collecting certbot==0.33.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 204))
  Downloading https://files.pythonhosted.org/packages/d1/0e/f236bc44f4c00058708cc7f17c48e0e7d5854d2b769dd15f87540aa48b8f/certbot-0.33.0-py2.py3-none-any.whl (324kB)
Collecting acme==0.33.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 207))
  Downloading https://files.pythonhosted.org/packages/1c/fc/ba9a7dbc5535cd9ffdf5c4032b365ee3cc31be692529c832112120de1ce3/acme-0.33.0-py2.py3-none-any.whl (86kB)
Collecting certbot-apache==0.33.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 210))
  Downloading https://files.pythonhosted.org/packages/85/40/41af45945649321b4d9dabe91abad617e59b12ec617930ecfcac1e1d6e2c/certbot_apache-0.33.0-py2.py3-none-any.whl (249kB)
Collecting certbot-nginx==0.33.0 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 213))
  Downloading https://files.pythonhosted.org/packages/f2/0c/2816571232606b7a3364b2738b01c94898861e6c3ba37e63b04a0468a524/certbot_nginx-0.33.0-py2.py3-none-any.whl (86kB)
Requirement already satisfied: setuptools>=1.0 in /opt/eff.org/certbot/venv/lib/python2.7/site-packages (from josepy==1.1.0->-r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 87))
THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    pycparser==2.19 from https://www.piwheels.org/simple/pycparser/pycparser-2.19-py2.py3-none-any.whl#sha256=344870c533812cb119c5475b5aed033ec546118711338ff9b2b78e67098d64e7 (from -r /tmp/tmp.u2T6vbpT4R/letsencrypt-auto-requirements.txt (line 105)):
        Expected sha256 a988718abfad80b6b157acce7bf130a30876d27603738ac39f140993246b25b3
             Got        344870c533812cb119c5475b5aed033ec546118711338ff9b2b78e67098d64e7
=====================================================

Certbot has problem setting up the virtual environment.

We were not be able to guess the right solution from your pip
output.

Consult https://certbot.eff.org/docs/install.html#problems-with-python-virtual-environment
for possible solutions.
You may also find some support resources at https://certbot.eff.org/support/

Edit: After changing the sha256 in certbot-auto and calling it with certbot-auto renew --no-self-upgrade it ran trough.

I don’t have access to a Raspbian system at the moment. Can someone hitting this problem download https://raw.githubusercontent.com/certbot/certbot/v0.32.0/certbot-auto, make the script executable, and run it with the flags --no-self-upgrade --verbose and provide the full output?

EDIT: Changed GitHub link to raw script.

EDIT 2: You can skip this check because on closer inspection, it won’t verify what I want.

The problem here is Raspbian has configured pip to use third party mirrors which certbot-auto doesn’t trust. I’m not sure where Raspbian has done this, but configuring pip to not use piwheels.org would solve this problem.

With all that said though, OS packages are still the preferred way to install Certbot on this platform.

While I’m curious to hear the outcome of that, you should only be hitting this problem if you’re on Raspbian Stretch or greater and we recommend people on those systems use the packages provided by your OS. See https://certbot.eff.org/lets-encrypt/debianstretch-other.

2 Likes

Thanks for your answer.
Just checking my system and observed it was configured to use pipwheels instead of pip. After removing the pip.conf file the renewal of the certificate was running smoothly.

2 Likes

Same issue at my side:

Requirement already satisfied: setuptools>=1.0 in /opt/eff.org/certbot/venv/lib/python2.7/site-packages (from josepy==1.1.0->-r /tmp/tmp.HuTppwRXXz/letsencrypt-auto-requirements.txt (line 87))
THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them.
    pycparser==2.19 from https://www.piwheels.org/simple/pycparser/pycparser-2.19-py2.py3-none-any.whl#sha256=344870c533812cb119c5475b5aed033ec546118711338ff9b2b78e67098d64e7 (from -r /tmp/tmp.HuTppwRXXz/letsencrypt-auto-requirements.txt (line 105)):
        Expected sha256 a988718abfad80b6b157acce7bf130a30876d27603738ac39f140993246b25b3
             Got        344870c533812cb119c5475b5aed033ec546118711338ff9b2b78e67098d64e7
=====================================================

Certbot has problem setting up the virtual environment.

We were not be able to guess the right solution from your pip 
output.

Consult https://certbot.eff.org/docs/install.html#problems-with-python-virtual-environment
for possible solutions.
You may also find some support resources at https://certbot.eff.org/support/ .`

I found my pip config:

root@moon:~# cat /etc/pip.conf

[global]

extra-index-url=https://www.piwheels.org/simple

I deleted the /etc/pip.conf file and certboot managed to work again

Thanks

8 Likes

Thanks, this also fixed my problem.

Just to clarify this point, while modifying /etc/pip.conf should work, there are a number of benefits to using our recommended installation method for Stretch instead of continuing to use certbot-auto which I wanted to explain for people here.

When you run certbot-auto on Raspbian, it has to compile packages from source (on every update) because precompiled packages are not available for some of our dependencies on ARM systems. This process is slow and can completely fail on smaller systems with less memory. Additionally, certbot-auto installations take significantly more disk space than installations from OS packages because for stability, certbot-auto pulls in exact versions of most of our dependencies rather than reusing the versions already installed on your OS.

Installing Certbot through your package manager avoids both of these problems and come with the additional benefits of having automatic renewal preconfigured to make sure your certificates stay valid and having DNS plugins available for popular DNS providers.

3 Likes

Hello bmw,

thank you for your support. I tried the recommended installation method, but I found out that python3-certbot-dns-ovh is not available on stretch.

What is your recommendation to get a wildcard-cert on raspian with ovh as dns-provider?

For now, the best solution to run Certbot in Docker.

Thx, this Workaround was the solution also for me.

HI Berndy,
Sorry, I’m a beginner but how did you change the sha256 in certbot-auto ?

This solution works fine for me.
Thank you.

Marc

@bmw Thanks for the link on installing for Stretch. In my case, I was trying to get certbot running on a fresh install of Hassbian, so I was using a tutorial on the Home Automation site and got led astray, haha.

I did have to jump through a variety of hoops (adding Stretch backports, and then muck around with missing Debian public keys, which lead to adding some missing keyring dependencies, yadda, yadda, yadda. But I was finally able to get things going.

So if for any future Hassbian (1.5.1 based on Stretch 9.9) users that arrive here, follow the instructions in this post

2 Likes

When I went for the /etc/pip.conf amendment I didn’t have too much time to solve that issue even if I didn’t like very much to change the pip configuration.
As you recommend the clean solution would be to install the certbot through the package manager
apt-get install certbot and then to renew the certificate by using new certbot in same way like:

# certbot renew --dry-run --standalone
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/xxxxxxx.duckdns.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Attempting to parse the version 0.33.1 renewal configuration file found at /etc/letsencrypt/renewal/xxxxxx.duckdns.org.conf with version 0.28.0 of Certbot. This might not work.
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator standalone, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for xxxxxx.duckdns.org
Waiting for verification...
Cleaning up challenges

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/xxxxxxx.duckdns.org/fullchain.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
** DRY RUN: simulating 'certbot renew' close to cert expiry
**          (The test certificates below have not been saved.)

Congratulations, all renewals succeeded. The following certs have been renewed:
  /etc/letsencrypt/live/xxxxxx.duckdns.org/fullchain.pem (success)
** DRY RUN: simulating 'certbot renew' close to cert expiry
**          (The test certificates above have not been saved.)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

If suppose that the warning:
Attempting to parse the version 0.33.1 renewal configuration file found at /etc/letsencrypt/renewal/xxxxxx.duckdns.org.conf with version 0.28.0 of Certbot. This might not work.
is due to previuos use of certbot-auto.

1 Like

That’s right. In the past we’ve had some issues where people downgrading Certbot like this caused problems so that message is just there as a warning. I don’t expect there to be any issues for people who downgrade from certbot-auto to the version in stretch-backports. It isn’t that much older.

I’d encourage anyone who does this though to test their new installation with sudo certbot renew --dry-run to make sure things are working properly.

1 Like

I too followed this post and it worked.

I am running Hassbian with Stretch.

All I did was run: sudo apt-get install certbot then after the update, ran sudo cerbot renew rebooted my RPi then all was good again.

Thanks again!

1 Like

I had the same problem, but removing the /etc/pip.conf was partially working, now I got the following:

Requirement already satisfied: setuptools>=1.0 in /opt/eff.org/certbot/venv/lib/python2.7/site-packages (from josepy==1.1.0->-r /tmp/tmp.hbtHfnPczP/letsencrypt-auto-requirements.txt (line 87))
Collecting pyparsing>=1.5.5 (from certbot-nginx==0.34.2->-r /tmp/tmp.hbtHfnPczP/letsencrypt-auto-requirements.txt (line 213))
In --require-hashes mode, all requirements must have their versions pinned with ==. These do not:
pyparsing>=1.5.5 from https://files.pythonhosted.org/packages/dd/d9/3ec19e966301a6e25769976999bd7bbe552016f0d32b577dc9d63d2e0c49/pyparsing-2.4.0-py2.py3-none-any.whl#sha256=9b6323ef4ab914af344ba97510e966d64ba91055d6b9afa6b30799340e89cc03 (from certbot-nginx==0.34.2->-r /tmp/tmp.hbtHfnPczP/letsencrypt-auto-requirements.txt (line 213))

This is really frustrating, I can’t find a solution searching around.
I’m using a clean sketch of Raspian running on Pi Zero.
Thanks.

@andreimestereaga, the best solution is to use the packages from Debian as described above.

Hi,

Just like to take issue with the disk space argument. It’s not an issue these days (“significant” is a meaningless term). Also, time taken trying to track down and fix this is way longer than time taken to run upgrade.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.