2019-06-30 16:55:28,132 fail2ban.ipdns [32457]: WARNING Unable to find a corresponding IP address for box.janning.tech: [Errno -3] Temporary failure in name resolution
but stopping the service does not stop the status page errors.
How about externally??? How long has it been since you have set DNS and is propagation complete to you? Whilst this may have been an issue at the time you posted, it appears now that your DNS is well propagated.
Have you tried SSL issuance? Did it fail?
And have you rebooted since installation was complete?
Have you check your firewall if it is not blocking any of these ports? sudo ufw status Will show you firewall status. You could share the output and we see.
hmm. Fresh install doesn´t work. maybe my type of network setup is not working for mailinabox.
the “box” has an internal ip address: 192.168.2.87 which is routed through an opnsense firewall. opnsense has some portforwarding from WAN IP (Virtual IP) to the neccessary ports: 25,53,80,143,etc.
maybe this type of structure is not supported? do i need to configure the “box” with the public ip address?
Upgrading to Nextcloud version 14.0.6
sudo: unable to resolve host box.janning.tech: Resource temporarily unavailable
creating sqlite db
sudo: unable to resolve host box.janning.tech: Resource temporarily unavailable
Nextcloud is already latest version
Installing Z-Push (Exchange/ActiveSync server)...
Installing Mail-in-a-Box system management daemon...
Already using interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in /usr/local/lib/mailinabox/env/bin/python3
Also creating executable in /usr/local/lib/mailinabox/env/bin/python
Installing setuptools, pkg_resources, pip, wheel...done.
Installing Munin (system monitoring)...
sudo: unable to resolve host box.janning.tech: Resource temporarily unavailable
updated DNS: box.janning.tech
You’ve got a unique setup as far as the typical audience of MiaB is concerned, so sadly you are probably going to be on your own.
The big hangup seems to be (from everything you have posted so far) with DNS port 53. I am not familiar with networking enough to give you any valid advice. But I would focus on port 53 … you may need to tweak your /etc/resolv.conf due to your network setup … of course in Ubuntu 18, it is much more convoluted than editing that file. Good luck!
I experienced similar issues with MiaB behind pfSense, and received no help on this forum. The project is currently very narrowly focused (in my opinion, too narrowly focused).
My purpose was mostly just to test MiaB as a project and the project performed flawlessly except for this one issue.
I did not modify any network settings on the server, but did configure pfSense to open ports (except 53) to MiaB, plus I used an external DNS server.
