Https://discourse.mailinabox.email/t/waiting-for-the-mail-in-a-box-management-daemon-to-start-message-looping-forever/1160

Hi, I am having this exact same issue as outlined in the post:

OP did not post his fix, can anybody help?

Thanks very much.

Following advice given in the original post, I tried mxtools with my domain. The result was LOOP DETECTED WE WERE REFERRED BACK TO … the transcript is:

PWS3v2 266ms
0 z.au 37.209.198.5 NON-AUTH 46
ms Received 2 Referrals , rcode=NO_ERROR happygoanna.com.au. 14400
IN NS ns2.box.happygoanna.com.au,happygoanna.com.au. 14400 IN NS
ns1.box.happygoanna.com.au,

1 ns1.box.happygoanna.com.au 128.199.224.255 NON-AUTH 218 ms , rcode=SERVER_FAILURE

1 ns2.box.happygoanna.com.au 128.199.224.255 NON-AUTH 218 ms Loop Prevented, rcode=SERVER_FAILURE

I wonder if anybody could tell me what is wrong?

Thanks very much for any help!
Cheers

@Vatyx , would really appreciate knowing how you resolved this mate… Cheers

Here is the output of the script prior to going into the loop behaviour…

Primary Hostname: box.happygoanna.com.au
Public IP Address: 128.199.224.255
Mail-in-a-Box Version: v0.17c

Updating system packages…
Installing system packages…
Initializing system random number generator…
Firewall is active and enabled on system startup
Installing nsd (DNS server)…
Installing Postfix (SMTP server)…
Installing Dovecot (IMAP server)…
Installing OpenDKIM/OpenDMARC…
Installing SpamAssassin…
Installing Nginx (web server)…
Installing Roundcube (webmail)…
Installing ownCloud (contacts/calendar)…
ownCloud is already latest version
Installing Z-Push (Exchange/ActiveSync server)…
Installing Mail-in-a-Box system management daemon…
Installing Munin (system monitoring)…
Waiting for the Mail-in-a-Box management daemon to start…
Waiting for the Mail-in-a-Box management daemon to start…
Waiting for the Mail-in-a-Box management daemon to start…
Waiting for the Mail-in-a-Box management daemon to start…
Waiting for the Mail-in-a-Box management daemon to start…

… and so on and so on… !!!

Hey man, sorry about the delay.

What I did is I manually changed that part of the sh file. It’s trying to ping something on a certain port but it seemed like that port was closed, and also arbitrary. So I changed it to port 22 and it worked. Just try and find it in that file.

Mate, you’re a legend!!

Changing 10222 to 22 got me past the loop too… I just wonder… how you found that line of code…?

I never saw any output or other indicator, how did you sniff it out???

Cheers and Thanks again for your help!

If you have to modify the box at this point, your box is probably not set up correctly and may not function correctly.

Thanks for the reply @JoshData, and well done on your work!

So far I have been able to do a few things OK, add users, create/send/check emails using roundcube… I was getting some “Sorry something went wrong” popups occur when trying to add a TLS, but after a reboot things seemed to have settled down.

In system status checks only the first two items are red, I have opened a topic on #1 DKIM - would appreciate advice on that and #2 I’m still trying to resolve (SSH server on this machine permits password-based login.).

Once again, great work! You are bringing incredibly difficult setups into the realm of not-so-expert unix users. Just bloody great mate!

For the ssh error, you need to edit /etc/ssh/sshd_config as discussed on this post:

So how do you get around this error if you can’t modify it? I was unable to open that port and I assumed that the script would work on a fresh new install of linux. What was my issue then?

Yes I was also wondering about this… it seemed a very strange/random thing to occur on an otherwise extremely robust setup…

I am also running on a DigitalOcean droplet, and followied the tutorial

and initially set the VPS up according to the referenced tutorial

So maybe it has something to do with some DO networking rules???

Be great to know for sure if the change compromises security or anything.

CHEERS!

Thanks very much @v60fan that helped so much.

FYI, the line that now exists in that file by default is (at least on my new install):

PasswordAuthentication yes

So for anybody else don’t forget to both

  1. uncomment the line
  2. change the yes -> no.

thanks again mate.

Cheers

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.