Master is now the 0.29 release candidate

[JoshData]

Hi all,

The master branch is new a release candidate for the next release v0.29. I'd appreciate everyone's help testing it for those who know how. If there are no problems, I'll post a release in about 10 days.

This may be the last release before the Ubuntu 18.04 branch is released. Because of Nextcloud upgrade issues, this will be a required upgrade for everyone, meaning upgrading from Mail-in-a-Box v0.28 or earlier to the Ubuntu 18.04 will not be supported. Only upgrades from v0.29 (or later, if we have subsequent Ubuntu 16.04 releases) will be supported.

Thanks everyone.

[just4t]

Only upgrades from v0.29 (or later, if we have subsequent Ubuntu 16.04 releases) will be supported

• Perhaps, you wanted to say:
  Only upgrades from v0.29 (or later, if we have subsequent Ubuntu 14.04 releases) will be supported

[JoshData]

Quite right!

[yodax]

I’m running master without issues. I haven’t tested a new install.

[just4t]

@JoshData As requested installed as fresh, over an up-to-date VULTR 14.05 image smoothly without issues ... I didn't test it in deep yet as that has been just an install test.
Reported as Mail-in-a-Box Version: v0.28-10-g6eb9055

• Going now to update my production server after snapshot it and I'd report here if any issue arise.
  [181013-0804-CEST] Production server upgraded, too with no issues so far.

[jvolkenant]

Upgrade wen't ok so far v0.26c -> v0.28-10-g6eb9055

[tdulcet]

#1435 fixes dozens of bugs in the bash scripts (found by ShellCheck) and adds continuous integration...

See the install log here.

[JoshData]

I'm not going to include #1435 in the next release because it needs to be reviewed etc.

[rfrush]

I pulled the master branch to /root/mailinabox and ran ./setup/start.sh.

Old version: v0.28
New version: Mail-in-a-Box Version: v0.28-10-g6eb9055

The upgrade completed without any errors or issues. A basic status check suggests everything is working fine.

My certs are due to auto update in about 6 days from (2018-10-22). I had problems with the initial installation of the certs, and I'll report how the renewal goes in a few days.

[rpatrick1]

Tried a new build with this - all worked without any problems at all.

[KeiroD]

Hi,

Only error I get is this:

Log:
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags. 

I provisioned TLS cert, though via the admin screen. Everything is updated. At least, it seems so, since it's running v28. The system checks all indicate A-OK.

Edit: I lied, apparently nginx is now throwing an error 500 on the admin screen after a reboot. Investigating...

[DeviantEng]

Interestingly, I started getting the same issues as @KeiroD. I had to bounce my VPS to get to the admin page, and I can't get LE to update a cert. Getting that same error message:

Log:
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None You should register before running non-interactively, or provide --agree-tos and --email <email_address> flags.

Thoughts?

EDIT: Found a forum post that suggested a sudo mailinabox, which had a prompt to accept the LE ToS. Seems to have fixed my issue.

Evidently, curl -s https://mailinabox.email/setup.sh | sudo bash doesn't prompt this, which is what I normally run.

[JoshData]

Thanks everyone! I've released v0.29!

[hannahbee91]

@JoshData Does this mean that, with the update to v0.29, it's safe to run do-release-upgrade on our servers? I want to upgrade from 14.04, so does this support 16.04, or only 18.04? I just want to make sure this update goes as smoothly as possible.