Louis Lam

Can you see the cert expiry date on the dashboard? It happens when it is failed to retrive the cert: https://github.com/louislam/uptime-kuma/blob/2adb142ae25984ecebfa4b51c739fec5e492763a/server/prometheus.js#L73-L75

Confirmed, 1.19.0-beta.0 is ok, but 1.19.0-beta.1 is bugged.

Have you try to restart the container? Because tcp monitor is no code change. beta.2 and 1.19.0 are nearly identical.

I cannot reproduce the issue. Could you backup the volume and downgrade to 1.8.5, see if the problem whether is gone. Also can you reproduce on https://demo.uptime.kuma.pet:27000/

I remember someone asked before, but i cannot find the issue. As I remember, the down email was unexpectedly rejected by email vendor for unknown reason.

Duplicate of https://github.com/louislam/uptime-kuma/issues/978

Are there any error just before `INFO: Shutdown requested` If no, it probably shutdown by external factors: - Docker healthcheck (You should check the healthcheck log) - Docker deamon restart...

``` Called signal: SIGTERM ``` I checked, the `SIGTERM` signal should be probably sent from `docker stop`, I suggest you should check the docker log, find out what or who...

I have no plan to switch the project language to Typescript. I would rather spend time on reviewing and merging pending feature pull requests.

`Maintenance Time Window` only activate if the current date is within the `Effective Date Range`