gorkem-bwl
f74d1d53f6
fetchMonitorCertificate parsed the monitor URL but passed only the hostname to ssl-checker, which then defaulted to 443. A monitor on a non-standard port such as https://host:54321 therefore had the certificate of whatever answered on 443 inspected instead of its own, surfacing as "N/A" in the certificate expiry box when nothing was listening there. URL.port is an empty string for default ports, so it is mapped to 443 explicitly rather than passed through Number(), which would have yielded NaN. ssl-checker already accepts the port via SSLOptions, so no dependency or signature change is needed. Adds a regression suite covering the reported case (non-standard port), the default-port fallback, an explicit :443, and the NaN guard. Verified by reverting the fix: the three port assertions fail without it. Fixes #3646
Checkmate backend
The backend service for Checkmate, an open source uptime and infrastructure monitoring application
This directory contains the backend of Checkmate, which handles data processing, storage, and API services for the Checkmate monitoring tool. The backend is responsible for managing uptime checks, handling real-time alerts, and storing historical monitoring data.
Checkmate's backend is designed to be lightweight and scalable, ensuring reliable performance even with a high number of active monitors.
Installation & documentation
For setup instructions, configuration details, and deployment guidelines, please visit our official documentation at docs.checkmate.so.
Related repositories
- Capture Agent (Optional, provides additional server insights)