Skip to main content
Version: Unreleased

Monitor GUI Port Recovery

Problem​

When the Monitor GUI port config is changed to an invalid or already used port (for example port 443, which is used by CCM) through the Monitor dashboard UI, the server fails to bind to the new port and crashes. Because the value is persisted in the SQLite database, every restart reads the same bad value and crashes again. The Monitor becomes permanently unreachable.

Solution​

A recovery script is included in the Monitor image that resets the GUI port to its default value (445). The script removes the port setting from the database so the application falls back to the default on the next startup.

Step 1 — Run the recovery script​

podman exec mon /moki/scripts/reset-gui-port.sh

Or if using Docker:

docker exec mon /moki/scripts/reset-gui-port.sh

Expected output:

GUI port reset to default (445). Restart the container to apply.

Step 2 — Restart the container​

podman restart mon

Or:

docker restart mon

Step 3 — Verify​

Access the Monitor UI on the default port:

http://<hostname>:445