Frank Elsinga

Please see the pinned issue for information

@homelab-alpha curl is also doing http request, not the different monitor. @ashrude did you restart the container after editing the host file? I am not shure how node caches this..

Yes, but you really don't have to ask for such things. Just provide a PR For this PR, please make sure that it fits into the rest of the UI...

Related: - https://github.com/louislam/uptime-kuma/issues/5122#issuecomment-2888699249

@mabed-fr I did a few experiments in gimp and none of them looked remotely acceptable. What was the design you were thinking about?

So really you are requesting that if hovering over/near errors, the information from below is shown? 

@adityarawat007 we don't assign people. First of all because we can't (only contributors and the issue creates can be assigned) and secondly because we don't think that the additional burocracy...

``` docker exec uptime-kuma ping -c 1 ipv6.google.com connect: Network is unreachable ``` If ipv6.google.com is not reachable from the docker container, this is not our fault. There is something...

Could you try the debugging step in https://docs.docker.com/engine/daemon/ipv6/#use-ipv6-for-the-default-bridge-network first? This seems like a bug in docker..

No, does docker run --rm -p 80:80 traefik/whoami bind to ipv6 The docs pretty clearly state that the docker compose part should not be nessesary