Closed thomasmerz closed 12 months ago
"500 Server Error" - had to restart container… 🤷🏼♂️
Older Version of Speedtest Tracker v0.11.16 at home is running fine… (needs some automatic update!!!)
Newer version has been totally redesigned/refactored with way too much "overhead" for my usecase… From one single all-in-one container to three containers, extra-network, db-volume, … Might stop using this - or stay on old(er) version? 🤔
Resolved: Speedtest-v2-FSN1-1 is back up in 8f77645
after 1 day, 8 hours, 43 minutes.
"Fix":
Date: Thu Oct 5 14:02:58 2023 +0200
upptime/issues/2013 🚧 newer versions (since v13?) don't work with this simple setup/docker-compose anymore :-(
diff --git a/bin/docker-speedtest-tracker.sh b/bin/docker-speedtest-tracker.sh
index 64ddfe1..5dae477 100755
--- a/bin/docker-speedtest-tracker.sh
+++ b/bin/docker-speedtest-tracker.sh
@@ -10,7 +10,8 @@ function restart_speedtest-tracker () {
docker-compose up -d
}
-docker pull ghcr.io/alexjustesen/speedtest-tracker | grep "is up to date" || {
+# TODO: newer versions (since v13?!) don't work with this simple setup/docker-compose anymore :-(
+#docker pull ghcr.io/alexjustesen/speedtest-tracker | grep "is up to date" || {
restart_speedtest-tracker
-}
+#}
Date: Thu Oct 5 14:03:04 2023 +0200
upptime/issues/2013 🚧 newer versions (since v13?) don't work with this simple setup/docker-compose anymore :-(
diff --git a/docker-speedtest-tracker.sh b/docker-speedtest-tracker.sh
index 0a27051..00fc9e8 100755
--- a/docker-speedtest-tracker.sh
+++ b/docker-speedtest-tracker.sh
@@ -10,7 +10,8 @@ function restart_speedtest-tracker () {
docker-compose up -d
}
-docker pull ghcr.io/alexjustesen/speedtest-tracker | grep "is up to date" || {
+# TODO: newer versions (since v13?!) don't work with this simple setup/docker-compose anymore :-(
+#docker pull ghcr.io/alexjustesen/speedtest-tracker | grep "is up to date" || {
restart_speedtest-tracker
-}
+#}
In
4eff892
, Speedtest-v2-FSN1-1 ($URL_SPEEDTEST_V2_FSN_1) was down: