Home /  MMonit /  Release 4-4-0

Released on Nov 18, 2026

New installation | Upgrading

  1. New
  2. Fixed
  3. Enhanced

Changes Version 4.4.0

This release focuses on security, storage efficiency and performance.

  1. Two-factor authentication (2FA): Add an extra layer of security to your account. You log in with your password and a time-based code from your authenticator app. If a user loses the authenticator, mmonit-admin can turn off 2FA for that user.
  2. Quantum-resistant cryptography: Added support for hybrid ML-KEM key exchange with TLS 1.3. No configuration or certificate renewal is needed.
  3. Analytics storage: The default analytics configuration needs about 30% less database storage than M/Monit 4.0.0 to 4.3.4. You can also tune the analytics storage on the Admin/Settings page. Turn each precision level on or off and set how long it keeps data. The page shows the current and the estimated database usage.
  4. New charts: Swap paging activity, file size, network errors and file descriptor usage for systems and processes. Swap paging needs Monit 5.36.0 or later. Network errors need Monit 5.11.0 and file descriptors Monit 5.27.0. The chart type selector has a new search field. The "Custom range" selector has a date and time picker.
  5. Status Details: The page now includes swap paging activity and file descriptor usage. It also shows the number of subdirectories in a directory and the number of hard links to a file or fifo. These two need Monit 5.34.0 or later. The service actions are now both above and below the services table. That helps when a host has many services.
  6. Fine-grained event types: Monit 6.1.0 and later report a specific event type for every test. Instead of the old "Resource" class, you see "CPU usage" or "Space usage".
  7. Unmonitored service warning: M/Monit warns you when a service is not monitored. The host shows a warning on the Dashboard and on the Status page. You can now turn the warning off in the Admin/Settings page.
  8. Dashboard: The Dashboard now tells you when M/Monit cannot send alert mail. It shows the reason, such as a mail server that is down or refuses the login. A link takes you to the mail server settings.
    The Dashboard also tells you when M/Monit refuses the reports from a Monit agent. It shows the host name and the reason.
  9. Admin/Hosts: The hosts table is now paginated. You can filter hosts by host group and LED. The "Delete Hosts?" button can be used to delete all hosts that match the filter.
  10. User management via CLI: mmonit-admin can now create, delete and list users. It can also assign and revoke roles and list the available roles.
  11. Bash completion for mmonit and mmonit-admin: Bash now completes options, arguments and option values. For mmonit-admin it also completes user and role names. The bash-completion package 2.12 or later loads the completion by itself. Otherwise source the two files in share/bash-completion/completions from ~/.bashrc.
  12. Easier upgrades: Start mmonit with the new -u option and it upgrades an older database in place.
    The Upgrade program now checks the database permissions before it starts. It can resume a failed or interrupted upgrade where it stopped. The new -t option sets its timeout, and the output is clearer and in color. Upgrading a large database can take a while and we show a progress bar with a clock, so you know the upgrade has not stalled.
  13. Docker: The container image is now OCI compliant and includes curl for Alert Service scripts. It upgrades the database on start, shows errors in docker logs and keeps the log files in a volume.
    M/Monit might need some time at stop to store its statistics and pending alerts. The docker run command that build.sh prints gives it 2 minutes, and so does the Compose file it writes. If you start the container another way, give it the same time with docker run --stop-timeout 120. M/Monit usually stops within seconds, but a database operation in progress can make it take longer.
  14. Email alerts now carry headers that stop out-of-office replies from Exchange, Outlook, Office365 and Gmail.
  15. Security hardening: Weak SSL ciphers are now off by default. RSA, DSA and DH keys must be at least 2048 bits long, and ECC keys at least 224 bits.
  16. CSRF protection: M/Monit now uses the Sec-Fetch-Site and Origin headers that browsers send. It protects every request that changes something, including the login form. Scripts that use the HTTP-API need no CSRF token. M/Monit ignores the old z_csrf_protection login parameter and the CSRFToken header. /api/2/session/get no longer returns a token.
    A reverse proxy that changes the Host header must set X-Forwarded-Host to the host name the browser used. Apache's mod_proxy does this by default. For nginx, add proxy_set_header X-Forwarded-Host $http_host;. See Appendix C in the manual.
  17. "Keep me signed in": A remembered login now lasts up to 30 days. It ends after 7 days without use and survives a restart of M/Monit. Your profile page shows when the session ends.
  18. Admin General: "Active Sessions" is now "Login Sessions" and shows the number of authenticated sessions. I.e. logins.
  19. "No report from Monit": M/Monit now waits at most one hour for a status report before it reports a host as down. Before, it waited the host's poll cycle times its report skew, however long that was. Monit before 6.0.0 reports only once per poll cycle. For these versions M/Monit waits up to two poll cycles if that is longer. The host's page in Admin/Hosts shows how long M/Monit waits.
  20. With many hosts on MySQL or PostgreSQL, M/Monit now stores the statistics in batches instead of one row at a time. It stops about three times faster. It also starts faster with many hosts, particularly on MySQL.
  21. server.xml: Size and time attributes now take units, like fileCache="10 MB" or sessionTimeout="30 min". M/Monit checks the values on start. A value without a unit means what it did before. server.xml documents the base unit of each attribute.
  22. server.xml and web.xml: An error now names the line of the faulty element. It also names the line where the enclosing element begins.
  23. Access log: M/Monit no longer looks up host names. The enableLookups attribute in server.xml is no longer supported, and the access log records the client's IP address. To see host names, resolve the log afterwards with a tool like Apache's logresolve. A server.xml that still sets the attribute gives a warning on start.
  24. Execute Program actions: A program now always has a timeout. You can choose 1, 3 or 5 minutes, and 3 is the default. "Never" is gone. The Upgrade program sets previous "Never" and longer timeouts to 5 minutes, so review your Execute Program actions after the upgrade. Alert Service scripts work the same way with a 3-minute timeout.
    Keep the output of a program short. A program that writes more than 16 KB waits until its timeout stops it. M/Monit reads at most 500 lines of its output.
  25. Restored Forward Secrecy support with the ECDHE cipher suites. This was a regression in M/Monit 4.1.0.
  26. HTTP-API (breaking changes): The host and alert admin endpoints no longer return plaintext passwords. /api/2/admin/hosts/test now takes only a host id instead of arbitrary connection parameters. This prevents Server-Side Request Forgery (SSRF).
    A failed login now returns HTTP 401 instead of 200, and the x-auth: denied header is gone. Scripts that log in should check for 401. If your reverse proxy replaces error pages, exclude 401 so users still see M/Monit's login error page. The settings are proxy_intercept_errors in nginx and ProxyErrorOverride in Apache. A successful login now gives the session a new id. Scripts must store the cookie from the login response. With curl, use -c as well as -b on the login request.
    /api/2/reports/events/dismiss, /api/2/session/put, /api/2/session/delete and /api/2/session/invalidate now accept POST only. They answer a GET with HTTP 404. /login/logout.csp is gone. Post to /api/2/session/invalidate to log out.
    M/Monit answers HTTP 400 to a parameter that is not valid UTF-8 or too long to store. A request that changes something gets HTTP 200 and an empty body instead of {"status":"ok"}. Check the status code.
  27. Security fixes: Fixed XSS in the Events report in mobile mode and in the Dashboard's license limit warning. Fixed SMTP header injection through a customized mail format. All template output is now HTML-escaped. Dismissing an event or adding a note now checks the user's permissions. Plus other security and stability fixes.
  28. Logs: M/Monit now escapes control characters and line breaks in the logs, as Apache and nginx do. If you use fail2ban, update the filter from the wiki. Its patterns now match only at the start of a line, and it also catches failed two-factor logins.
  29. Sessions: A session could time out too early. M/Monit counted the timeout from the request before the last one. A login could fail if the browser had two session cookies for M/Monit. This could happen when M/Monit was used both directly and through a proxy, or over both http and https. mmonit-admin users password and mmonit-admin users delete now also end the user's logins.
  30. Roles: Users with a custom role got "Access denied" on service actions in Status Details. This happened even when the role gave them the "Service Actions" permission for the host. If the database was down while roles were reconfigured, M/Monit lost the roles until a restart.
  31. Mail alerts: A mail server that stopped answering in the middle of a session held back every alert behind it. M/Monit now waits at most 30 seconds for a reply. Then it ends the session and tries again later.
    Admin/Users now refuses an email address that M/Monit cannot send to, such as one with an underscore in the domain. The Upgrade program lists each user with an invalid address, so you can correct them in Admin/Users.
    M/Monit saves unsent alerts when it stops. One alert that cannot be saved no longer loses the others.
  32. Alert Rules: A catch-all rule with the "Send Instant Message to user" action now leaves out hosts the user may not view.
  33. Host Groups: The old name of a renamed host group can now be used again without a restart. The host group cache also stays in sync with the database.
  34. Text outside ASCII: The Upgrade program repairs text stored with the wrong encoding. On SQLite it converts names that M/Monit 4.3.4 stored from a Monit control file saved as Latin-1. On MySQL and MariaDB it fixes text that M/Monit 3.7.12 and earlier garbled, so e.g. "Müller" becomes "Müller" again. The upgrade prints each change. It also converts MySQL and MariaDB databases to utf8mb4. They can then store emojis etc. Names that differ only in case or accents become different names, as on SQLite and PostgreSQL. M/Monit now refuses a service name that is not valid UTF-8, so save your Monit control files as UTF-8.
  35. Analytics: On MySQL, an index removed in 4.3.3 is back. Without it, the start and the statistics cleanup were very slow on a large database. Moving averages are now right when Monit sends the same value again. M/Monit now saves the analytics data it is still collecting when it stops. Many analytics requests at once no longer stall M/Monit. A request over the limit gets HTTP 503 with Retry-After.
  36. Large databases: Deleting old events or hosts no longer holds back new events and their alerts. A stop no longer waits for old events to be deleted.
  37. Uptime report: A custom range that ends in the future no longer shows false downtime.
  38. Redirects: A redirect now keeps the address the browser used, even when M/Monit listens on another port. This is common with docker run -p 80:8080, NAT and port forwards. It also applies behind a proxy with proxyScheme="https" and no proxyPort. A redirect now keeps the brackets around an IPv6 address.
  39. License limit: M/Monit now answers HTTP 402 to a Monit agent over the license limit. Monit logs the error and keeps its events queued. The Dashboard shows a warning for the refused host.
  40. Start and stop: mmonit stop now also stops an M/Monit that is still starting, for example during an upgrade with -u. A stop no longer waits for a mail server that does not answer. It goes on if the database is down, so systemd no longer marks the service as failed. On PostgreSQL, one failed write at stop no longer loses other data. M/Monit now starts even when a saved alert names a mail server that was removed.
  41. Stability: Fixed a number of crashes, hangs, memory leaks and race conditions. Among them were crashes on stop and problems keeping the cache in sync with the database. The event purge could also stop after a database error. M/Monit no longer hangs at start with an unsupported MySQL proxy such as MySQL Router. It stops with an error instead. An error that repeats is now logged once and no longer fills the error log. Examples are a database write that keeps failing and a Monit agent whose messages are refused.
  42. Updated OpenSSL to fix these CVEs:
         CVE-2024-9143
         CVE-2024-13176
         CVE-2025-11187
         CVE-2025-15467
         CVE-2025-15468
         CVE-2025-66199
         CVE-2025-68160
         CVE-2025-69418
         CVE-2025-69419
         CVE-2025-69420
         CVE-2025-69421
         CVE-2026-7383
         CVE-2026-9076
         CVE-2026-14457
         CVE-2026-18798
         CVE-2026-22795
         CVE-2026-22796
         CVE-2026-28388
         CVE-2026-28389
         CVE-2026-28390
         CVE-2026-31789
         CVE-2026-31790
         CVE-2026-34180
         CVE-2026-34181
         CVE-2026-34182
         CVE-2026-35189
         CVE-2026-42766
         CVE-2026-42767
         CVE-2026-42768
         CVE-2026-42769
         CVE-2026-42770
         CVE-2026-45445
         CVE-2026-45446
         CVE-2026-45447
         CVE-2026-54872
         CVE-2026-54874
         CVE-2026-54875
         CVE-2026-63072
         CVE-2026-63073
         CVE-2026-63074
         CVE-2026-63075
         CVE-2026-63076
         CVE-2026-72897
         CVE-2026-75803
         CVE-2026-75805
         CVE-2026-77696
  1. Updated PostgreSQL to fix CVE-2026-6477.
  2. Updated zlib to fix CVE-2026-4738 and CVE-2026-85091.
  3. Updated the Docker image to Alpine 3.24 to fix CVE-2024-58251, CVE-2025-15467, CVE-2025-46394, CVE-2025-60876, CVE-2026-6042, CVE-2026-27171 and CVE-2026-40200.
  4. Plus many minor improvements and fixes.

