Frank Elsinga

@jahway603 This is currently in 1.22:  Can you close this issue, since it is resolved?

@97WaterPolo Could you please check if this issue is still an active issue? This seems like it is resolved.

@shleeable as noted by @lucasnz in #3885 (we will review this PR in 2.1) the http monitors are blocked by these issues upstream: - https://github.com/axios/axios/issues/5785 - https://github.com/axios/axios/issues/590

I was not here when axios was chosen. I am not aware of any alternatives to `axios` offering the features (robust error handling, proxy support, ...) we need. Given the...

Related #1308 #3743 Unsure which issue is a duplicate of the other

Closing in favor of https://github.com/louislam/uptime-kuma/issues/1308 and https://github.com/louislam/uptime-kuma/issues/3743 as handlng this in two PRs is likely better => having two issues is also better. This third issue is not nessesary =>...

I am going to close this issue due to lacking enough specificity and braindump-issues (multiple issues being collected into one) not being managable for us. More in-depth ratinale: - FTP...

Is this one of the duplicates linked to https://github.com/louislam/uptime-kuma/pull/1236?

> Yes i want to monitor it, but no it's not relevant enough to notify me with any notifications. You could just disable the notifiations for said monitor. Am I...

@Vecsy We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/1089 and as there is no functional difference (maybe...