Comma separated list of server IDs that should not be used when running an Ookla Speedtest.
SPEEDTEST_INTERFACE
false
Set the network interface to use for the test. This need to be the network interface available inside the container
eth0
SPEEDTEST_EXTERNAL_IP_URL
false
URL of a service used to get the external WAN IP address.
SPEEDTEST_INTERNET_CHECK_HOSTNAME
false
Hostname used to ping for an active internet connection.
THRESHOLD_ENABLED
false
Enable the thresholds. Note: Only effective during initial setup.
true
THRESHOLD_DOWNLOAD
false
Set the Download Threshold
Note: Only effective during initial setup.
900
THRESHOLD_UPLOAD
false
Set the Upload Threshold
Note: Only effective during initial setup.
900
THRESHOLD_PING
false
Set the Ping Threshold
Note: Only effective during initial setup.
25
PRUNE_RESULTS_OLDER_THAN
false
Set the value to greater than zero to prune stored results. This value should be represented in days, e.g. 7 will purge all results over 7 days old.
7
***
### API
-
Name
Required
Description
Example
API_RATE_LIMIT
false
Number of requests per minute to the API.
- Default: 60
100
+
Name
Required
Description
Example
API_RATE_LIMIT
false
Number of requests per minute to the API.
- Default: 60
100
API_MAX_RESULTS
false
Sets the maximum number of results returned by API.
- Default 500
500
diff --git a/getting-started/installation/README.md b/getting-started/installation/README.md
index 115b677..e37ce3b 100644
--- a/getting-started/installation/README.md
+++ b/getting-started/installation/README.md
@@ -2,6 +2,10 @@
Speedtest Tracker is containerized so you can run it anywhere you run your containers. The image is built by LinuxServer.io, build information can be found [here](https://fleet.linuxserver.io/image?name=linuxserver/speedtest-tracker).
+{% hint style="danger" %}
+Only the installation methods listed below are supported. Any other installation methods, such as bare metal setups or Proxmox LXCs, are **not supported** by this project.
+{% endhint %}
+
Use the install guides listed below to install Speedtest Tracker:
### Docker
diff --git a/getting-started/installation/using-docker-compose.md b/getting-started/installation/using-docker-compose.md
index d5587db..96fdaba 100644
--- a/getting-started/installation/using-docker-compose.md
+++ b/getting-started/installation/using-docker-compose.md
@@ -16,7 +16,7 @@ Docker run commands can be found on the [Using Docker](using-docker.md) page and
{% stepper %}
{% step %}
-#### Generate an Application Key
+**Generate an Application Key**
Run the command below to generate a key, the key is required for [encryption](../../security/encryption.md). Copy this key including the `base64:` prefix and paste it as your `APP_KEY` value.
@@ -26,10 +26,16 @@ echo -n 'base64:'; openssl rand -base64 32;
{% endstep %}
{% step %}
-#### **Setting Up Docker**
+**Setting Up Docker**
SQLite is fine for most installs but you can also use more traditional relational databases like MariaDB, MySQL and Postgres.
+{% hint style="info" %}
+You will need to get your user's `PUID` and `PGID`, you can do this by running `id $user` on the host.
+
+[https://docs.linuxserver.io/general/understanding-puid-and-pgid/](https://docs.linuxserver.io/general/understanding-puid-and-pgid/)
+{% endhint %}
+
{% tabs %}
{% tab title="SQLite" %}
```yaml
@@ -42,9 +48,10 @@ services:
- 8080:80
- 8443:443
environment:
- - PUID=1000
- - PGID=1000
- - APP_KEY=
+ - PUID=
+ - PGID=
+ - APP_KEY= # Required
+ - APP_URL= # Required
- DB_CONNECTION=sqlite
volumes:
- /path/to/data:/config
@@ -62,9 +69,10 @@ services:
- 8080:80
- 8443:443
environment:
- - PUID=1000
- - PGID=1000
- - APP_KEY=
+ - PUID=
+ - PGID=
+ - APP_KEY= # Required
+ - APP_URL= # Required
- DB_CONNECTION=mariadb
- DB_HOST=db
- DB_PORT=3306
@@ -107,9 +115,10 @@ services:
- 8080:80
- 8443:443
environment:
- - PUID=1000
- - PGID=1000
- - APP_KEY=
+ - PUID=
+ - PGID=
+ - APP_KEY= # Required
+ - APP_URL= # Required
- DB_CONNECTION=mysql
- DB_HOST=db
- DB_PORT=3306
@@ -152,9 +161,10 @@ services:
- 8080:80
- 8443:443
environment:
- - PUID=1000
- - PGID=1000
- - APP_KEY=
+ - PUID=
+ - PGID=
+ - APP_KEY= # Required
+ - APP_URL= # Required
- DB_CONNECTION=pgsql
- DB_HOST=db
- DB_PORT=5432
@@ -167,17 +177,18 @@ services:
depends_on:
- db
db:
- image: postgres:17
+ image: postgres:18
restart: always
environment:
- POSTGRES_DB=speedtest_tracker
- POSTGRES_USER=speedtest_tracker
- POSTGRES_PASSWORD=password
+ - PGDATA=/var/lib/postgresql/data/
volumes:
- speedtest-db:/var/lib/postgresql/data
healthcheck:
- test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER} -d ${POSTGRES_DB}"]
- interval: 5s
+ test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER:-postgres}"]
+ interval: 10s
retries: 5
timeout: 5s
volumes:
@@ -192,13 +203,13 @@ If you would like to provide your own SSL keys, they must be named `cert.crt` (f
{% endstep %}
{% step %}
-#### **Environment Variables**
+**Environment Variables**
-In order for the application to run smoothly, some environment variables need to be set. Check out the [Environment Variables](../environment-variables.md) section. Make sure all r**equired** variables are configured.
+In order for the application to run smoothly, some environment variables need to be set. Check out the [Environment Variables](../environment-variables.md) section. Make sure all **required** variables are configured.
{% endstep %}
{% step %}
-#### **Configuration Variables (Optional)**
+**Configuration Variables (Optional)**
You can set configuration variables to have automatic speedtest on an schedule. Check out the [Environment Variables](../environment-variables.md#speedtest) section on how to set the variables. Also see the [FAQ](../../help/faqs.md#speedtest) for tips effectively scheduling tests.
@@ -208,13 +219,13 @@ Complete overview of the Environment Variables for custom configuration can be f
{% endstep %}
{% step %}
-#### **Start the Container**
+**Start the Container**
You can now start the container accordingly the platform you are on.
{% endstep %}
{% step %}
-#### **First Login**
+**First Login**
During the start the container there is a default username and password created. Use the [default login](../../security/authentication.md#default-user-account) credentials to login to the application. You can [change the default user](../../security/authentication.md#change-account-details) after logging in.
{% endstep %}
diff --git a/getting-started/installation/using-docker.md b/getting-started/installation/using-docker.md
index 63037ca..b5ff34a 100644
--- a/getting-started/installation/using-docker.md
+++ b/getting-started/installation/using-docker.md
@@ -16,7 +16,7 @@ Docker run commands assume you already have a database installed and configured.
{% stepper %}
{% step %}
-#### Generate an Application Key
+**Generate an Application Key**
Run the command below to generate a key, the key is required for [encryption](../../security/encryption.md). Copy this key including the `base64:` prefix and paste it as your `APP_KEY` value.
@@ -26,24 +26,30 @@ echo -n 'base64:'; openssl rand -base64 32;
{% endstep %}
{% step %}
-#### **Setting Up Docker**
+**Setting Up Docker**
SQLite is fine for most installs but you can also use more traditional relational databases like MariaDB, MySQL and Postgres.
+{% hint style="info" %}
+You will need to get your user's `PUID` and `PGID`, you can do this by running `id $user` on the host.
+
+[https://docs.linuxserver.io/general/understanding-puid-and-pgid/](https://docs.linuxserver.io/general/understanding-puid-and-pgid/)
+{% endhint %}
+
{% tabs %}
{% tab title="SQLite" %}
-```docker
-docker run -d --name speedtest-tracker --restart unless-stopped \
+
{% endtab %}
{% tab title="MariaDB" %}
@@ -51,9 +57,10 @@ docker run -d --name speedtest-tracker --restart unless-stopped \
docker run -d --name speedtest-tracker --restart unless-stopped \
-p 8080:80 \
-p 8443:443 \
- -e PUID=1000 \
- -e PGID=1000 \
- -E APP_KEY= \
+ -e PUID= \
+ -e PGID= \
+ -e APP_KEY= \
+ -e APP_URL= \
-e DB_CONNECTION=mariadb \
-e DB_HOST= \
-e DB_PORT=3306 \
@@ -71,9 +78,10 @@ docker run -d --name speedtest-tracker --restart unless-stopped \
docker run -d --name speedtest-tracker --restart unless-stopped \
-p 8080:80 \
-p 8443:443 \
- -e PUID=1000 \
- -e PGID=1000 \
- -e APP_KEY= \
+ -e PUID= \
+ -e PGID= \
+ -e APP_KEY= \
+ -e APP_URL= \
-e DB_CONNECTION=mysql \
-e DB_HOST= \
-e DB_PORT=3306 \
@@ -93,7 +101,8 @@ docker run -d --name speedtest-tracker --restart unless-stopped \
-p 8443:443 \
-e PUID=1000 \
-e PGID=1000 \
- -e APP_KEY=
+ -e APP_KEY= \
+ -e APP_URL= \
-e DB_CONNECTION=pgsql \
-e DB_HOST= \
-e DB_PORT=5432 \
@@ -113,13 +122,13 @@ If you would like to provide your own SSL keys, they must be named `cert.crt` (f
{% endstep %}
{% step %}
-#### **Environment Variables**
+**Environment Variables**
-In order for the application to run smoothly, some environment variables need to be set. Check out the [Environment Variables](../environment-variables.md) section. Make sure all r**equired** variables are configured.
+In order for the application to run smoothly, some environment variables need to be set. Check out the [Environment Variables](../environment-variables.md) section. Make sure all **required** variables are configured.
{% endstep %}
{% step %}
-#### **Configuration Variables (Optional)**
+**Configuration Variables (Optional)**
You can set configuration variables to have automatic speedtest on an schedule. Check out the [Environment Variables](../environment-variables.md#speedtest) section on how to set the variables. Also see the [FAQ](../../help/faqs.md#speedtest) for tips effectively scheduling tests.
@@ -129,14 +138,18 @@ Complete overview of the Environment Variables for custom configuration can be f
{% endstep %}
{% step %}
-#### **Start the Container**
+**Start the Container**
You can now start the container accordingly the platform you are on.
{% endstep %}
{% step %}
-#### **First Login**
+**First Login**
During the start the container there is a default username and password created. Use the [default login](../../security/authentication.md#default-user-account) credentials to login to the application. You can [change the default user](../../security/authentication.md#change-account-details) after logging in.
{% endstep %}
{% endstepper %}
+
+[^1]: Generate with: `echo -n 'base64:'; openssl rand -base64 32`
+
+[^2]: The URL where you'll access the app (e.g., `http://localhost:8080`)
diff --git a/getting-started/installation/using-qnap.md b/getting-started/installation/using-qnap.md
index a63287c..4e1f36b 100644
--- a/getting-started/installation/using-qnap.md
+++ b/getting-started/installation/using-qnap.md
@@ -30,8 +30,8 @@ services:
- 8080:80
- 8443:443
environment:
- - PUID=1000
- - PGID=1000
+ - PUID=
+ - PGID=
- DB_CONNECTION=mariadb
- DB_HOST=db
- DB_PORT=3306
diff --git a/getting-started/installation/using-synology.md b/getting-started/installation/using-synology.md
index 84dcbec..c08d71a 100644
--- a/getting-started/installation/using-synology.md
+++ b/getting-started/installation/using-synology.md
@@ -12,30 +12,55 @@ The following directions are for the old "Docker" application, if you're using "
### Install on a Synology NAS
-Open the Docker interface of your Synology Device, search for `ajustesen/speedtest-tracker` in the Registry and download it.
+{% hint style="warning" %}
+This guide assumes you know how to use the old "Docker" application.
+{% endhint %}
+
+{% stepper %}
+{% step %}
+#### Download Image
+
+Open the Docker interface of your Synology Device, search for `linuxserver/speedtest-tracker` in the Registry and download it.
+{% endstep %}
-
+{% step %}
+#### Create Directory
Create a local directory (i.e. `/volume1/docker/speedtest-tracker`) which later can be mapped to the docker container.
+{% endstep %}
+
+{% step %}
+#### Start Image
Launch the image once the download is completed.
+{% endstep %}
-
+{% step %}
+#### Map Ports
Map the ports to available ports.
-
+| Local Port | Container Port |
+| ---------- | -------------- |
+| 8443 | 443 |
+| 8080 | 80 |
{% hint style="info" %}
Make sure the ports you choose are not used by any other application or DSM service on your device and remember to adjust the Synology Firewall settings accordingly.
{% endhint %}
+{% endstep %}
+
+{% step %}
+#### Map Directory
Map the directory you created earlier to the mount path `/config`.
+{% endstep %}
-
+{% step %}
+#### Finish
Review your settings and click "done".
-
-
You can now access Speedtest-Tracker via `http://YOUR_IP_ADDRESS:8080` or `https://YOUR_IP_ADDRESS:8443`.
+{% endstep %}
+{% endstepper %}
diff --git a/help/error-messages.md b/help/error-messages.md
index 09d958e..c16f48d 100644
--- a/help/error-messages.md
+++ b/help/error-messages.md
@@ -1,18 +1,82 @@
# Error Messages
-### Speedtest errors
+### Troubleshooting
+
+For all below errors there will be more information provided in the container logs. You can check the logs for more details by checking the container logs by running `docker logs speedtest-tracker`.
+
+or any other equivalent command for your setup.
+
+
+
+Enable Debugging
+
+By default `APP_DEBUG` is set to `false` in production to prevent verbose error outputs. To debug the issue follow the steps below.
+
+1. Set `APP_DEBUG=true` as a environment variable
+2. Restart the container
+3. Reproduce the error by visiting the page or performing the action that caused the error
+4. View the output in the UI or in the logs to help resolve the issue, if you can not resolve it open an issue in the [GitHub](https://github.com/alexjustesen/speedtest-tracker/issues) repository
+5. In the output the line that starts with `[timestamp] production.ERROR:` is the error the server ran into
+6. Once the issue is resolved you can remove the `APP_DEBUG` environment variable
+
+
+
+### Application
+
+
+
+I'm getting a 500 | SERVER ERROR error
+
+The `500 | SERVER ERROR` is caused by either a bug or a misconfiguration. You must e[nable debugging](error-messages.md#enable-debugging) to determine the exact cause of the error.
+
+
+
+
+
+Unsupported cipher or incorrect key length. Supported ciphers are: aes-128-cbc, aes-256-cbc, aes-128-gcm,aes-256-gcm.
+
+This error is shown when the `APP_KEY` is not set or not set correctly. Make suer you set the `APP_KEY` as described in the [installation steps](../getting-started/installation/using-docker-compose.md#install-with-docker-compose).
+
+
+
+### Speedtest Process
+
+
+
+Failed to connected to hostname
+
+When a speedtest is being [processed](../other/speedtest-process.md) Speedtest Tracker will make a ICMP ping to [icanhazip.com](http://icanhazip.com) to check if there is an internet connection before starting the Speedtest
+
+**Possible reasons**:
+
+* There is a docker network problem or no internet connection.
+* Some DNS blocks lists will block this domain, if you're getting errors and your server has access to the internet you'll need to add this to your allow lists.
+* _Most_ Docker setups can send ICMP requests without needed elevated privileges on the host or in the container. That being said if your Docker user doesn't run with elevated permissions or doesn't belong to the Docker group you can get a failure on this step. To allow the user to send ICMP requests you need to add the permission to the container.
+
+**Configuration options**
+
+* Use available [Environment Variables](../getting-started/environment-variables.md#speed-tests) to change the endpoint to your liking
+
+
-Tests are saying there is no internet while there is.
+Failed to fetch external IP address
-When a speedtest is being processed Speedtest Tracker will make a call to [http://icanhazip.com](http://icanhazip.com) to get your external IP address. This is done to determine if your server has access to the internet and to check if your external IP address (WAN IP) should be skipped.
+When the `SPEEDTEST_SKIP_IPS` environment variable is Speedtest Tracker will make a call to [http://icanhazip.com](http://icanhazip.com/) to get your external IP address. This is done check if your external IP address (WAN IP) should be skipped.
-Some DNS blocks lists will block this domain, if you're getting errors and your server has access to the internet you'll need to add this to your allow lists.
+**Possible reasons**:
+
+* There is a docker network problem or no internet connection.
+* Some DNS blocks lists will block this domain, if you're getting errors and your server has access to the internet you'll need to add this to your allow lists.
+
+**Configuration options**
+
+* Use available [Environment Variables](../getting-started/environment-variables.md#speed-tests) to change the endpoint to your liking. :warning: Whatever service you choose needs to only return an IP address in the body of the response for this to work.
-### Ookla errors
+### Ookla Related
@@ -37,3 +101,29 @@ This usually means the defined server is no longer available. Remove it from you
Not 100% sure what causes this exception yet but it's likely when the CLI can't locate a local server. You should specify a list of servers to see if that addresses the issue.
+
+
+
+Unable to retrieve Ookla servers, check internet connection and see logs.
+
+This errors is shown when we try to retrieve the Ookla server list when selecting an server wehn running an manual speedtest. We get the list from: [https://www.speedtest.net/api/js/servers](https://www.speedtest.net/api/js/servers).
+
+This error is useually caused by a docker network problem or no internet connection. You can check the [container logs](error-messages.md#troubleshooting) for more details.
+
+
+
+### InfluxDB
+
+
+
+Failed to write to InfluxDB
+
+When Speedtest Tracker fails to write data to InfluxDB this error is shown. The [container logs](error-messages.md#troubleshooting) will show more details on why it failed.
+
+**Possible reasons:**
+
+* Connectivity problem to influxdb
+* Problem with authentication
+* Specified bucket does not exist in InfluxDB
+
+
diff --git a/help/faqs.md b/help/faqs.md
index 32aa0ea..91c3322 100644
--- a/help/faqs.md
+++ b/help/faqs.md
@@ -25,17 +25,16 @@ You need a `APP_KEY` for the encryption. See the [installation docs](../getting-
-### Time zones
-
-How do I set the display and schedule time zone?
+I'm getting duplicate message via Apprise
-1. Set `DISPLAY_TIMEZONE` environment variables to your local timezone.
-2. Restart the container
+By default when sending an notifications via Apprise we wait up to 30 seconds for Apprise to respond back with any message. Incase this 30 seconds is exceeded, we will retry 3 times. In case of any very slow Apprise processing this might cause duplicated notifications. Please check the [logs](error-messages.md#troubleshooting) to see the the timeout happend
+### Time zones
+
My display timestamps or scheduled tests aren't correct.
@@ -55,20 +54,3 @@ Once set restart the container.
Starting your cron schedule at an off-peak minute can help reduce network congestion or avoid overloading a speed test server. This [comment](https://github.com/alexjustesen/speedtest-tracker/issues/552#issuecomment-2028532010) on this issue can help you get the formatting right.
-
-### Other
-
-
-
-I'm getting a 500 | SERVER ERROR error
-
-By default `APP_DEBUG` is set to `false` in production to prevent verbose error outputs. To debug the issue follow the steps below.
-
-1. Set `APP_DEBUG=true` as a environment variable
-2. Restart the container
-3. Reproduce the error by visiting the page or performing the action that caused the error
-4. View the output in the UI or in the logs to help resolve the issue, if you can not resolve it open an issue in the [GitHub](https://github.com/alexjustesen/speedtest-tracker/issues) repository
-5. In the output the line that starts with `[timestamp] production.ERROR:` is the error the server ran into
-6. Once the issue is resolved you can remove the `APP_DEBUG` environment variable
-
-
diff --git a/other/caching.md b/other/caching.md
deleted file mode 100644
index 9dcee43..0000000
--- a/other/caching.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-description: >-
- Speedtest Tracker supports multiple cache drivers, use the docs below to setup
- your preferred handler.
----
-
-# Caching
-
-## Drivers
-
-You can change the default `database` cache by passing `CACHE_STORE` as an environment variable. Supported stores can be found in the [Laravel docs](https://laravel.com/docs/master/cache).
diff --git a/other/commands.md b/other/commands.md
index 7963490..6f01af5 100644
--- a/other/commands.md
+++ b/other/commands.md
@@ -20,13 +20,10 @@ Core commands exist at the framework level and might be extended to provide addi
Application commands are built to extend Speedtest Tracker's functionality from the CLI.
-
Command
Description
app:install
Installs a fresh version of Speedtest Tracker. If you have an existing install this will delete all data.
app:ookla-list-servers
Get a list of local Ookla speedtest servers.
app:user-change-role
Change the role for a user.
app:user-reset-password
Change the password for a user.
+
Command
Description
app:ookla-list-servers
Get a list of local Ookla speedtest servers.
app:user-change-role
Change the role for a user.
app:user-reset-password
Change the password for a user.
### Maintenance commands
Maintenance commands help fix issues that might crop up over time.
Command
Description
app:result-fix-statuses
Reviews the data payload of each result and corrects the status attribute.
-
-
-
diff --git a/other/community-projects.md b/other/community-projects.md
index 8a63fe6..a6f5745 100644
--- a/other/community-projects.md
+++ b/other/community-projects.md
@@ -2,12 +2,13 @@
description: >-
This page lists community projects that use SpeedTest Tracker as a base for
their own projects. If you have a project that you would like to share, please
- submit a pull request to add it to this list
+ submit a pull request to add it to this list.
---
# Community Projects
## Projects
-* [SpeedtestTrackerBot](https://github.com/josephistired/SpeedtestTrackerBot) - A locally-run Discord bot that integrates with the Speedtest Tracker API to provide real-time network speed test results. Easily deployable via Docker, it supports multi-architecture environments and offers commands for health checks and accessing the latest speedtest results.
+* [SpeedtestTrackerBot](https://github.com/josephistired/SpeedtestTrackerBot) — SpeedtestTrackerBot is a lightweight Discord bot that integrates with the Speedtest Tracker API to provide real-time network performance data via slash commands like `/latest`, `/stats`, `/result`, and `/run`. It's easy to set up with Docker or systemd.
* Stream Deck - Use the API to show the most recent result on your Stream Deck. Shoutout to [MartynKeigher](https://github.com/MartynKeigher) on GitHub for [providing](https://github.com/alexjustesen/speedtest-tracker/issues/1191) these instructions.
+* [Speedtest Tracker App (iOS)](https://apps.apple.com/us/app/speedtest-tracker-app/id6755368150) - Speedtest Tracker App is a native iOS client for Speedtest Tracker, which integrates with its API to allow you to perform actions or see stats straight from your phone.
diff --git a/other/proxies/cloudflare-tunnel-zero-trust.md b/other/proxies/cloudflare-tunnel-zero-trust.md
index ddcd72f..b4d5aef 100644
--- a/other/proxies/cloudflare-tunnel-zero-trust.md
+++ b/other/proxies/cloudflare-tunnel-zero-trust.md
@@ -1,14 +1,15 @@
# Cloudflare Tunnel (Zero Trust)
-[Cloudflare tunnel ](https://www.cloudflare.com/nl-nl/products/tunnel/)can be used as a Reverse Proxy in front of Speedtest Tracker when you want to expose the Dashboard publicly without exposing your IP Address and with a trusted certificate,You will need at add the `APP_URL` envoirment.
+A [Cloudflare tunnel ](https://www.cloudflare.com/nl-nl/products/tunnel/)can be used as a reverse proxy in front of Speedtest Tracker when you want to expose the application publicly without exposing your IP address.
### Cloudflare Tunnel Configuration
-* Go to the **Networks** -> **Tunnels** page.
-* For the tunnel you want to add the Speedtest Tracker to. Click on **Edit**
-* Go to **Public Hostname**
-* Click on **Add a public hostname**
-* Fill in the fields the following field
+* Update your `APP_URL` to the public URL you are going to use and restart the service.
+* In the Cloudflare panel go to **Zero Trust** -> **Networks** -> **Tunnels** page.
+* For the tunnel you want to add the Speedtest Tracker to click on **Edit** or add a new tunnel.
+* Go to **Public Hostname.**
+* Click on **Add a public hostname.**
+* Fill in the following fields.
* **Subdomain:** The subdomain you want to access the Speedtest Tracker on.
* **Domain:** The domain you want to access the Speedtest Tracker on.
* **Type:** Connection type to the Speedtest Tracker (http/https)
diff --git a/other/proxies/nginx.md b/other/proxies/nginx.md
new file mode 100644
index 0000000..15d8694
--- /dev/null
+++ b/other/proxies/nginx.md
@@ -0,0 +1,74 @@
+# Nginx
+
+[Nginx](https://nginx.org) can be used as a Reverse Proxy in front of Speedtest
+Tracker to expose the Dashboard publicly with a trusted certificate.
+
+First, you will need to add the `APP_URL` and `ASSET_URL` environment variables
+to your `docker-compose.yml`.
+
+```yaml
+services:
+ speedtest-tracker:
+ container_name: speedtest-tracker
+ environment:
+ - PUID=1000
+ - PGID=1000
+ - APP_KEY=
+ - DB_CONNECTION=sqlite
+ - SPEEDTEST_SCHEDULE=
+ - SPEEDTEST_SERVERS=
+ - PRUNE_RESULTS_OLDER_THAN=
+ - CHART_DATETIME_FORMAT=
+ - DATETIME_FORMAT=
+ - APP_TIMEZONE=
+ # Change both below to the desired domain
+ - APP_URL=https://speedtest.yourdomain.com
+ - ASSET_URL=https://speedtest.yourdomain.com
+ volumes:
+ - /path/to/data:/config
+ - /path/to-custom-ssl-keys:/config/keys
+ image: lscr.io/linuxserver/speedtest-tracker:latest
+ restart: unless-stopped
+```
+
+Next, you will need to configure nginx to proxy to the Speedtest Tracker app.
+
+{% hint style="info" %}
+Depending on how you generate your SSL certificates and how you configure your
+Docker network, you may need to adjust the `ssl_` and `proxy_pass` values.
+{% endhint %}
+
+```nginx
+server {
+ listen 80;
+ server_name speedtest.yourdomain.com;
+ return 301 https://$host$request_uri;
+}
+
+server {
+ listen 443 ssl;
+ server_name speedtest.yourdomain.com;
+
+ ssl_certificate /etc/letsencrypt/live/speedtest.yourdomain.com/fullchain.pem;
+ ssl_certificate_key /etc/letsencrypt/live/speedtest.yourdomain.com/privkey.pem;
+
+ ssl_protocols TLSv1.2;
+ ssl_ciphers
+'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';
+ ssl_prefer_server_ciphers on;
+ ssl_session_cache shared:SSL:10m;
+ ssl_session_timeout 10m;
+ ssl_dhparam /etc/ssl/certs/dhparam.pem;
+
+ add_header Strict-Transport-Security "max-age=31536000;includeSubdomains";
+
+ location / {
+ proxy_set_header X-Forwarded-Host $host;
+ proxy_set_header X-Forwarded-Server $host;
+ proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+ proxy_set_header X-Forwarded-Proto $scheme;
+
+ proxy_pass http://speedtest-container-host:80;
+ }
+}
+```
diff --git a/other/proxies/traefik.md b/other/proxies/traefik.md
index 713fa0e..16db0ee 100644
--- a/other/proxies/traefik.md
+++ b/other/proxies/traefik.md
@@ -1,6 +1,6 @@
# Traefik
-[Traefik](https://traefik.io) can be used as a Reverse Proxy in front of Speedtest Tracker when you want to expose the Dashboard publicly with a trusted certificate. You will need at add the `APP_URL` envoirment and needed labels to the docker compose have Traefik apply the certificate and routing.
+[Traefik](https://traefik.io) can be used as a Reverse Proxy in front of Speedtest Tracker when you want to expose the Dashboard publicly with a trusted certificate. You will need at add the `APP_URL` environment and needed labels to the docker compose have Traefik apply the certificate and routing.
Docker-Compose:
diff --git a/other/speedtest-process.md b/other/speedtest-process.md
index ed20d23..dfa6d87 100644
--- a/other/speedtest-process.md
+++ b/other/speedtest-process.md
@@ -4,33 +4,31 @@ Speedtest Tracker uses the [Official Ookla CLI](https://www.speedtest.net/apps/c
{% stepper %}
{% step %}
-
-#### Waiting
+**Waiting**
The speedtest run request was created but has not been started.
{% endstep %}
{% step %}
-
-#### Started
+**Started**
The speedtest process has been started by a queue worker.
{% endstep %}
{% step %}
-#### Checking
+**Checking**
-The application checks for an internet connection by calling `https://icanhazip.com`
+The application checks for an internet connection by calling `https://icanhazip.com` .
{% endstep %}
{% step %}
-#### Skipped \[Optional]
+**Skipped \[Optional]**
If you have the `SPEEDTEST_SKIP_IPS` the test will be marked as skipped as the IP returning during `Checking` matches your defined IP.
{% endstep %}
{% step %}
-#### Running
+**Running**
The application runs the speedtest by simply running the speedtest command. This command runs the speedtest like another other speedtest and returns the result in json format so the application an easily process it.
@@ -46,19 +44,19 @@ speedtest -accept-license --accept-gdpr --format=json --server-id=YOURSERVERID
{% endstep %}
{% step %}
-#### Failed
+**Failed**
If for various reasons the Ookla CLI returns an error, because the defined server was offline for example the tests is marked as failed. As well when the `Checking` stage fails when there is no internet.
{% endstep %}
{% step %}
-#### Benchmarking
+**Benchmarking**
When you have thresholds set this step will evaluate the results against the threshold to determine if the test was healthy or not.
{% endstep %}
{% step %}
-#### Completed
+**Completed**
This is the end stage of the process when every step is completed the test is marked as such.
{% endstep %}
diff --git a/security/authentication.md b/security/authentication.md
index c93b56e..27ef9a8 100644
--- a/security/authentication.md
+++ b/security/authentication.md
@@ -16,7 +16,7 @@ During the first start of the application a default admin account is created for
#### Login Details
-You can update the login details of your account through the profile page. Every user can update these details for there own account.
+You can update the login details of your account through the profile page. Every user can update these details for their own account.
* In the top right corner click on the user logo next to the bell icon.
* Click on Profile
diff --git a/security/authorization.md b/security/authorization.md
index ecbde04..d92192a 100644
--- a/security/authorization.md
+++ b/security/authorization.md
@@ -23,7 +23,7 @@
### Other
-
User
Admin
Trigger a manual Speedtest
false
true
+
User
Admin
Manage API tokens
false
true
Trigger a manual Speedtest
true
true
***
diff --git a/settings/data-platforms/influxdb2.md b/settings/data-platforms/influxdb2.md
index a983172..5438054 100644
--- a/settings/data-platforms/influxdb2.md
+++ b/settings/data-platforms/influxdb2.md
@@ -14,7 +14,7 @@ If you have a history of results, you can use the `Export current results` featu
### Grafana Dashboard
-You can use this community made Grafana Dashbaord to visualize your data.
+You can use this community made Grafana Dashboard to visualize your data.
{% embed url="https://github.com/masterwishx/Speedtest-Tracker-v2-InfluxDBv2" %}
diff --git a/settings/data-platforms/prometheus.md b/settings/data-platforms/prometheus.md
new file mode 100644
index 0000000..84be1cf
--- /dev/null
+++ b/settings/data-platforms/prometheus.md
@@ -0,0 +1,35 @@
+# Prometheus
+
+After each test, Speedtest Tracker exposes the metrics for Prometheus to scrape. For long term storage or custom visualizations.
+
+### Allowed IPs
+
+You can configure the Prometheus endpoint so it’s only accessible from specific IP addresses or networks. This can include single IPs or entire CIDR ranges.
+
+
+
+### Grafana Dashboard
+
+You can use this community made Grafana Dashboard to visualize your data.
+
+{% embed url="https://github.com/CrazyWolf13/Speedtest-Tracker-Prometheus" %}
+
+### Data pattern
+
+Speedtest Tracker exports data in two categories: labels and metrics. Labels are used for filtering, while metrics are used for displaying data.
+
+
Name
app_name
label
isp
label
server_id
label
server_name
label
server_country
label
server_location
label
healthy
label
status
label
scheduled
label
download_bytes
Metric
upload_bytes
Metric
ping
Metric
download_bits
Metric
upload_bits
Metric
download_jitter
Metric
upload_jitter
Metric
ping_jitter
Metric
download_latency_avg
Metric
download_latency_high
Metric
download_latency_low
Metric
upload_latency_avg
Metric
upload_latency_high
Metric
upload_latency_low
Metric
packet_loss
Metric
+
+### Prometheus Scrape Config
+
+Below is an example Prometheus scrape configuration:
+
+```yaml
+scrape_configs:
+ - job_name: 'speedtest-tracker'
+ scrape_interval: 60s # Adjust to your set schedule
+ scrape_timeout: 10s
+ metrics_path: /prometheus
+ static_configs:
+ - targets: ['speedtest-tracker.local']
+```
diff --git a/settings/notifications/apprise.md b/settings/notifications/apprise.md
index f5d7c98..5dfd401 100644
--- a/settings/notifications/apprise.md
+++ b/settings/notifications/apprise.md
@@ -1,22 +1,33 @@
----
-hidden: true
----
-
# Apprise
-Speedtest Tracker uses [Apprise](https://github.com/caronc/apprise-api) to send notifications to a wide variety of messaging services with a simple, unified configuration.
+Apprise provides a unified notification channel that lets you send alerts to numerous services—like Discord, Pushover, and Ntfy as well as many additional platforms
+
+### Why Apprise
+
+Apprise allows the application to sent notifications to a wide variety of services. It let us focus on features instead of maintaining X number of notification channels. Essentially helping us cut down on maintenance/feature requests.
-Apprise allows you to easily deliver alerts to popular platforms such as Discord, Slack, Telegram and many more.
+### Apprise Server
-{% hint style="warning" %}
-To use Apprise notifications, you must deploy the [Apprise API](https://github.com/caronc/apprise-api) service. This is out of scope of this documentation.
+{% hint style="info" %}
+We don't offer support on setting up Apprise, incase of any problems with the Apprise Container please reach out to the Apprise team.
{% endhint %}
-
Apprise Settings
+To use Apprise, you’ll need to set up your own Apprise instance. This container isn’t created automatically, so make sure to include it in your deployment. See the Apprise [Github Repo](https://github.com/caronc/apprise-api) for the setup instructions. On the notification page you will need to define the location of your Apprise instance. Make sure this instance is reachable for the Speedtest Tracker.
-
Name
Description
URL
This is the URL of your running Apprise API instance
Service URL
This is the URL of the service that will receive the notification. You can find a full list of supported services and how to format their URLs in the Apprise notification services documentation.
+### Notification Channels
-### Triggers
+Notification channels are the formatted URLs used by Apprise to send notifications to various services. Refer to the [Apprise documentation](https://github.com/caronc/apprise?tab=readme-ov-file#supported-notifications) for a full list of supported channels and their required formats. You can add as many different channels as you wish. The notifications will be sent to all of them.
+
+### Tips and Tricks
-
Name
Description
On completed speedtest
On each successful speedtest a notification will be send to the application.
On absolute threshold failure
On any absolute threshold failure a notification will be send to the application.
+#### Format
+
+By default the format used for message is `markdown` This allows us to do some formatting on the message like bold text etc.
+
+#### Preview Images
+
+By default Apprise does not allow preview images for URLs. This is an default setting on the Apprise instance. Depending on the service used you can override this settings in the notification channel URL. Check the Apprise documentation to see if your service support this and how to set it.
+
+### Triggers
+
Name
Description
on every scheduled speedtest run
On each successful scheduled speedtest a notification will be send to the application.
on threshold failures for scheduled speedtests
On any absolute threshold failure for scheduled speedtest a notification will be send to the application.
diff --git a/settings/notifications/database.md b/settings/notifications/database.md
index a253512..e4f0348 100644
--- a/settings/notifications/database.md
+++ b/settings/notifications/database.md
@@ -6,4 +6,4 @@ Notifications sent to the database channel will show up under the 🔔 icon in t
### Triggers
-
Name
Description
On completed speedtest
On each successful speedtest a notification will be send to the application.
On absolute threshold failure
On any absolute threshold failure a notification will be send to the application.
+
Name
Description
on every scheduled speedtest run
On each successful scheduled speedtest a notification will be send to the application.
on threshold failures for scheduled speedtests
On any absolute threshold failure for scheduled speedtest a notification will be send to the application.
diff --git a/settings/notifications/mail.md b/settings/notifications/mail.md
index 923d9f1..a8e1bbe 100644
--- a/settings/notifications/mail.md
+++ b/settings/notifications/mail.md
@@ -16,40 +16,42 @@ Make sure these are not set in both your `.env` file or your `docker-compose.yml
```
MAIL_MAILER=smtp
-MAIL_HOST=mailhog
-MAIL_PORT=1025
-MAIL_USERNAME=null
-MAIL_PASSWORD=null
-MAIL_FROM_ADDRESS="hello@example.com"
-MAIL_FROM_NAME="Speedtest Tracker"
-MAIL_SCHEME=null
+MAIL_HOST=
+MAIL_PORT=
+MAIL_USERNAME=
+MAIL_PASSWORD=
+MAIL_FROM_ADDRESS=
+MAIL_FROM_NAME=
```
-**GMAIL example:**
+{% hint style="info" %}
+`MAIL_SCHEME` is optional, only use it if you need to define `smtp` or `smtps` otherwise Laravel will determine the scheme based on the port provided.
+{% endhint %}
+
+***
+
+### Examples
-Steps for creating an app password.
+#### Gmail
-* Go to your [Google Account](https://myaccount.google.com) .
-* Select Security.
-* Under "How you sign in to Google," choose 2-Step Verification.
-* Click on App passwords.
-* Enter a name and generate a password.
-* Remember to copy the password before closing; otherwise, you'll need to create another one.
+1. Go to [https://myaccount.google.com/](https://myaccount.google.com/) and click on the "Security" tab.
+2. Under the "How you sign in to Google" section, click on "2-Step Verification".
+3. Click on "App passwords".
+4. Enter a name for your app password and click "Create". Use this password for the `MAIL_PASSWORD` env variable in the example configuration below.
```
MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=465
-MAIL_USERNAME=username@gmail.com
+MAIL_USERNAME="username@gmail.com"
MAIL_PASSWORD="password"
-MAIL_FROM_ADDRESS=username@gmail.com
+MAIL_FROM_ADDRESS="username@gmail.com"
MAIL_FROM_NAME="Speedtest Tracker"
-MAIL_SCHEME=tls
```
### Triggers
-
Name
Description
On completed speedtest
On each successful speedtest a notification will be send to the application.
On absolute threshold failure
On any absolute threshold failure a notification will be send to the application.
+
Name
Description
on every scheduled speedtest run
On each successful scheduled speedtest a notification will be send to the application.
on threshold failures for scheduled speedtests
On any absolute threshold failure for scheduled speedtest a notification will be send to the application.