[solved - no need to reply] Deployed corteza on synology - can't access it locally

🚧 Installation
#1

Hey all!
I deployed corteza on my synology nas using portainer. I followed every step in the devops guide excluding proxy configuration as I wanted to just access it locally. Here is the yaml I used

version: '3.5'

services:
  server:
    image: cortezaproject/corteza:${VERSION}
    networks: [ internal ]
    restart: always
    depends_on: [ db ]
    volumes: [ "/volume1/docker/my-corteza/data/server:/data" ] 

    ports:
      - "8080:80"
      - "8443:443"

  db:
    image: postgres:15
    networks: [ internal ]
    restart: always
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U corteza"]
      interval: 10s
      timeout: 5s
      retries: 5
    environment:
      POSTGRES_USER: corteza
      POSTGRES_PASSWORD: corteza

networks:
  internal: {}

and .env

VERSION=2023.9.2
DB_DSN=postgres://corteza:corteza@192.168.80.2:5432/corteza?sslmode=disable
HTTP_WEBAPP_ENABLED=true
AUTH_JWT_SECRET=IDIDSETARANDOMSTRING

When I access http://192.168.100.76:8080/ the browser spits out error that it can’t connect and the adress bar changes to this:

http://localhost/auth/oauth2/default-client?redirect_uri=http://192.168.100.76:8080/auth/callback&scope=profile%20api&state=k67waf5rzia

Here are the logs from conrteza server:

WRN ts=1706733617.1465569 msg=You're using SQLite as a storage backend

WRN ts=1706733617.1470199 msg=Should be used only for testing

WRN ts=1706733617.1470466 msg=You may experience instability and data loss

WRN ts=1706733619.6275828 msg=no SMTP servers found, email sending will be disabled

WRN ts=1706733619.6331358 msg=Environmental variables (APIGW_*) and integration gateway settings (most likely changed via admin console) are not the same. When server was restarted, values from environmental variables were copied to settings for easier management. To avoid confusion and potential issues, we suggest you to remove all APIGW_* variables

WRN ts=1706733619.639159 logger=http.apigw msg=profiler enabled only for routes with a profiler prefilter, use global setting to enable for all (APIGW_PROFILER_GLOBAL)

WRN ts=1706733619.6395144 logger=http.apigw msg=profiler enabled only for routes with a profiler prefilter, use global setting to enable for all (APIGW_PROFILER_GLOBAL)

WRN ts=1706733619.640113 logger=http.apigw msg=profiler enabled only for routes with a profiler prefilter, use global setting to enable for all (APIGW_PROFILER_GLOBAL)

And logs for corteza db

PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-01-31 20:40:15.534 UTC [1] LOG:  starting PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

2024-01-31 20:40:15.548 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432

2024-01-31 20:40:15.548 UTC [1] LOG:  listening on IPv6 address "::", port 5432

2024-01-31 20:40:15.635 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-01-31 20:40:15.850 UTC [28] LOG:  database system was shut down at 2024-01-31 20:39:55 UTC

2024-01-31 20:40:16.141 UTC [1] LOG:  database system is ready to accept connections

I’m completely new at this so I could be doing some rookie mistake, however I hired a dude proficient at docker and linux administration, and while he wasn’t completely going by the devops guide as he was testing, he encountered the exact same issue when trying to expose ports locally.
Please help.

#2