Skip to content

Speedtest Tracker ​

Speedtest Tracker runs scheduled Ookla tests from the server to internet test servers and retains performance history. It uses a separate PostgreSQL container. LibreSpeed measures local browser-to-server performance.

Prepare the guest using the host setup guide. Host-specific AI commands and private recovery details are in Speedtest Tracker · Internal Operations.

Access and configuration ​

SettingThis homelab
Host address10.120.40.100
Domainspeedtest.home.rwk.me
Normal accesshttps://speedtest.home.rwk.me
Direct accesshttp://10.120.40.100:8081
Project directory/docker/speedtest-tracker

For another homelab, use your own host address, domain, timezone, paths, and network policy. The addresses above describe internal access; the dashboard does not require a public router port forward.

Create the project ​

Run as a deployment account with Docker access on the prepared guest:

sh
sudo install -d -o "$(id -u)" -g "$(id -g)" -m 0750 /docker/speedtest-tracker
cd /docker/speedtest-tracker

Create compose.yaml with the following configuration. It is a documented example of the repository's pinned deployment, not a second deployment source file:

yaml
name: speedtest-tracker

services:
  speedtest-tracker:
    image: lscr.io/linuxserver/speedtest-tracker:1.15.1
    container_name: speedtest-tracker
    environment:
      PUID: "${PUID}"
      PGID: "${PGID}"
      TZ: UTC
      APP_KEY: "${APP_KEY}"
      APP_URL: https://speedtest.home.rwk.me
      ASSET_URL: https://speedtest.home.rwk.me
      DB_CONNECTION: pgsql
      DB_HOST: postgres
      DB_PORT: "5432"
      DB_DATABASE: speedtest_tracker
      DB_USERNAME: speedtest
      DB_PASSWORD: "${DB_PASSWORD}"
      SPEEDTEST_SCHEDULE: "17 */3 * * *"
      DISPLAY_TIMEZONE: America/Chicago
      PRUNE_RESULTS_OLDER_THAN: "365"
      PUBLIC_DASHBOARD: "false"
      ADMIN_NAME: "${ADMIN_NAME:-Administrator}"
      ADMIN_EMAIL: "${ADMIN_EMAIL}"
      ADMIN_PASSWORD: "${ADMIN_PASSWORD}"
    volumes:
      - ./data:/config
    depends_on:
      postgres:
        condition: service_healthy
    ports:
      - "${SERVER_IP}:8081:80"
    security_opt:
      - no-new-privileges:true
    mem_limit: 1g
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"
    healthcheck:
      test:
        [
          "CMD-SHELL",
          "curl --fail --silent --show-error http://127.0.0.1/api/healthcheck >/dev/null",
        ]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 60s
    restart: unless-stopped

  postgres:
    image: postgres:18.6
    container_name: speedtest-tracker-db
    environment:
      POSTGRES_DB: speedtest_tracker
      POSTGRES_USER: speedtest
      POSTGRES_PASSWORD: "${DB_PASSWORD}"
      POSTGRES_HOST_AUTH_METHOD: scram-sha-256
    volumes:
      - ./postgres:/var/lib/postgresql
    security_opt:
      - no-new-privileges:true
    mem_limit: 512m
    shm_size: 128m
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"
    healthcheck:
      test:
        [
          "CMD",
          "pg_isready",
          "--username=speedtest",
          "--dbname=speedtest_tracker",
        ]
      interval: 10s
      timeout: 5s
      retries: 6
      start_period: 30s
    restart: unless-stopped

Create .env alongside it:

dotenv
SERVER_IP=10.120.40.100
PUID=1000
PGID=1000
APP_KEY=
DB_PASSWORD=
ADMIN_NAME=Administrator
ADMIN_EMAIL=[email protected]
ADMIN_PASSWORD=

Replace blank secrets and example credentials before starting. SERVER_IP must be an address assigned to the Docker host. Preserve existing keys and data when updating an installation. Protect the file with chmod 600 .env and keep it out of Git.

Configure storage and secrets ​

Set PUID and PGID to the deployment account's numeric IDs from id. Create data owned by that account and postgres owned by the PostgreSQL image's UID/GID (999:999 for the pinned image):

sh
mkdir -p data
sudo install -d -o 999 -g 999 -m 0700 postgres

Keep both on local Linux storage. PostgreSQL 18's binding is /var/lib/postgresql; do not blindly reuse an older major version's data layout.

Generate APP_KEY in a private terminal with printf 'base64:'; openssl rand -base64 32 and put the complete value, including the prefix, into .env. See the application encryption guide. Generate independent database and administrator passwords, choose your administrator email, and retain all original values for recovery.

Update APP_URL and ASSET_URL to your dashboard's HTTPS URL. SPEEDTEST_SCHEDULE is a cron expression: 17 */3 * * * runs at minute 17 every three hours. The application and database use UTC, while DISPLAY_TIMEZONE controls the UI display. PRUNE_RESULTS_OLDER_THAN=365 retains 365 days, and PUBLIC_DASHBOARD=false requires authentication. PostgreSQL is internal to the project and has no host port.

Start and verify ​

Run only this Compose project:

sh
cd /docker/speedtest-tracker
docker compose config --quiet
docker compose pull
docker compose up -d --wait --wait-timeout 180
docker compose ps
docker compose logs --tail=100 speedtest-tracker

Keep logs private. Do not rerun the base guest provisioner to install or update one service; it upgrades the host and restarts Docker.

Configure DNS and HTTPS ​

Make speedtest.home.rwk.me resolve to Nginx Proxy Manager (10.120.40.101 in this lab). Add a proxy host:

SettingValue
Domainspeedtest.home.rwk.me
Schemehttp
Backend10.120.40.100
Port8081
WebSocketsNot required
CertificateA certificate covering speedtest.home.rwk.me
Force SSL / HTTP/2Enabled

Use your own domain and certificate on another homelab. Apply a LAN/VPN access list appropriate to your users. A proxy access list does not restrict clients connecting directly to a backend port; use network filtering when the backend must be proxy-only.

Check both paths:

sh
curl --fail --silent --show-error --output /dev/null http://10.120.40.100:8081/api/healthcheck
curl --fail --silent --show-error --output /dev/null https://speedtest.home.rwk.me/api/healthcheck

Add the HTTPS health endpoint to Uptime Kuma, using TLS validation and a suitable check interval. Monitoring on the same VM cannot independently report that VM's outage.

Complete application setup ​

Sign in with the administrator credentials configured for the fresh installation. Run one manual test, confirm it appears in history, then confirm a scheduled result arrives. Compare nearby Ookla servers before choosing a fixed one; changing servers can affect comparisons. Avoid frequent tests that interfere with normal network use.

Maintenance and recovery ​

Back up application configuration and take a consistent PostgreSQL dump; copying a live database directory is not a complete backup procedure. Preserve the application key with protected recovery copies. The lab runner stops the application while dumping the database and archiving /config. PostgreSQL major upgrades require a planned dump/restore migration. Restore a compatible database, configuration, and image together, then verify login and history.

The deployed files remain in the private homelab source directory. Keep these instructions aligned with source changes. Review release notes and preserve a recovery point before updating pinned images. After maintenance, repeat the checks and verify the main application function.