[BUG] <title>This constantly goes down for me and has to be restarted to access

[Landrin201]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I'm honestly not even sure the best way to describe the issue I'm having here, I'll do my best.

I have the speedtest-tracker running with a postgresql database, set up via a docker compose.

When I start both containers up it works fine, at first. I can access the UI and run manual tests.

But after a while (I don't know why because I see nothing wrong in the logs) the UI and API both become inaccessible. I have to force both the database container and the main container to restart in order to be able to access the UI again.

When I get back into the UI, I will see that ALL of the last requests have failed. When I restart the containers I'll see 2-3 runs work (I schedule runs every 2 hours) then start failing after 4-6 hours; I see no clear errors for any of these failures. They just say that something was wrong with the connection, but I can confirm that the connection is still working (this runs behind glutun with a VPN on and other apps run behind the same instance).

All of the graphs are NEVER populated, even though there IS data in the past.

I'm really not sure what is happening here. The container logs contain NOTHING. I'm going nuts, and I haven't got a clue what's wrong.

Expected Behavior

No response

Steps To Reproduce

I honestly don't even know. Start the container, let it run for more than 6 hours, try to access the UI. The UI is just inaccessible.

Environment

- OS: debian
- How docker service was installed: docker-compose, pasted above

CPU architecture

x86-64

Docker creation

speedtest-tracker:
    container_name: speedtest-tracker
    image: 'lscr.io/linuxserver/speedtest-tracker:latest'
    network_mode: service:gluetun_protonvpn
    restart: unless-stopped
    environment:
        - PUID=1000
        - PGID=1000
        - DB_CONNECTION=pgsql
        - DB_HOST=localhost
        - DB_PORT=port
        - DB_DATABASE=speedtest_tracker
        - DB_USERNAME=user
        - DB_PASSWORD=password
        - TZ=America/New_York
        - APP_KEY=key
        - SPEEDTEST_SCHEDULE=6 */2 * * *
    volumes:
        - '/etc/localtime:/etc/localtime:ro'
        - '/configStorage/config/arrSpeedtestTracker/config:/config'
    depends_on:
        - speedtest_tracker_db
        - gluetun_protonvpn

    labels:
      - "deunhealth.restart.on.unhealthy=true"
      
  speedtest_tracker_db:
    image: postgres:15
    container_name: speedtest_tracker_db
    restart: unless-stopped
    network_mode: service:gluetun_protonvpn
    depends_on:
        - gluetun_protonvpn
    environment:

        - POSTGRES_DB=speedtest_tracker
        - POSTGRES_USER=user
        - POSTGRES_PASSWORD=password
    volumes:
          - /configStorage/config/arrSpeedtestTracker/database:/var/lib/postgresql/data

Container logs

using keys found in /config/keys

Waiting for DB to be available

**** The following active confs have different version dates than the samples that are shipped. ****

**** This may be due to user customization or an update to the samples. ****

**** You should compare the following files to the samples in the same folder and update them. ****

**** Use the link at the top of the file to view the changelog. ****

┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐

│  old date  │  new date  │ path                                                                   │

├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤

│ 2024-05-27 │ 2024-07-16 │ /config/nginx/site-confs/default.conf                                  │

└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘

[custom-init] No custom files found, skipping...

[ls.io-init] done.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[ramazansancar]

Is the problem still there? @Landrin201
Did you check the log files?

Docker log command:

sudo docker container logs --follow speedtest-tracker

Check Log file command:

docker exec speedtest-tracker cat /app/www/storage/logs/laravel.log

I am sharing my own docker configuration to understand the problem.
I can run it without any problems with these configurations.

version: "3"

services:
  speedtest-tracker:
    image: lscr.io/linuxserver/speedtest-tracker:latest
    container_name: speedtest-tracker
    restart: unless-stopped
    ports:
      - 9898:80
      - 9443:443
    environment: # https://docs.speedtest-tracker.dev/getting-started/environment-variables
      - PUID=1000
      - PGID=1000
      - APP_KEY=base64:(hidden)
      - DB_CONNECTION=sqlite
      - SPEEDTEST_SCHEDULE=6 */1 * * *
    #  - SPEEDTEST_SERVERS=42411,20981,20989,60741,20960,39901 # https://www.speedtest.net/speedtest-servers-static.php,https://c.speedtest.net/speedtest-servers-static.php
      - PRUNE_RESULTS_OLDER_THAN=180
      - CHART_DATETIME_FORMAT=j/m G:i
      - DATETIME_FORMAT=j M Y, G:i:s
      - APP_TIMEZONE=Europe/Istanbul
      - PUBLIC_DASHBOARD=true
      - DASHBOARD_POLLING=60
      - RESULTS_POLLING=60
      - DISPLAY_TIMEZONE=Europe/Istanbul
      - APP_LOCALE=tr_TR
    volumes:
      - ./data:/config
      - ./data/keys:/config/keys

[drizuid]

no response from OP, we can't reproduce internally. OP also indicates they installed docker using docker-compose which is impossible and makes it hard for us to try to reproduce the issue.