search

alexjustesen / speedtest-tracker

Speedtest Tracker is a self-hosted internet performance tracking application that runs speedtest checks against Ookla's Speedtest service.
https://speedtest-tracker.dev/
MIT License
2.68k stars 99 forks source link

Configuration - Could not retrieve or read configuration (ConfigurationError) #1636

Closed rmcgirr83 closed 1 month ago

rmcgirr83 commented 1 month ago

Describe the bug Everytime I start a speedtest it is stalled on "started". Looked in the laravel logs and there were some errors, notably server_id doesn't exist in db and it was trying to log this error message Configuration - Could not retrieve or read configuration (ConfigurationError). No speedtest is completing

Expected behavior Show a speedtest result. Prior to using latest from lscr.io everything was working fine

Environment (please complete the following information): Using docker in synology NAS here is compose file

services: speedtest: container_name: speedtest image: lscr.io/linuxserver/speedtest-tracker:latest ports:

rmcgirr83 commented 1 month ago

Clicking on view for the test and it doesn't appear anything is being populated Capture

alexjustesen commented 1 month ago

TL;DR: the specified speedtest server is unavailable, choose a different one.

https://docs.speedtest-tracker.dev/help/error-messages#configuration-could-not-retrieve-or-read-configuration-configurationerror

rmcgirr83 commented 1 month ago

According to this, that server is listed https://c.speedtest.net/speedtest-servers-static.php Capture

rmcgirr83 commented 1 month ago

Additionally My new yml file

services: speedtest: container_name: speedtest image: lscr.io/linuxserver/speedtest-tracker:latest ports:

  • 8999:80 volumes:
  • /volume1/docker/speedtest:/config environment:
  • PGID=100
  • PUID=1032
  • APP_TIMEZONE=America/New_York
  • DISPLAY_TIMEZONE=America/New_York
  • DB_CONNECTION=sqlite
  • APP_KEY=redacted
  • SPEEDTEST_SERVERS=56485
  • SPEEDTEST_SCHEDULE=0 restart: unless-stopped

and that server is accurate Untitled

laravel error logs laravel.log

and I'm still stuck at "started" for the past 10 minutes

alexjustesen commented 1 month ago

I'm close to you (CT also) so I'll give 18687 a shot later today.

rmcgirr83 commented 1 month ago

It seems to be an issue with my firewall rules on the NAS. Disabling the firewall and the speedtest completed however I'm not sure how to setup the firewall correctly in this instance. I'll keep at it and let you know.

rmcgirr83 commented 1 month ago

So the issue was the container with docker had joined a some speedtest_default network defined as 172.28.0.x, my bridge network is set as 172.17.0.x and has a firewall rule to allow connections to this network. Changing the docker container network from the speedtest_default to the bridge network and things are running as normal. Capture

rmcgirr83 commented 1 month ago

You may want to include the network_mode in yml instructions for docker containers ;)

services: speedtest: container_name: speedtest image: lscr.io/linuxserver/speedtest-tracker:latest ports:

  • 8999:80 volumes:
  • /volume1/docker/speedtest:/config environment:
  • PGID=100
  • PUID=1032
  • APP_TIMEZONE=America/New_York
  • DISPLAY_TIMEZONE=America/New_York
  • DB_CONNECTION=sqlite
  • APP_KEY=redacted
  • SPEEDTEST_SERVERS=56485
  • SPEEDTEST_SCHEDULE=0 restart: unless-stopped network_mode: bridge
alexjustesen commented 1 month ago

You may want to include the network_mode in yml instructions for docker containers ;)

Glad you were able to locate the issue! I'll make a note in the docs as it depends on how people have networking setup in their particular instances.