ric/uptime-kuma
1
0
Fork 0
mirror of https://github.com/louislam/uptime-kuma.git synced 2024-11-30 18:24:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

improved the troubleshooting docs by adding a reference to docker network types and improving the rephrasing the gramar (#70)

Frank Elsinga 2023-12-03 19:14:19 +01:00 committed by GitHub
parent d0413ea29f
commit a8e0792aca
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
Troubleshooting.md

@ -1,9 +1,13 @@
## Uptime Kuma reports DOWN, but I can access. ## Uptime Kuma reports `DOWN`, but the service can be accessed
If your Uptime Kuma reports DOWN of your service, sometimes you would like to know it is a bug of Uptime Kuma or your own Docker network issue. > [!INFO]
> In case you did not know:
> docker has [more than one network type](https://youtu.be/bKFMS5C4CG0) with only some of them allowing access to the local network and some not even allowing access to remote networks
Go into your container's bash. 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
```bash ```bash
docker exec -it uptime-kuma bash docker exec -it uptime-kuma bash
@ -15,7 +19,9 @@ Install `curl`
apt update && apt --yes install curl apt update && apt --yes install curl
``` ```
Then you can test with these commands for example: Then you can debug this issue with commands like `ping`, `curl`, ...
Examples:
```bash ```bash
curl https://google.com curl https://google.com
ping google.com ping google.com