I get a long pause … which eventually shows the following error:
FAILED: add-apt-repository -y ppa:certbot/certbot
Error: retrieving gpg key timed out.
So, the gpg key is not being added for the repository. I added that repositories key manually but still no luck. Not being a scripting person, I cannot make heads or tails of MiaB’s set up scripts to find where this would be happening to see if I can figure a work around … so … any ideas anyone?
If you just git clone the repository from master directly, it still installed v0.40 BUT you get all the commits and file changes from the latest commit in the master branch (Dubbed in most case as a development branch, which will not usually line up with a release tag file-wise btw.)
so what it downloaded, I used. My only concern is that to start the scripts installing, I ran that command again — I was worried that it would overwrite the file I had edited, but it did not. Is it possible that I have other worries to be concerned with now by doing it this way?
Things were rolling along fine until the install of the Mail-in-a-Box system management daemon … this still kept going but slowly until …
Installing Mail-in-a-Box system management daemon…
Already using interpreter /usr/bin/python3
Using base prefix ‘/usr’
New python executable in /usr/local/lib/mailinabox/env/bin/python3
Also creating executable in /usr/local/lib/mailinabox/env/bin/python
Installing setuptools, pkg_resources, pip, wheel…done.
Installing Munin (system monitoring)…
[FATAL ERROR] Lock already exists: /var/run/munin/munin-update.lock. Dying.
at /usr/share/perl5/Munin/Master/Update.pm line 128.
Stop munin services systemctl stop munin and then re-run setup using curl -s https://mailinabox.email/setup.sh | sudo -E bash, make sure /var/run/munin/munin-update.lock does not exist.