Synology docker compose problem

[gkazanci]

Hello, I am not a very good docker user, but I have been trying to install it via the interface on synology for 2 days, but I have not been successful yet. I want to install it with the yaml codes below. But I get the error below. I took a screenshot because I could not get the logs.

services:
  frontend:
    image: ghcr.io/worklenz/worklenz-frontend
    build:
      context: ./worklenz-frontend
      dockerfile: Dockerfile
    container_name: worklenz_frontend
    ports:
      - "4200:4200"
    depends_on:
      backend:
        condition: service_started
    networks:
      - bridge    

  backend:
    image: ghcr.io/worklenz/worklenz-backend
    build:
      context: ./worklenz-backend
      dockerfile: Dockerfile
    container_name: worklenz_backend
    ports:
      - "3000:3000"
    depends_on:
      db:
        condition: service_healthy
    environment:
      - ANGULAR_DIST_DIR="./worklenz_frontend/dist/worklenz" 
      - ANGULAR_SRC_DIR="./worklenz_frontend"
      #- AWS_REGION
      - BACKEND_PUBLIC_DIR="./worklenz_backend/src/public"
      - BACKEND_VIEWS_DIR"./worklenz_backend/src/views/admin"
      - COMMIT_BUILD_IMMEDIATELY=true
      - COOKIE_SECRET=test
      #- DB_HOST=worklenz-db
      #- DB_MAX_CLIENTS
      - DB_NAME=worklenz-db
      - DB_PASSWORD=worklenz
      - DB_PORT=5433
      - DB_MAX_CLIENTS=50
      - DB_USER=worklenz_backend
      #- GOOGLE_CALLBACK_URL
      #- GOOGLE_CLIENT_ID=test
      #- GOOGLE_CLIENT_SECRET=test
      - HOSTNAME=localhost:4200
      #- LOGIN_FAILURE_REDIRECT
      - NODE_ENV=development
      - PORT=3000
      - SESSION_NAME=worklenz.sid
      - SESSION_SECRET=test
      #- SLACK_WEBHOOK
      - SOCKET_IO_CORS=http://localhost:4200
      - SERVER_CORS=*
      #- SOURCE_EMAIL
      #- USE_PG_NATIVE
      #- BUCKET
      #- REGION
      #- S3_URL=test
      #- S3_ACCESS_KEY_ID=test
      #- S3_SECRET_ACCESS_KEY=test

    networks:
      - bridge  

  db:
    image: postgres:15
    container_name: worklenz_db
    environment:
      POSTGRES_DB: "worklenz_db"
      POSTGRES_PASSWORD: "worklenz"
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -d worklenz_db -U worklenz_client"]
      interval: 10s
      timeout: 5s
      retries: 5
    networks:
      - bridge  
    volumes:
      - worklenz_postgres_data:/var/lib/postgresql/data
      - ./worklenz-backend/database/:/docker-entrypoint-initdb.d

volumes:
  worklenz_postgres_data:

networks:
  bridge:

[gkazanci]

I solved this problem after long efforts. I bypassed the Docker dns address by setting it to 8.8.8.8.

The installation is now complete, but I am getting an error like this.

http://192.168.1.56:3000/auth

Error: connection to server at "127.0.0.1", port 5432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections?

at /usr/src/app/node_modules/pg-pool/index.js:45:11
at tryCatcher (/usr/src/app/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/src/app/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/usr/src/app/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromise0 (/usr/src/app/node_modules/bluebird/js/release/promise.js:649:10)
at Promise._settlePromises (/usr/src/app/node_modules/bluebird/js/release/promise.js:725:18)
at _drainQueueStep (/usr/src/app/node_modules/bluebird/js/release/async.js:93:12)
at _drainQueue (/usr/src/app/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/usr/src/app/node_modules/bluebird/js/release/async.js:102:5)
at Async.drainQueues [as _onImmediate] (/usr/src/app/node_modules/bluebird/js/release/async.js:15:14)
at process.processImmediate (node:internal/timers:476:21)

[gkazanci]

I overcame this problem. But it's too bad there's no trouble-free guide on this subject, it really took me days to set it up.

But this time I have a problem. The person I invited for registration is not receiving an email.

[kalinga777]

@gkazanci Could you pleas chech thst this issue fixed?

[kallal79]

I'd like to work on this issue because I specialize in reproducible infrastructure and troubleshooting complex environment setups. I’ve resolved CI and ARM64 compatibility issues in Veraison and managed Docker org ownership for sponsorship eligibility, so I’m comfortable debugging container orchestration and service connectivity.

Plan of Action:

Audit the Docker Compose YAML for syntax issues (e.g. missing = in BACKEND_VIEWS_DIR).

Ensure DB_HOST=worklenz_db is uncommented and matches the container name.

Verify Postgres user worklenz_client exists and has access to worklenz_db.

Inspect backend email configuration—check SMTP credentials, environment variables, and logs for delivery errors.

Document a reproducible setup guide tailored for Synology users.

[kalinga777]

@7908837174 -Please , let us know once you have contributed