I have tried very hard to avoid posting but I just don’t seem to be getting anywhere with installing MIAB on my new Ubuntu machine (from System76).
I am trying to set this up at my house where I have business class internet (fixed IPs) from Comcast. I have a pfSense firewall/router after the Comcast modem and before my System76 machine. pfSense seems to be set up correctly (it works as intended for the other servers at my house); that is, ports 80, 443, 25, 587, 143, 110, 465, 995, 993 for 126.96.36.199 are all port forwarded to 10.10.10.76.
:~$ sudo mailinabox
Primary Hostname: mail76.pminj.org
Public IP Address: 188.8.131.52
Public IPv6 Address: 2603:3023:30e:a7f0:9877:b43e:58a9:7c47
Private IP Address: 10.10.10.76
Mail-in-a-Box Version: v0.43
Updating system packages…
Installing system packages…
Initializing system random number generator…
And then it stops. Back to the prompt.
Not sure where that IPv6 address is coming from. The network settings say 2603:3023:30e:a7f0:4a9:c3ae:e44f:bc1 instead. WhatIsMyIP? says it is 2603:3023:30e:a7f0:9877:b43e:58a9:7c47 though.
I am using external DNS and I believe it is correct.
I believe I have UFW set up correctly.
:~$ sudo ufw status numbered
To Action From
-- ------ ----
[ 1] 443/tcp ALLOW IN Anywhere
[ 2] Anywhere ALLOW IN 10.10.10.10 [my personal machine on same network ]
[ 3] 53 ALLOW IN Anywhere
[ 4] 25/tcp ALLOW IN Anywhere
[ 5] 587 ALLOW IN Anywhere
[ 6] 993 ALLOW IN Anywhere
[ 7] 995 ALLOW IN Anywhere
[ 8] 4190/tcp ALLOW IN Anywhere
[ 9] 80 ALLOW IN Anywhere
 Anywhere ALLOW IN 184.108.40.206 [IP of my pfSense]
 Anywhere ALLOW IN nn.nn.nn.nn/28 [machines in my rack at datacenter]
 22/tcp ALLOW IN Anywhere
 443/tcp (v6) ALLOW IN Anywhere (v6)
 53 (v6) ALLOW IN Anywhere (v6)
 25/tcp (v6) ALLOW IN Anywhere (v6)
 587 (v6) ALLOW IN Anywhere (v6)
 993 (v6) ALLOW IN Anywhere (v6)
 995 (v6) ALLOW IN Anywhere (v6)
 4190/tcp (v6) ALLOW IN Anywhere (v6)
 80 (v6) ALLOW IN Anywhere (v6)
 22/tcp (v6) ALLOW IN Anywhere (v6)
canyouseeme port checker says ports 80 and 25 are closed.
Doesn’t make sense to me, but I accept it. Can’t determine where the issue is though.
pfSense can see 220.127.116.11 from wan side and lan side and lan can see 10.10.10.76 as well.
I can’t show the status page because I can’t get to it.
And why is my network a problem?
The two other servers in my house aren’t having issues; I have business class internet. The 19 servers behind my pfSense firewall in my datacenter rack don’t have any issues. None of them are Ubuntu or MiaB; so I suppose you are right cuz it seems to be one of those two reasons.
It seems to me that MiaB is not completing its install process. Something is causing it to end early.
I will try again but I will add port 53 first.
This is on a Meerkat machine from System76 running Ubuntu 18.04 LTS.
:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
UFW did not get enabled by the MiaB installer. All the settings that I noted before were done by me.
:/home/user-data$ ls -l
-rw-r–r-- 1 user-data user-data 8980 Apr 16 2018 examples.desktop
-rw-r–r-- 1 user-data user-data 3 Nov 2 02:33 mailinabox.version
:/home/user-data$ sudo nano mailinabox.version
The November 2nd date tells you how long I have been trying to avoid bothering this list!
You didn’t answer my question though … which ISO did you install the OS from? or was this pre-installed? I have no idea what a ‘Meerkat’ machine is, so you need to answer what I ask. Is this a desktop, laptop, or rack server?
Go to the home directory of the user that you installed MaiB as and then cd mailinabox cd management ./status_checks.py
That really matters? I had MiaB mostly working on the machine during the summer (mail worked in my email client, web mail worked but only with IPv4). I started over due to all my efforts for bringing IPv6 into my network caused a bunch of issues; now they seem to be all worked out.
@Keith_Rettig I don’t think the desktop/server different should really make a difference. It looks like the Mail-in-a-Box setup isn’t finishing. If it’s ending after “Initializing system random number generator…” then it hasn’t done almost any of the setup yet. Something at that stage is failing. Your best bet is to try to figure out which command is failing by looking through the setup source code and seeing what’s after that message. Usually hard failures signal easy problems.
Drop to root then check. But that may not be an accurate check - if it is there. If it is not, you know that you failed at line 221 or 227
echo Initializing system random number generator...
dd if=/dev/random of=/dev/urandom bs=1 count=32 2> /dev/null
# This is supposedly sufficient. But because we're not sure if hardware entropy
# is really any good on virtualized systems, we'll also seed from Ubuntu's
# pollinate servers:
pollinate -q -r
Also, you are about at max replies for the first day in this forum. So be advised that you may not be able to reply any more today soon.