Uptime Kuma has recently released version 1.23.3, bringing important bug fixes and security updates to its server monitoring software.
One important note for users is that due to a security fix, all login sessions will be logged out after updating to this version. This is a necessary measure to ensure the security of the system.
If you are using any unofficial or third-party tools with Uptime Kuma, it is important to be aware that this update may introduce breaking changes. In such cases, it may be necessary to re-generate an authentication token to ensure compatibility.
The latest release includes several bug fixes that address various issues reported by the user community. These bug fixes include:
- Fixed an issue where notifications were not working if the configuration was too long. This improvement was contributed by @FJBlok.
- Enabled status page certificate expiry badge for all HTTP(s) monitors, thanks to @marvinruder.
- Fixed bugs related to the Kafka producer, with contributions from @mhkarimi1383.
- Addressed an issue where
x-forwarded-host was not being utilized correctly. This fix was provided by @xuexb.
- Resolved a race condition issue in the status page editor that prevented some data from being saved when clicked too quickly. This fix was made possible by @chakflying.
In addition to bug fixes, version 1.23.3 also brings important security fixes. One notable fix addresses a persistent session tokens issue. Prior to this update, there was no way to revoke session tokens even if the password was changed. With this update, users can now revoke session tokens by changing their password. More information about this security fix can be found here.
This latest release of Uptime Kuma provides users with important bug fixes and security updates, ensuring a more reliable and secure server monitoring experience.