Louis Lam

Should be memory leak. You should find the log in `~/.pm2/logs`

Thanks for the info! Hope I can figure out the problem. > It's odd the processes are growing as well I guess it causes by this bug, I recently fixed:...

Should be fixed by https://github.com/louislam/uptime-kuma/commit/466b403a96917b4363f82fa9bf8244ff0a079ff2 now. You can test it using master branch.

https://github.com/louislam/uptime-kuma/commit/1da00d19fdd9d2e01114f5b2e463025f0d78dc47 should fix your new issue. But unfortunately, avoiding getPeerCertificate error didn't solve the issue. At this point, I have no idea where is the memory leak.

Enable inspector 1. Edit `ecosystem.config.js`, add `--inspect` like this: ``` module.exports = { apps: [{ name: "uptime-kuma", script: "./server/server.js", env: { NODE_OPTIONS: "--inspect" } }] }; ``` 2. Remove previous...

Auto is working fine in my region. I manually set it to Paris Timezone, it is still working fine. 

Which guide did you follow when you were installing Uptime Kuma? Usually you were using a different data directory or volume.

Should we use `$t('Search...')` instead? Because `Search monitored sites` is English only.

> Please don't add the English translations to non English files as it will fall back to the English translation if no other translation is found and will just cause...

Going to work on it. I merged conflict and added `v-if` to the field, so it shows only if http(s) related monitors. But there are some questions/issues: - Timeout value...