Can't Access my MiaB

Maintenance
1

Hello, all has been working fine until sometime today and now all I get is this when trying to access the mailbox or the admin:

Hmm. We’re having trouble finding that site.

We can’t connect to the server at box.skhilledmail.com.

I can login to ssh and have tried running “mailinabox” from the cli and get the following errors:

FAILED: apt-get -y -o Dpkg::Options::=–force-confdef -o Dpkg::Options::=–force-confnew install munin munin-node libcgi-fast-perl

E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

The error log shows the following:

2020/09/28 08:37:39 [error] 880#880: *6229 open() “/home/user-data/www/default/VWmC” failed (2: No such file or directory), client: 185.220.101.4, server: box.skhilledmail.com, request: “HEAD /VWmC HTTP/1.1”, host: “136.243.142.86”
2020/09/28 08:45:51 [crit] 880#880: *6232 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 51.81.83.138, server: 0.0.0.0:443
2020/09/28 08:45:51 [crit] 880#880: *6233 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 51.81.83.138, server: 0.0.0.0:443
2020/09/28 08:45:52 [crit] 880#880: *6234 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 51.81.83.138, server: 0.0.0.0:443
2020/09/28 11:25:47 [error] 880#880: connect() to [2a02:26f0:eb::214:bdb3]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bdb3]:80, certificate: “/home/user-data/ssl/box.skhilledmail.com-20201213-01b664f1.pem”
2020/09/28 11:25:48 [error] 880#880: connect() to [2a02:26f0:eb::214:bd5a]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bd5a]:80, certificate: “/home/user-data/ssl/skhilledmail.com-20201214-757b1269.pem”
2020/09/28 11:27:59 [crit] 880#880: *6492 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 164.68.112.178, server: 0.0.0.0:443
2020/09/28 12:33:08 [error] 880#880: connect() to [2a02:26f0:eb::214:bd5a]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bd5a]:80, certificate: “/home/user-data/ssl/skhilledmail.com-20201214-757b1269.pem”
2020/09/28 13:34:07 [error] 880#880: connect() to [2a02:26f0:eb::214:bd5a]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bd5a]:80, certificate: “/home/user-data/ssl/box.skhilledmail.com-20201213-01b664f1.pem”
2020/09/28 14:21:12 [error] 880#880: connect() to [2a02:26f0:eb::214:bdb3]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bdb3]:80, certificate: “/home/user-data/ssl/ssl_certificate.pem”
2020/09/28 14:55:57 [error] 880#880: *6707 open() “/home/user-data/www/default/GponForm/diag_Form” failed (2: No such file or directory), client: 207.154.242.83, server: box.skhilledmail.com, request: “POST /GponForm/diag_Form?style/ HTTP/1.1”, host: “192.168.0.1:443”
2020/09/28 16:03:59 [error] 880#880: connect() to [2a02:26f0:eb::214:bd5a]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bd5a]:80, certificate: “/home/user-data/ssl/ssl_certificate.pem”
2020/09/28 16:35:45 [error] 880#880: connect() to [2a02:26f0:eb::214:bdb3]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bdb3]:80, certificate: “/home/user-data/ssl/ssl_certificate.pem”
2020/09/28 19:41:56 [crit] 880#880: *6777 SSL_do_handshake() failed (SSL: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol) while SSL handshaking, client: 34.221.177.23, server: 0.0.0.0:443
2020/09/28 20:14:31 [error] 880#880: connect() to [2a02:26f0:eb::214:bdb3]:80 failed (101: Network is unreachable) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: [2a02:26f0:eb::214:bdb3]:80, certificate: “/home/user-data/ssl/ssl_certificate.pem”
2020/09/28 23:27:54 [error] 8238#8238: *17 open() “/home/user-data/www/default/sitemap.xml” failed (2: No such file or directory), client: 185.191.171.18, server: skhilledmail.com, request: “GET /sitemap.xml HTTP/1.1”, host: “skhilledmail.com”

Any help would be appreciated. Thanks.

2

You have far more problems that that… check:

“https://dnschecker.org/#SOA/box.skhilledmail.com”

https://internet.nl/mail/skhilledmail.com/419702/
https://internet.nl/site/box.skhilledmail.com/985766/

as to your “mailinabox” command, tried “sudo mailinabox”?
( 1. Re-run the setup by logging into your box (using the same ssh command that you used during setup) and running sudo mailinabox . Then check the System Status Checks page again.)

but first, I would try to re-run the upgrade once again:
curl -s https://mailinabox.email/setup.sh | sudo bash

3

Thanks for responding. As I’ve previously stated I have already ran the “mailinabox” command but it does nothing to solve it. I can still access my mail on my tablet via a mail app and just noticed there’s a new version. I ran the curl upgrade command and that seemed to fix it. I can now access the mail and admin.

However, after accessing the admin I see the following in the “box.skhilledmail.com” and the “skhilledmail.com” sections:

:heavy_multiplication_x: MTA-STS policy is missing: STSFetchResult.NONE

But otherwise, all else is ok and seems to work just fine. But it has still not resolved according to dnschecker.

EDIT: Upon further investigation, I noticed two TSL Certificates were not installed. They were previously installed and then somehow uninstalled. I installed them and that fixed the MTA-STS policy issue. That may have been why it wasn’t resolving. I guess it’s just a waiting game now. Nothing has been changed at my domain’s registar for the domain since I’ve initially installed MiaB last year.

4

See my post here: