uptime-kuma: monitor type ping stopped working

Info Uptime Kuma Version: 1.3.2 Using Docker?: Yes OS: Windows (client) Docker with uptime-kuma runs on Debian 10 Browser: Chrome

I installed uptime-kuma a few days ago and setup a few monitors, most of them https and one as ping type. The ping type one stopped working yesterday evening. I know the target is up, even if I do a docker exec -ti uptime-kuma sh and do a manual ping to the same target the ping works so why does it keep failing for a full 24h inside uptime-kuma?

Also, uptimerobot reports no issues pinging this particular host.

Open for any suggestions.

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15 (7 by maintainers)

Commits related to this issue

raise the ping timeout from 2s to 10s (avoid #294) — committed to louislam/uptime-kuma by louislam 3 years ago

Most upvoted comments

Just wanted to let you know, that I have now added fixed DNS servers to uptime-kuma’s docker-compose.yml file

    dns:
      - 1.1.1.1
      - 9.9.9.9
      - 8.8.8.8

Response times have gone seriously down compared to before. Before this, the docker host used to use a locally (Docker run) DNS (adguard home).

ovizii on Sep 1, 2021

Thanks, I have switched to :1.5.2-debian and everything seems fine. I guess I’ll check in a few weeks later and figure out how you are handling tags. For now I’ll keep using 1.5.2-debian - maybe later you’ll have a generic :debian or whatever.

If Debian is better for most users, I will use Debian as main tag in the future. For example:

1.6 (Debian)
1.6-alpine (Alpine)

louislam on Sep 1, 2021

Please let me know if you think its my local system and not due to the alpine base image, I can do further tests.

ovizii on Sep 1, 2021

My guess: Your dns server is slow. It takes more than 2 seconds to resolve a domain.

You can ping the IP directly.

louislam on Aug 31, 2021