SQLite '400 Bad Request'

[meelokun]

Copy and pasting your docker-compose into my existing docker-compose file is proving to be challenging. Admittingly, I'm a bit of a docker novice. I have been successful in loading various docker containers via docker-compose, but yours contains code/structure ive never come across before in a docker-compose.

I get the following when attempting to pull. (i put yours at the top of my docker compose file for convenience...

I'm wondering if its just a spacing issue... Noticed theres varing amounts of spacing as compared to all my other containers in my compose file.

Also - i hope this is ok, but i did deviate and changed the app_port to 8765 (coping the predecessor)

I'm running a Synology DS1621+ NAS (DSM 7.1.1)

[alexdelprete]

Check the docs site for the official examples: https://docs.speedtest-tracker.dev/getting-started/installation#install-with-docker-compose

Choose the one based on the database you want to use.

Just as an example, this is my docker-compose, with 2 space indentation (doesn't make much difference), using an external database (MariaDB):

version: '3.3'
services:
  speedtest-tracker:
    image: ghcr.io/alexjustesen/speedtest-tracker:v0.3.0
    container_name: speedtest-tracker
    restart: unless-stopped
    ports:
      - 8008:443
    environment:
      TZ: Europe/Rome
      PUID: 1000
      PGID: 1000
      DB_CONNECTION: mysql
      DB_HOST: mariadb.domain.local
      DB_PORT: 3306
      DB_DATABASE: speedtest_tracker
      DB_USERNAME: db_user
      DB_PASSWORD: db_pw
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - $PWD/config:/config
      - $PWD/certs:/etc/ssl/web

[Ceredril]

Is it possible to use a HTTP Port instead?
(asking this because my Firefox browser aswell as my cloudflared tunnel are not happy with opening this port on localhost over HTTPS)

[alexjustesen]

I'm going to be enabling mixed ssl at the container layer in the next release so you can map to port 80 or 443 for http and https requests.

[alexdelprete]

Is it possible to use a HTTP Port instead?

Yes, through the SSL_MODE env. variable:

1. SSL_MODE=mixed both http/80 and https/443 available
2. SSL_MODE=full (default) only https/443 available
3. SSL_MODE=off only http/80 available

If you don't configure it, the default is FULL, so only https/443.

[Ceredril]

Thank you for the tip!
Another noob question: I wasnt able to reuse the same port I already opened for 443. What would I have to do for that? Does Docker not close connections after deleting a container?

[alexdelprete]

if you stop a container the internal port is released. if you find it open, there's another service/container that is using it.

if you want to see the status of all running containers and all the ports, I use this command:

docker ps --format '\''CONTAINER ID: {{.ID}} | NAME: {{.Names}} | IMAGE:  {{.Image}} |  PORTS: {{.Ports}}'\

In the list you will see all containers, the status, and the ports used.