Deprecated: XMPP (Jabber) alerts will be removed in a future major release of M/Monit. We recommend Alert Services such as Slack, Microsoft Teams and Telegram for instant messages. If you use XMPP alerts and want to keep them, please tell us at info@mmonit.com.


New installation

  • Download the release for your OS.
  • Unpack the tar.gz file in any directory. Good choices are /opt or /usr/local. Example:
 tar -xzf mmonit-4.4.0-linux-x64.tar.gz
  • Go to the unpacked mmonit-4.4.0 directory
 cd mmonit-4.4.0
  • Optional: Change the passwords of the default accounts:
 ./bin/mmonit-admin users password admin

 ./bin/mmonit-admin users password monit
  • Start M/Monit:
 ./bin/mmonit
  • Point your browser to the host where M/Monit runs, for example http://localhost:8080/ . Log in as admin with the password swordfish, or the password you set with mmonit-admin.
  • To use MySQL or PostgreSQL instead of the default SQLite database, follow these instructions in the wiki.
  • The application and the manual (PDF) have more documentation.
  • Troubleshooting If M/Monit does not seem to run, look in logs/error.log. You can also start mmonit with -id to run it in the foreground in diagnostic mode. It then prints errors and debug information to the console. Press CTRL+C to stop it.

Upgrading from previous M/Monit releases (2.3 or later)

