From e9b532ccd8c3f242bfa0e35762f9351c6f3a542c Mon Sep 17 00:00:00 2001 From: Louis Lam Date: Thu, 23 Jun 2022 16:16:11 +0800 Subject: [PATCH 1/2] Update to 1.17.1 --- 🆙-How-to-Update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/🆙-How-to-Update.md b/🆙-How-to-Update.md index 6342075..d4770d6 100644 --- a/🆙-How-to-Update.md +++ b/🆙-How-to-Update.md @@ -34,7 +34,7 @@ cd # Update from git git fetch --all -git checkout 1.17.0 --force +git checkout 1.17.1 --force # Install dependencies and prebuilt npm install --production From e983952325ac9bbfc3a97a80265d7adc42fec9bc Mon Sep 17 00:00:00 2001 From: Louis Lam Date: Thu, 30 Jun 2022 16:39:37 +0800 Subject: [PATCH 2/2] Created Troubleshooting (markdown) --- Troubleshooting.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 Troubleshooting.md diff --git a/Troubleshooting.md b/Troubleshooting.md new file mode 100644 index 0000000..75552b8 --- /dev/null +++ b/Troubleshooting.md @@ -0,0 +1,16 @@ + +## Uptime Kuma reports DOWN, but I can access. + +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. + +Go into your container's bash. + +``` +docker exec -it uptime-kuma bash +``` + +Then you can test with these commands for example: +``` +curl https://google.com +ping google.com +```