Frank Elsinga

@louislam had some reservances to this in the past. I don't want to step on his shues on this one - I am a junior maintainer after all.

Answering the question: no, this is not currently something that can be configured. I'd assume that after making the Beat-Range configurable this should be a fairly simple thing. Feel free...

We have a healthcheck that our dockerfile registers. We just query localhost. https://github.com/louislam/uptime-kuma/blob/13a85b82005da06c82720d3b7459c3bb1bfe7bd4/extra/healthcheck.go#L71 Usually, that catches all erros and is reasonably performant.

Maybe relevant for some: that we currently support the tls versions that node supports by default.

Yes, just pass the relevant node environment variables. Please fix your services instead of bodging like this though.

I guess what could work is changing the existing tabs to be actual, clickable tabs in one PR and in a second PR add a new tab showing details on...

To update this issue: Some work has gone into the evaluation engine behind us, but this has not been applied to the http monotors. See the dns monotor for further...

I read the following PR/issue as if `std::ops::RangeFull` and `std::ops::RangeToInclusive` does not yet have support in serde - https://github.com/serde-rs/serde/issues/2685 - https://github.com/serde-rs/serde/pull/2686 `std::ops::{Range,RangeTo,RangeFrom}` seems unproblemantic though.

Have you allowed the docker container access to localhost outside of the container? (Read: are you running the container in host network mode) https://github.com/louislam/uptime-kuma/wiki/Troubleshooting

You can allow access to the host network via `--network=host`.