Self-host Speedtest Tracker with Levelrail
Runs Ookla speed tests on a schedule and charts your connection's throughput, latency, and jitter over time.
- Authoralexjustesen
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host Speedtest Tracker
-
Pull the images
One image is pulled on your server.
Show images
lscr.io/linuxserver/speedtest-tracker:v1.15.0-ls174
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
1 secret is generated and stored encrypted, 5 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Speedtest Tracker requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Speedtest Tracker. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Speedtest Tracker docs page.
Deploy Speedtest Tracker your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Speedtest Tracker from the CLI
levelrail-cli templates deploy speedtest-tracker --name my-speedtest-tracker Deploy Speedtest Tracker with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/speedtest-tracker/deploy Speedtest Tracker configuration
Speedtest Tracker services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| speedtest-tracker | lscr.io/linuxserver/speedtest-tracker:v1.15.0-ls174 | 80 | speedtest_config -> /config |
Speedtest Tracker environment variables
| Variable | Service | Value |
|---|---|---|
| APP_KEY | speedtest-tracker | Generated at deploy |
| DB_CONNECTION | speedtest-tracker | Preset by the template |
| PGID | speedtest-tracker | Preset by the template |
| PUID | speedtest-tracker | Preset by the template |
| SPEEDTEST_SCHEDULE | speedtest-tracker | Preset by the template |
| TZ | speedtest-tracker | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: speedtest_config -> /config
Speedtest Tracker FAQ
How much memory does Speedtest Tracker need?
The catalog lists about 256 MiB of memory for Speedtest Tracker.
Does Speedtest Tracker run on arm64?
For Speedtest Tracker, an arm64 image is published; amd64 is image published.
What licence is Speedtest Tracker under?
Speedtest Tracker is licensed under MIT, which is permissive, with few conditions on reuse.
Does Speedtest Tracker need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Speedtest Tracker use?
Speedtest Tracker listens on port 80 inside the stack.
Where does Speedtest Tracker keep its data?
In a named volume: speedtest_config mounted at /config.
Can I deploy Speedtest Tracker on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id speedtest-tracker for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/speedtest-tracker:v1.15.0-ls174 is what you deploy there.