We’ve been using MIAB (Ubuntu 18.04.2) for a couple of months now without issues.
For the last 2 days when I want to login to the admin dashboard I get “502 bad gateway”.
I restart the mailinabox service then I can login there.
Today in the Status Checks Change Notice email I got this:
Mail-in-a-Box Management Daemon is not running (port 10222).
Also, to update some packages, I give the sudo apt-get update
But the status check page still shows 18 software packages that can be updated.
I’m planning to restart the server tonight, but what should be my next step if I get the same 502 error and management daemon not running tomorrow?
Yesterday night I updated all packages and restarted the server.
Today, in the status checks change notice email (3:09 AM) it still says:
Mail-in-a-Box Management Daemon is not running (port 10222)
and 17 software packages that can be updated.
But today I could login to the admin panel without getting the 502 bad gateway error and my system status checks page is showing System Software is up to date.
I had to revert to a 3 days old droplet for other reasons.
Today, the system status checks page is all green and the status change checks notice shows system is up to date.
But the 502 bad gateway error is back. Had to restart the mailinabox service to get in the admin panel.
sudo apt update && sudo apt upgrade # Add a " -y" to the upgrade part if you want to automate in a cron job!
sudo systemctl restart mailinabox # Restarts the Admin panel
This needs to be done sometimes when python or kernel is updated. A reboot might also be recommended in some cases.