I posted a topic about three weeks back asking for help with an install I was having problems with. The post is here Systemd-resolved.service is masked
Apologies for not picking this up on that topic but life took over for a while.
The immediate problem then was resolved by including googles name-servers in my resolv.conf file, which otherwise only contained local host, which enabled the install script to find and install a number of things where otherwise it would just stall. The install script then got as far as starting Mail-in-a-Box management daemon but this message then just repeatedly looped without progressing.
There were some old posts on this forum about this problem on the previous version of mailinabox on ubuntu 14.04. One suggestion was that Port 10222 in the Start.sh script should be changed to port 22. I have not tried this because there were further posts indicating such changes would cause MIAB to fail.
In the responses to the posts three weeks ago there was a comment that indicated that my problem was my low end vps and this system being likely to run MSAzure related services and therefore that this would be incompatible with MIAB. I dont really understand the implications of this because I am not very technical. The suggestion was that I should change to another provider. I am not able to do this right now because of the cost.
So my questions really are
- is there anyway to seek workarounds to the problems I am having running the Mailinabox Startup script?
- If not and you all think the problem is because of my VPS and MS azure does this mean that I will have to give up on a MIAB install and find another solution?
Thanks in advance for any help you can give.