Reverse proxy not working with docker container http:port yes, httpS no

[vpsnewbie]

I can't seem to securely access Umami without a port number. I can access Umami via http://IP:3001 or http://umami.domain.com:3001 but not via https://umami.domain.com

I have several setups with and without docker containers set up the exact same way via reverse proxy (external app under severer configuration + rewrite rule in .htaccess) on OpenLiteSpeed (i.e. cyberpanel, openlitespeed, filebrowser).

However, with Umami it does not work. It's the first software that will does not want to talk to be via httpS and without port a number (3001).

Things I've tried

• I've also turned off any firewall just to make sure that wasn't causing any issue.
• Also, trying to delete the ENV varible hostname 0.0.0.0 (to see if that does anything) redeploying the container and restarting docker did not work. It automatically added the variable back. But same issue.

I changed the default port to 3001 as with 3000 there was a port conflict with nghttpx.

Here's my stack compose file

version: '3'
services:
  umami:
    image: ghcr.io/umami-software/umami:postgresql-latest
    container_name: Umami
    ports:
      - 3001:3000
    environment:
      TRACKER_SCRIPT_NAME: oishii
      DATABASE_URL: postgresql://umami:umami@db:5432/umami
      DATABASE_TYPE: postgresql
      APP_SECRET: XXXXXXX
    depends_on:
      db:
        condition: service_healthy
    restart: always
  db:
    image: postgres:15-alpine
    container_name: Umami-db
    environment:
      POSTGRES_DB: umami
      POSTGRES_USER: umami
      POSTGRES_PASSWORD: umami
    volumes:
      - umami-db-data:/var/lib/postgresql/data
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
      interval: 5s
      timeout: 5s
      retries: 5
volumes:
  umami-db-data:

I used Portainer BE that deployed the umami stack via the docker compose file from above.

I'm running a VPS on Ubuntu 22.04.3 LTS (GNU/Linux 5.15.0-86-generic x86_64), Cyberpanel & OpenLitespeed (both most current versions)

Just a guess
Don't docker containers have their own networking thing? As my other stuff like the Cyberpanel & Openlitespeed run natively without docker could that be the problem? And if so how to I fix that?

Any ideas what it could be?

 

[Cold-Egg]

It should doable. Have you checked the connection between OLS and the docker container with curl command? Will it return a 200 if you try to SSH to the server, and run curl http://127.0.0.1:3001?