The upgrade program copies the database and the configuration files from the previous installation and updates the database schema. On macOS the installer upgrades M/Monit in /usr/local/mmonit by itself.

The upgrade usually takes less than a minute. A large database takes longer. You do not have to stop or change Monit on other machines. Monit simply starts reporting to M/Monit 4.4.0 when you start mmonit again after the upgrade.

On MySQL and MariaDB the upgrade needs free space in the temporary directory of the database server. That is innodb_tmpdir, or tmpdir if innodb_tmpdir is not set. A large database needs a lot of space there. If the space runs out, the upgrade stops with "Temporary file write failure". Run it again and it should go on from there.

  • Download the new 4.4.0 release for your OS.
  • Install M/Monit 4.4.0 next to the previous release. For example:
 /usr/local/mmonit-4.3.4
 /usr/local/mmonit-4.4.0
  • Stop the previous M/Monit release.
 /usr/local/mmonit-4.3.4/bin/mmonit stop

Or if Monit monitors M/Monit:

 monit stop mmonit
  • Run the upgrade program with the path to the previous M/Monit release:
 /usr/local/mmonit-4.4.0/upgrade/upgrade -p /usr/local/mmonit-4.3.4
  • Start M/Monit 4.4.0:
 /usr/local/mmonit-4.4.0/bin/mmonit
  • Finally, clear your browser cache before you open M/Monit 4.4.0.