I did follow the guide through on:
https://mailinabox.email/guide.html
when the installer comes to certain point it terminate itself.
Initializing system random number generator... Creating SSH key for backup…
any idea?
You are installing to a VPS (not a VM hosted at home/work, etc.) and it has a perfectly clean Ubuntu 18.04 LTS server edition OS installed, correct?
Yes, 18.04, to be clean its on LXD container. with ports open for inbount and outbound to a public static ip.
22 ALLOW Anywhere
53 ALLOW Anywhere
25/tcp ALLOW Anywhere
587 ALLOW Anywhere
993 ALLOW Anywhere
995 ALLOW Anywhere
4190/tcp ALLOW Anywhere
80 ALLOW Anywhere
443 ALLOW Anywhere
am going to check the setup.sh , look for
Initializing system random number generator... Creating SSH key for backup…
maybe i will be able to get an idea why it fails there.
i also made sure i have these packages.
apt-get install build-essential libssl-dev libffi-dev libxml2-dev libxslt1-dev zlib1g-dev
apt-get install python-pip
apt-get install python-all-dev python-setuptools python-wheel```
EDITE:
after following the guide, and had the problem mention, i tried to run installer manually.
```mailinabox/setup/start.sh
mailinabox/setup/start.sh: line 5: setup/functions.sh: No such file or directory
mailinabox/setup/start.sh: line 10: setup/preflight.sh: No such file or directory
mailinabox/setup/start.sh: line 34: setup/migrate.py: No such file or directory
ls -all mailinabox/setup/
total 180
drwxr-xr-x 2 root root 4096 Mar 12 18:36 .
drwxr-xr-x 8 root root 4096 Mar 12 17:58 ..
-rw-r--r-- 1 root root 2716 Mar 12 17:58 bootstrap.sh
-rwxr-xr-x 1 root root 3288 Mar 12 17:58 dkim.sh
-rwxr-xr-x 1 root root 4878 Mar 12 17:58 dns.sh
-rw-r--r-- 1 root root 1786 Mar 12 17:58 firstuser.sh
-rw-r--r-- 1 root root 7682 Mar 12 17:58 functions.sh
-rwxr-xr-x 1 root root 9478 Mar 12 17:58 mail-dovecot.sh
-rwxr-xr-x 1 root root 15038 Mar 12 17:58 mail-postfix.sh
-rwxr-xr-x 1 root root 6738 Mar 12 17:58 mail-users.sh
-rwxr-xr-x 1 root root 3982 Mar 12 17:58 management.sh
-rwxr-xr-x 1 root root 9989 Mar 12 17:58 migrate.py
-rwxr-xr-x 1 root root 3226 Mar 12 17:58 munin.sh
-rw-r--r-- 1 root root 2449 Mar 12 17:58 network-checks.sh
-rwxr-xr-x 1 root root 13906 Mar 12 17:58 nextcloud.sh
-rw-r--r-- 1 root root 2298 Mar 12 17:58 preflight.sh
-rw-r--r-- 1 root root 7802 Mar 12 17:58 questions.sh
-rwxr-xr-x 1 root root 6103 Mar 12 17:58 spamassassin.sh
-rwxr-xr-x 1 root root 3971 Mar 12 17:58 ssl.sh
-rwxr-xr-x 1 root root 6100 Mar 12 17:58 start.sh
-rwxr-xr-x 1 root root 14782 Mar 12 17:58 system.sh
-rwxr-xr-x 1 root root 7580 Mar 12 17:58 webmail.sh
-rwxr-xr-x 1 root root 5526 Mar 12 17:58 web.sh
-rwxr-xr-x 1 root root 3800 Mar 12 17:58 zpush.shIs your output similar:
sudo ls -alF /root/.ssh/
drwx------ 2 root root 4096 May 23 2019 ./
drwx------ 6 root root 4096 Jun 15 2019 ../
-rw------- 1 root root 2211 May 23 2019 authorized_keys
-rw------- 1 root root 1679 May 23 2019 id_rsa_miab
-rw-r--r-- 1 root root 412 May 23 2019 id_rsa_miab.publs: cannot access '/root/.ssh/miab': No such file or directory```Just wondering if you noticed my edit. That was a typo.
yup.
drwx------ 2 root root 4096 Mar 12 17:59 ./
drwx------ 7 root root 4096 Mar 12 18:38 ../
-rw------- 1 root root 1675 Mar 12 17:59 id_rsa_miab
-rw-r--r-- 1 root root 402 Mar 12 17:59 id_rsa_miab.pubOkay, so that step completes. It’s whatever after that which is failing. I half-wondered if there was some sort of permissions issue.
Hi @seven Right now, it is a bad time for me … but maybe later (say in 4-5 hours) you can come to the MiaB Slack where we can work through this in real time together?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.