Released on February 9, 2024
Changes Version 4.1.1
This is a bug fix release which fixes a few important issues
- Introduced new options for configuring outgoing TLS connections. Refer to the documentation for details on the <SSLClientConfig> element. In the previous 4.1.0 release, we activated verification of the remote host's SSL certificate. This verification enforced two constraints: the remote certificate could not be self-signed, and the connection failed if the hostname in the certificate did not match the address M/Monit connected to. This led to unintended consequences, as many users rely on self-signed SSL certificates with Monit. This release addresses this issue by allowing you to configure M/Monit to connect to servers using self-signed certificates and to disable hostname verification if the certificate's hostname does not match the host. Below is the configuration for the new <SSLClientConfig> element, set up to allow self-signed certificates and disable hostname verification. Copy and place it just under <Host> in server.xml (if you require this configuration):
<SSLClientConfig> <!-- Allow self-signed certificates --> <SelfSignedCertificate allow="true" /> <!-- Disable hostname verification. Enable to prevent MITM --> <HostnameVerification enable="false" /> </SSLClientConfig>
- By an incuria, support for IP version 6 was not activated in M/Monit 4. This is now fixed.
- Download the release for your OS.
- Unpack the tar.gz file in a directory, any directory will do, but unpacking in /opt or /usr/local are good choices.
- Go to the unpacked mmonit-4.1.1 directory
- Run M/Monit using: ./bin/mmonit
- Point your Browser to the host where mmonit is installed (or "localhost" if running on the same machine), for example: http://localhost:8080/ and login as user admin with password swordfish
- If you want to set up M/Monit to use MySQL or PostgreSQL instead of the default SQLite database, follow these instructions in the wiki.
- More documentation can be found inline in the application and in the manual (PDF).
- Troubleshooting If M/Monit does not appear to run, investigate the error.log in the logs directory. You can also run mmonit in the foreground and in diagnostic mode, start mmonit with the -id options. In diagnostic mode, mmonit will print errors and debug informations to the console. Use CTRL+C to stop mmonit in this mode.
The upgrade program can be used to automatically copy database and configuration files from the previous installation and update the database schema. On macOS upgrading is not needed as the installer will upgrade M/Monit in /usr/local/mmonit automatically.
The whole upgrade process should take less than a minute and you do not have to stop or change Monit on other machines during this process. Monit will simply pick up and start reporting to the new M/Monit 4.1.0 version.
- Download the new 4.1.0 release for your OS.
- Install M/Monit 4.1.1 in the same directory as previous release. For example:
- Stop the previous M/Monit release.
Or if you monitor M/Monit via Monit:
monit stop mmonit
- Run the upgrade program and specify the path to the previous M/Monit release:
/usr/local/mmonit-4.1.1/upgrade/upgrade -p /usr/local/mmonit-4.1.0
- Start M/Monit 4.1.1:
- Finally, please clear your browser cache before accessing M/Monit 4.1.1