Error report SSL.CertificateError versus hostname of box

I started getting the following error in my status report email at 3am. I am running MIAB 0.53a.

Not sure what triggered this unless the latest recommended system updates for the OS?
Thanks for any insight.

Traceback (most recent call last):
File “management/”, line 1035, in
run_and_output_changes(env, pool)
File “management/”, line 880, in run_and_output_changes
run_checks(True, env, cur, pool)
File “management/”, line 61, in run_checks
run_system_checks(rounded_values, env, output)
File “management/”, line 167, in run_system_checks
check_miab_version(env, output)
File “management/”, line 862, in check_miab_version
latest_ver = get_latest_miab_version()
File “management/”, line 847, in get_latest_miab_version
return’TAG=(.*)’, urlopen(“”, timeout=5).read()).group(1).decode(“utf8”)
File “/usr/lib/python3.6/urllib/”, line 223, in urlopen
return, data, timeout)
File “/usr/lib/python3.6/urllib/”, line 526, in open
response = self._open(req, data)
File “/usr/lib/python3.6/urllib/”, line 544, in _open
‘_open’, req)
File “/usr/lib/python3.6/urllib/”, line 504, in _call_chain
result = func(*args)
File “/usr/lib/python3.6/urllib/”, line 1368, in https_open
context=self._context, check_hostname=self._check_hostname)
File “/usr/lib/python3.6/urllib/”, line 1325, in do_open
File “/usr/lib/python3.6/http/”, line 1281, in request
self._send_request(method, url, body, headers, encode_chunked)
File “/usr/lib/python3.6/http/”, line 1327, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File “/usr/lib/python3.6/http/”, line 1276, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File “/usr/lib/python3.6/http/”, line 1042, in _send_output
File “/usr/lib/python3.6/http/”, line 980, in send
File “/usr/lib/python3.6/http/”, line 1442, in connect
File “/usr/lib/python3.6/”, line 407, in wrap_socket
_context=self, _session=session)
File “/usr/lib/python3.6/”, line 817, in init
File “/usr/lib/python3.6/”, line 1077, in do_handshake
File “/usr/lib/python3.6/”, line 694, in do_handshake
match_hostname(self.getpeercert(), self.server_hostname)
File “/usr/local/lib/mailinabox/env/lib/python3.6/site-packages/”, line 19, in patched_match_hostname
return real_match_hostname(cert, hostname)
File “/usr/lib/python3.6/”, line 331, in match_hostname
% (hostname, dnsnames[0]))
ssl.CertificateError: hostname ‘’ doesn’t match ‘

Why is anything in your configuration looking for

I have no idea.

This is the first time I have seen this error message in my console messaging ever. I have a standard install of 0.53a but did the latest OS updates that the system was telling me to install.

The output on 6/25 said:
System – Previously:

:heavy_multiplication_x: There are 1 software packages that can be updated.
linux-libc-dev (4.15.0-147.151)

System – Currently:

:heavy_multiplication_x: System updates have been installed and a reboot of the machine is required.

Output on 6/26 said:
System – Previously:

:heavy_multiplication_x: System updates have been installed and a reboot of the machine is required.

System – Currently:

✓ System software is up to date.

And the output of 6/27 was the messaging at the top.

Standard would be using MiaB exactly as it configures itself, including using MiaB as the name server.

Not sure I understand? :slight_smile: -
The only deviation I have is using external DNS but that has been the case for multiple versions of MIAB over the years for me. Just not sure where this is picking this up from and why now?

The best I can recommend is to track down why MiaB is doing anything with the domain This is something you may have done when you first set the box up or were doing some kind of testing?

My point is that I can’t know what your configuration is, and the term you had used conflicted with how it is typically used and the post information.

This is part of the status checks’s check for a new version of Mail-in-a-Box.

But there must be some local configuration issue because it appears that is resolving to (the error message suggests the HTTP connection is going to a server replying with a certificate for that hostname), which I assume is your box.

maybe it had trouble resolving the hostname with my external dns provider and somehow used the local box as the destination?

Not sure?