Ok, I ran the command line status checks. The thing that seems to start the cascade is that every time I try to run a sudo command I get the following message:
sudo: unable to resolve host box.mydomain.com: Resource temporarily unavailable
Now it occurs to me that I’ve had a similar issue before with hosting websites on the lan. The comcast business router can’t do a loopback(? Can’t remember if that’s what it is called). So if I want to see the live site being hosted by another computer on the lan, I have to either use a proxy to access the internet, or put an entry in my hosts file that maps the domain name to the lan-accessible IP.
So I just added an entry to the mailinabox’s /etc/hosts file the says:
127.0.0.1 box.mydomain.com
And rebooted the box.
Now when I run the system checks, that first error goes away, but I still get all of the others.
'System
SSH Login (ssh) is running but is not publicly accessible at
my.public.ip.address:22.
Public DNS (nsd4) is not running (port 53).
Incoming Mail (SMTP/postfix) is running but is not publicly accessible at
my.public.ip.address:25.
Outgoing Mail (SMTP 587/postfix) is running but is not publicly accessible
atmy.public.ip.address:587.
IMAPS (dovecot) is running but is not publicly accessible at
my.public.ip.address:993.
Mail Filters (Sieve/dovecot) is running but is not publicly accessible at
my.public.ip.address:4190.
HTTP Web (nginx) is running but is not publicly accessible at
my.public.ip.address:80.
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
HTTPS Web (nginx) is running but is not publicly accessible at
my.public.ip.address:443.
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: [warn] “ssl_stapling” ignored, issuer certificate not found for
certificate “/home/user-data/ssl/ssl_certificate.pem”
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
The SSH server on this machine permits password-based login. A more secure
way to log in is using a public key. Add your SSH public key to
$HOME/.ssh/authorized_keys, check that you can log in without a password,
set the option ‘PasswordAuthentication no’ in /etc/ssh/sshd_config, and then
restart the openssh via ‘sudo service ssh restart’.
✓ System software is up to date.
? You are running version Mail-in-a-Box v0.51. Mail-in-a-Box version check
disabled by privacy setting.
✓ System administrator address exists as a mail alias.
[administrator@box.mydomain.com ↦ admin@mydomain.com]
✓ The disk has 178.37 GB space remaining.
✓ System memory is 90% free.
Network
✓ Firewall is active.
✓ Outbound mail (SMTP port 25) is not blocked.
✓ IP address is not blacklisted by zen.spamhaus.org.
multiprocessing.pool.RemoteTraceback:
“”"
Traceback (most recent call last):
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 119, in worker
result = (True, func(*args, **kwds))
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 47, in starmapstar
return list(itertools.starmap(args[0], args[1]))
File “/home/bryceb/mailinabox/management/status_checks.py”, line 367, in run_domain_checks_on_domain
check_mail_domain(domain, env, output)
File “/home/bryceb/mailinabox/management/status_checks.py”, line 625, in check_mail_domain
mxhost = mx.split(’; ‘)[0].split(’ ')[1]
IndexError: list index out of range
“”"
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File “/home/bryceb/mailinabox/management/status_checks.py”, line 1027, in
run_checks(False, env, ConsoleOutput(), pool)
File “/home/bryceb/mailinabox/management/status_checks.py”, line 66, in run_checks
run_domain_checks(rounded_values, env, output, pool)
File “/home/bryceb/mailinabox/management/status_checks.py”, line 335, in run_domain_checks
ret = pool.starmap(run_domain_checks_on_domain, args, chunksize=1)
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 274, in starmap
return self._map_async(func, iterable, starmapstar, chunksize).get()
File “/usr/lib/python3.6/multiprocessing/pool.py”, line 644, in get
raise self._value
IndexError: list index out of range’
And of course I get the same general error when I visit the system checks page as I did before.
I suspect the errors that have my public IP address are related to the same loopback issue. I’m pretty sure that access from outside the lan is working, as I can SSH into the mailinabox server using the public IP address.