-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Troubleshooting
Colgrave edited this page Oct 9, 2024
·
7 revisions
Tip
In case you did not know: docker has more than one network type with only some of them allowing access to the local network and some not even allowing access to remote networks
If your Uptime Kuma reports DOWN
of your service, knowing if it is a bug of Uptime Kuma / a docker network misconfiguration or a firewall is a good start to fixing the issue.
To debug this, go into your container's bash via
docker exec -it uptime-kuma bash
Install curl
apt update && apt --yes install curl
Then you can debug this issue with commands like ping
, curl
, ...
Examples:
curl https://google.com
ping google.com
If you are running Uptime Kuma on top of Docker and the service can only be access via IPv6. Please follow the Docker's official wiki to enable IPv6 support.
IPv6 are not supported out of the box on Docker.