Installation problem

[Azurz]

Hello,

I installed with Docker Compose, but I can't log in to the web console. I get this error.
POST http://localhost:8400/token net::ERR_CONNECTION_REFUSED

[robigan]

Provide docker compose configuration and more details.

POST http://localhost:8400/token net::ERR_CONNECTION_REFUSED

Where? Doing what? From the fronted? Is this what shows in the notification error (if from frontend) or some sort of console?

[Azurz]

Docker-compose.yml
version: '3.1'

services:
    bracket-frontend:
        image: ghcr.io/evroon/bracket-frontend
        container_name: bracket-frontend
        ports:
            - "3000:3000"
        environment:
            NEXT_PUBLIC_API_BASE_URL: "http://localhost:8400"
            NEXT_PUBLIC_HCAPTCHA_SITE_KEY: "10000000-ffff-ffff-ffff-000000000001"  # Public test key
        restart: unless-stopped

    bracket-backend:
        image: ghcr.io/evroon/bracket-backend
        container_name: bracket-backend
        ports:
            - "8400:8400"
        environment:
            ENVIRONMENT: "DEVELOPMENT"
            PG_DSN: "postgresql://bracket_dev:bracket_dev@postgres:5432/bracket_dev"
        restart: unless-stopped
        depends_on:
          - postgres

    postgres:
        image: postgres
        restart: always
        environment:
          POSTGRES_DB: bracket_dev
          POSTGRES_USER: bracket_dev
          POSTGRES_PASSWORD: bracket_dev

[evroon]

It could be that your firewall is blocking port 8400

[TheKringel]

I installed Bracket today on my Synology Docker environment and had the same issue but was able to fix it based on this solution:
#445

I'm using DDNS for my synology and I'm now able to access Brackets through DDNS.

For me the following worked:

1. Add the following to the docker compose file
   CORS_ORIGINS: "*" as environment variable to bracket-backend container
   NEXT_PUBLIC_API_BASE_URL: "http://<my_ddns_name>:8400" to bracket-frontend
2. re-create the docker containers
3. Open Port on firewall

[aledre]

I installed Bracket today on my Synology Docker environment and had the same issue but was able to fix it based on this solution: #445

I'm using DDNS for my synology and I'm now able to access Brackets through DDNS.

For me the following worked:

1. Add the following to the docker compose file
   CORS_ORIGINS: "*" as environment variable to bracket-backend container
   NEXT_PUBLIC_API_BASE_URL: "http://<my_ddns_name>:8400" to bracket-frontend
2. re-create the docker containers
3. Open Port on firewall

Can you explain me how to install on synology nas? I like to do it, but I'm new to github. I have other dockers running on nas, but I don't know how to install bracket from github in docker

[ghost]

Personally, I have found that NAS systems implement docker in a way different to how they would be on a regular VM (like debian or whatever).

I have a QNAP box, and it has it's own docker implementation called "Container Station".
While it does work, it does seem to have some issues with some docker projects that use ".env" files in the filesystem.

I recommend creating a VM in your Synology NAS, and try installing Bracket inside Docker on that instead.

There are a lot of unknowns in the QNAP / Synology container implementations - I think they are worth avoiding!