Appearance
LibreSpeed
LibreSpeed tests throughput, latency, and jitter between a browser device and the operations VM. Use Speedtest Tracker for scheduled internet tests instead.
Prepare the guest using the host setup guide. Host-specific AI commands and private recovery details are in LibreSpeed · Internal Operations.
Access and configuration
| Setting | This homelab |
|---|---|
| Host address | 10.120.40.100 |
| Domain | lan-speed.home.rwk.me |
| Normal access | https://lan-speed.home.rwk.me |
| Direct access | http://10.120.40.100:8082 |
| Project directory | /docker/librespeed |
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/librespeed
cd /docker/librespeedCreate 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: librespeed
services:
librespeed:
image: ghcr.io/librespeed/speedtest:6.3.1
container_name: librespeed
environment:
MODE: standalone
TITLE: Home Network Speed Test
TAGLINE: Test throughput between this device and the operations server.
USE_NEW_DESIGN: "true"
TELEMETRY: "false"
DISABLE_IPINFO: "true"
ports:
- "${SERVER_IP}:8082:8080"
security_opt:
- no-new-privileges:true
mem_limit: 512m
logging:
driver: json-file
options:
max-size: "10m"
max-file: "3"
healthcheck:
test:
[
"CMD-SHELL",
"curl --fail --silent --show-error --output /dev/null http://127.0.0.1:8080/",
]
interval: 30s
timeout: 5s
retries: 3
start_period: 20s
restart: unless-stoppedCreate .env alongside it:
dotenv
SERVER_IP=10.120.40.100Replace 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.
MODE=standalone runs a single test point. TITLE and TAGLINE control the page text. Telemetry and external IP lookup are disabled, and no results database is retained. Change the title and tagline for your own network.
Start and verify
Run only this Compose project:
sh
cd /docker/librespeed
docker compose config --quiet
docker compose pull
docker compose up -d --wait --wait-timeout 180
docker compose ps
docker compose logs --tail=100 librespeedKeep 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 lan-speed.home.rwk.me resolve to Nginx Proxy Manager (10.120.40.101 in this lab). Add a proxy host:
| Setting | Value |
|---|---|
| Domain | lan-speed.home.rwk.me |
| Scheme | http |
| Backend | 10.120.40.100 |
| Port | 8082 |
| WebSockets | Not required |
| Certificate | A certificate covering lan-speed.home.rwk.me |
| Force SSL / HTTP/2 | Enabled |
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.
In the proxy host's Advanced configuration, disable buffering and allow test uploads:
nginx
proxy_request_buffering off;
proxy_buffering off;
client_max_body_size 0;
proxy_connect_timeout 120s;
proxy_send_timeout 120s;
proxy_read_timeout 120s;Validate the proxy configuration before reloading it. These settings keep proxy body limits and buffering from distorting upload tests.
Check both paths:
sh
curl --fail --silent --show-error --output /dev/null http://10.120.40.100:8082/
curl --fail --silent --show-error --output /dev/null https://lan-speed.home.rwk.me/Add the HTTPS page to Uptime Kuma, using TLS validation and a suitable check interval. Monitoring on the same VM cannot independently report that VM's outage.
Run a test
Open the HTTPS page from the device you want to measure and start a test. Test a wired client first as a baseline, then compare Wi-Fi clients from the locations you care about. Close competing transfers when comparing runs. The result measures the path to this server, including the proxy and any VPN in use; it is not necessarily your ISP speed.
Maintenance and recovery
This stack is stateless. Preserve its configuration and image pin, then update with scoped Compose pull and up commands. Verify both upload and download after proxy changes. The operations runner deploys reviewed image updates in this lab.
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.