Speedtest Tracker collects hourly throughput measurements for the household and feeds them into Grafana dashboards.
This page documents the speedtest-tracker service.
speedtest-trackerlscr.io/linuxserver/speedtest-tracker:latesthouse_defaultunless-stoppedspeedtest.better-than.tv/srv/docker/speedtest-tracker/confighttp://192.168.0.113:8083https://speedtest.better-than.tvmanage subpath: https://manage.better-than.tv/speedtest/8083 -> 80proxy_cookie_flags/srv/docker/speedtest-tracker/configSPEEDTEST_SCHEDULE=0 * * * * (hourly) against server 31921:8083 before blaming the proxy for missing data2026-04-08, the manage MVP uses a subpath translation layer for Speedtest Tracker because the login page hardcoded the upstream host and used Livewire under /livewire/updatemanage rewrite carries /speedtest/, /speedtest/build/, /speedtest/img/, /speedtest/fonts/, /speedtest/js/, /speedtest/vendor/livewire/, and /speedtest/livewire//speedtest/ base path into the proxied HTML and redirects /speedtest/login plus /speedtest/admin to /speedtest/admin/login so embedded login flow requests stay under the subpath without hijacking the root manage login path/build/assets/, /js/filament/, /fonts/filament/, /vendor/livewire/, and /img/speedtest-tracker-icon.png because the embedded Filament login page can still request those assets at the root manage namespacejson-file/srv/docker/speedtest-tracker is under Duplicati coverageconfig directory so the same cron schedule and server settings stay in placespeedtest.better-than.tv look like UI failures even though the container is healthymanage subpath stops rewriting the upstream base URL or /speedtest/livewire/update, the login page may load while actions and assets fail2026-04-07