🐇
🐇
🐇
🐇
Speedtest Tracker
Search
⌃K
Comment on page

Frequently Asked Questions

A running list of frequently ask questions and their answers.

Database

Using SQLite
SQLite is supported by Laravel as a database driver but it is no longer the recommended driver for this project. To setup SQLite as your database driver of choice use the directions below.
v0.11.22 dropped SQLite support, to reconnect your existing database you can start on Step 3.
  1. 1.
    Create a volume called speedtest-tracker and attach it to the container.
  2. 2.
    Create a file called database.sqlite, you can do this by running touch database.sqlite in the mounted volume or create it in the mounted directory.
  3. 3.
    Update your environment variables to only include the following for under the DB_ prefix: DB_CONNECTION=sqlite and DB_HOST=/config/database.sqlite.
  4. 4.
    Restart the container.

Docker

I get a warning on container start up that the APP_KEY is missing
As of v0.12.0 the app key is generated on start-up and it is OK to ignore this warning. To set a persisted key follow the steps below
  1. 1.
    Open the CLI of the Speedtest Docker container
  2. 2.
    Run php artisan key:generate --show
  3. 3.
    Add the generated string to your environment variables attached to APP_KEY=generatedstringgoeshere
  4. 4.
    Restart the container

Notifications

Settings

Speedtest server

Q: Why do only some servers have the server name in the list?

By default Ookla's CLI only returns the "closest" 20 servers. If the server you've selected isn't in that list Speedtest Tracker can label it.

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. 1.
    Set APP_DEBUG=true as a environment variable
  2. 2.
    Restart the container
  3. 3.
    Reproduce the error by visiting the page or performing the action that caused the error
  4. 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 repository
  5. 5.
    In the output the line that starts with [timestamp] production.ERROR: is the error the server ran into
  6. 6.
    Once the issue is resolved you can remove the APP_DEBUG environment variable
Previous
Features
Next - Getting Started
Installation
Last modified 1mo ago