I actually think the patch is not such a good idea to merge as is though. It’s useful to bypass this issue but applied at large, it seriously reduces the security of the installation script.
A bypass prompt for such issues would be ideal but implies a lot of testing.
Just tried upgrading to V0.27 and got the same error. marcchampagne’s solution got me passed the Z-Push issue, but now I have an infinite “Waiting for the Mail-in-a-Box management daemon to start…” Not sure if it is related or a different issue…
Primary Hostname: box.XXXXXXXXX.net
Public IP Address: XXX.XXX.XXX.XXX
Mail-in-a-Box Version: v0.27
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 Nextcloud (contacts/calendar)…
Nextcloud 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…
This has been going on for about 40mins now…
e-mail seems to be function correctly, can send and recv via SMTP and roundcube.
But admin page gives a “502 Bad Gateway” error.