# System status check

**URL:** <https://discourse.mailinabox.email/t/system-status-check/16046>\
**Category:** uncategorized\
**Created:** [October 28, 2025, 11:18am UTC](https://discourse.mailinabox.email/t/system-status-check/16046 "2025-10-28T11:18:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![chin\_kmtm](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/c/8c91f0/32.png) [@chin\_kmtm](https://discourse.mailinabox.email/u/chin_kmtm)\
**Post date:** [October 28, 2025, 11:18am UTC](https://discourse.mailinabox.email/t/system-status-check/16046/1 "2025-10-28T11:18:52Z")

</div>

I’m wondering why my mail in a box status page says,

Public DNS (nsd4) is not running (port 53).  
✖

Incoming Mail (SMTP/postfix) is running but is not publicly accessible at 123.231.14.105:25.  
✖

Outgoing Mail (SMTP 465/postfix) is running but is not publicly accessible at 123.231.14.105:465.  
✖

Outgoing Mail (SMTP 587/postfix) is running but is not publicly accessible at 123.231.14.105:587.  
✖

IMAPS (dovecot) is running but is not publicly accessible at 123.231.14.105:993.  
✖

Mail Filters (Sieve/dovecot) is running but is not publicly accessible at 123.231.14.105:4190.  
✖

HTTP Web (nginx) is running but is not publicly accessible at 123.231.14.105:80.  
show more  
✖

HTTPS Web (nginx) is running but is not publicly accessible at 123.231.14.105:443.

Reverse DNS is also set to [mail2.lanka4us.com](http://mail2.lanka4us.com)

I have checked these ports using [dnschecker.org](http://dnschecker.org) port scanner. it shows them as OPEN, but mail in a box says they cannot be publicly accessible.

I am able to send and receive mails from internet.

Could someone help me to identify the issue.

---

<div class="post-metadata">

**Author:** ![KiekerJan](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/kiekerjan/32/2339_2.png) [@KiekerJan](https://discourse.mailinabox.email/u/KiekerJan)\
**Post date:** [October 28, 2025, 6:46pm UTC](https://discourse.mailinabox.email/t/system-status-check/16046/2 "2025-10-28T18:46:14Z")

</div>

Can you provide more information?

- Was this all ok before?
- How is Mailinabox deployed? On a VPS? With which provider?
- Is there a firewall involved somewhere?

---

<div class="post-metadata">

**Author:** ![chin\_kmtm](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/c/8c91f0/32.png) [@chin\_kmtm](https://discourse.mailinabox.email/u/chin_kmtm)\
**Post date:** [October 29, 2025, 12:13am UTC](https://discourse.mailinabox.email/t/system-status-check/16046/3 "2025-10-29T00:13:46Z")

</div>

Hi, thanks for replying. Background is as follows.

1. This runs in a virtual machine on my own.
2. Only the isp’s router with the firewall.
3. Runs on Ubuntu 22.04 server with a fresh install. No other services runs.
4. This is first install on this isp network.All ports are open/directed to this machine.
5. Very recently installed and from the very beginning it shows errors.
6. Tried formating and reinstalling several times.but errors same.

Thanks

---

<div class="post-metadata">

**Author:** ![KiekerJan](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/kiekerjan/32/2339_2.png) [@KiekerJan](https://discourse.mailinabox.email/u/KiekerJan)\
**Post date:** [October 30, 2025, 7:17pm UTC](https://discourse.mailinabox.email/t/system-status-check/16046/4 "2025-10-30T19:17:28Z")

</div>

These checks try to access the mentioned services on the public ip address. Apparently something in your setup causes the system to not be able to reach itself through its public ip address. I guess something network related.  
Since these services are actually publically reachable, so I don’t think there’s an actual problem. The Mailinabox code that does the checks just isn’t build for your current situation, which is a bit different than expected.

You might want to look into the firewall/router and/or virtual machine and see how it handles access to your own ip address.

---

<div class="post-metadata">

**Author:** ![netmaster48](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/n/82dd89/32.png) [@netmaster48](https://discourse.mailinabox.email/u/netmaster48)\
**Post date:** [October 31, 2025, 7:46am UTC](https://discourse.mailinabox.email/t/system-status-check/16046/5 "2025-10-31T07:46:59Z")

</div>

If MIAB in the private network need to reach it’s own services via public IP address, then “hairpin nat” is required in the router.  
[https://en.wikipedia.org/wiki/Network\_address\_translation#NAT\_hairpinning](https://en.wikipedia.org/wiki/Network_address_translation#NAT_hairpinning)

---

<div class="post-metadata">

**Author:** ![andrew](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/andrew/32/1449_2.png) [@andrew](https://discourse.mailinabox.email/u/andrew)\
**Post date:** [October 31, 2025, 11:14pm UTC](https://discourse.mailinabox.email/t/system-status-check/16046/6 "2025-10-31T23:14:43Z")

</div>

And then, after you’ve got it working, make sure your router’s external address and **internal address** are on these config lines. The config is built by the install process, but it doesn’t know about hairpin routing and doesn’t add network internal addresses.

This one is needed so fail2ban doesn’t block legitimate traffic from within your network (eg you ssh’ing into the server).

> **/etc/fail2ban/jail.d/mailinabox.conf**  
> ignoreip = 127.0.0.1/8 …

And add this one if you are sending mail (eg status reports) from within your network to your MIAB server.

> **/etc/postfix/main.cf**  
> mynetworks = 127.0.0.0/8 …

---

<div class="post-metadata">

**Author:** ![chin\_kmtm](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/c/8c91f0/32.png) [@chin\_kmtm](https://discourse.mailinabox.email/u/chin_kmtm)\
**Post date:** [November 1, 2025, 4:08am UTC](https://discourse.mailinabox.email/t/system-status-check/16046/7 "2025-11-01T04:08:56Z")

</div>

Appreciate the support extended to me. I have reached to ISP for hairpining support on my router configuration.

When they confirmed I’ll follow everyone’s suggestions and will update here accordingly, So it will help others who faced such scenarios.

---

<div class="post-metadata">

**Author:** ![chin\_kmtm](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/c/8c91f0/32.png) [@chin\_kmtm](https://discourse.mailinabox.email/u/chin_kmtm)\
**Post date:** [November 13, 2025, 4:27am UTC](https://discourse.mailinabox.email/t/system-status-check/16046/8 "2025-11-13T04:27:03Z")

</div>

Dear All,

Thank you all for your valuable comments, Which I have followed. Some help me to understand lot.

As far as, I know this is an issue arising from the ISP end. Even I reached to them, there is no response from them.

So, I change the ISP, installed the system. Now all are working as expected.  
Thank you all for your kindness to help others. Really appreciate it.
