Complete Guide to Installing Uptime Kuma 2.5: Advanced Monitoring for Your Services

Uptime Kuma is an open-source and self-hosted monitoring tool, designed to check the availability and proper functioning of web services, ports, DNS, databases, containers, and applications. Version 2.5 introduces new features and significant improvements, making the tool even more versatile and secure.

This guide is useful for system administrators and IT professionals who need to monitor critical services efficiently and securely. Thanks to the new features, Uptime Kuma 2.5 allows you to extend monitoring to NTP services, improve container security, and further customize notifications.

• NTP Monitoring: Check the reachability and proper functioning of Network Time Protocol services.
• Container Security: Run Uptime Kuma without root privileges inside containers, reducing the risks of compromise.
• Custom Monitoring Intervals: Configure longer monitoring intervals for services that do not require frequent checks.
• Advanced Notifications: Integrate Plivo SMS and voice calls, Ooredoo Maldives SMS, WxPusher Simple Push Token, and Flowtriq DDoS detection alerts.
• Security Improvements: Update dependencies and introduce a 14-day cooling period to reduce the risks of supply-chain attacks.

Prerequisites

• Hardware: A server or device with at least 1GB of RAM and 10GB of available disk space.
• Software: Docker and Docker Compose installed on the system.
• Administrative Access: Administrator permissions to install and configure the software.
• Internet Connection: To download Docker images and access online resources.

Procedure: Updating and Configuring Uptime Kuma 2.5

By the end of this guide, you will have updated Uptime Kuma to version 2.5 and configured the new features.

• Perform a backup of your current configuration data.
• Update Uptime Kuma to version 2.5 following the specific instructions for your execution environment (Docker, npm, etc.).
• Log in to the Uptime Kuma administration interface.
• If you use containers, set the new next-rootless tag to run Uptime Kuma without root privileges.
• Add custom headers to SMTP notifications.
• Enable optional tracking via Rybbit Analytics for public status pages.
• Verify that secure MQTT addresses use the mqtts:// protocol.
• Check that Steam monitors correctly resolve hostnames and that Kafka monitors have timeout functionality.
• Fix any issues with URLs associated with the DNS monitoring service, protocols saved in Globalping ping monitors, time zones for Discord notifications, browser engine screenshot delays, and malformed badge URLs.

Verification and Troubleshooting

After configuring Uptime Kuma 2.5, it is essential to verify the correct operation of the monitors and resolve any issues. Follow these steps to test and troubleshoot.

Functionality Test

• Monitor Verification: Log in to the Uptime Kuma administration panel and check the status of all configured monitors. Ensure that the monitors are in "Up" or "Down" status based on their actual availability.
• Notification Test: Verify that notifications are configured correctly. Send a notification test for each configured method (email, SMS, etc.) to ensure they are received correctly.
• Log Check: Examine Uptime Kuma logs to identify any errors or warnings. Logs can provide valuable information for troubleshooting.

Problem Resolution

• Non-Functioning Monitors: If a monitor is not working correctly, verify the configuration details. Check the IP address, port, protocol, and other relevant settings. Ensure that the monitored service is accessible from the location where Uptime Kuma is hosted.
• Notification Issues: If notifications are not being sent, verify the notification method settings. Check credentials, configuration parameters, and connectivity with external services.
• Security Issues: If you encounter security issues, update the project dependencies and verify that the latest security fixes have been applied. Ensure that the system is protected from potential attacks.
• Configuration Issues: If you encounter configuration issues, consult the official changelog for information on any fixes or changes made in version 2.5. Consult the changelog.

By following these steps, you can verify the correct operation of Uptime Kuma 2.5 and resolve any issues that may arise.

With this guide, you have learned the main new features introduced by Uptime Kuma 2.5 and how to use them to improve the monitoring of your services. Now you are ready to implement these features in your environment.

Here is a summary of the key steps:

• Verify the integrity of NTP services with the new monitor type.
• Explore the next-rootless Docker option for a more secure deployment.
• Integrate new notification options such as Plivo SMS and Rybbit Analytics.
• Fix any issues specific to existing monitors.

For more information, consult the official changelog.

If you haven't tried Uptime Kuma yet, follow the setup guide to get started quickly with Docker.