worker exciting error

[ypkoba]

I get an error wenn trying to login the famous: internal error.
In the log of the backend contoiner i got the following:

File "/usr/local/lib/python3.14/contextlib.py", line 214, in aenter
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/fastapi/routing.py", line 153, in merged_lifespan
async with original_context(app) as maybe_original_state:
~~~~~~~~~~~~~~~~^^^^^
File "/usr/local/lib/python3.14/contextlib.py", line 214, in aenter
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/fastapi/routing.py", line 153, in merged_lifespan
async with original_context(app) as maybe_original_state:
~~~~~~~~~~~~~~~~^^^^^
File "/usr/local/lib/python3.14/contextlib.py", line 214, in aenter
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/fastapi/routing.py", line 153, in merged_lifespan
async with original_context(app) as maybe_original_state:
~~~~~~~~~~~~~~~~^^^^^
File "/usr/local/lib/python3.14/contextlib.py", line 214, in aenter
return await anext(self.gen)
^^^^^^^^^^^^^^^^^^^^^
File "/app/bracket/app.py", line 45, in lifespan
await database.connect()
File "/app/.venv/lib/python3.14/site-packages/databases/core.py", line 112, in connect
await self._backend.connect()
File "/app/.venv/lib/python3.14/site-packages/databases/backends/postgres.py", line 74, in connect
self.pool = await asyncpg.create_pool(**kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/pool.py", line 439, in async__init
await self._initialize()
File "/app/.venv/lib/python3.14/site-packages/asyncpg/pool.py", line 466, in _initialize
await first_ch.connect()
File "/app/.venv/lib/python3.14/site-packages/asyncpg/pool.py", line 153, in connect
self._con = await self._pool._get_new_connection()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/pool.py", line 538, in _get_new_connection
con = await self._connect(
^^^^^^^^^^^^^^^^^^^^
...<5 lines>...
)
^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/connection.py", line 2443, in connect
return await connect_utils._connect(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<22 lines>...
)
^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1249, in _connect
raise last_error or exceptions.TargetServerAttributeNotMatched(
...<2 lines>...
)
File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1218, in _connect
conn = await _connect_addr(
^^^^^^^^^^^^^^^^^^^^
...<6 lines>...
)
^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1054, in _connect_addr
return await __connect_addr(params, True, *args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1099, in __connect_addr
tr, pr = await connector
^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 969, in _create_ssl_connection
tr, pr = await loop.create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<2 lines>...
host, port)
^^^^^^^^^^^
File "/usr/local/lib/python3.14/asyncio/base_events.py", line 1119, in create_connection
infos = await self._ensure_resolved(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(host, port), family=family,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
type=socket.SOCK_STREAM, proto=proto, flags=flags, loop=self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/asyncio/base_events.py", line 1505, in _ensure_resolved
return await loop.getaddrinfo(host, port, family=family, type=type,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
proto=proto, flags=flags)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/asyncio/base_events.py", line 936, in getaddrinfo
return await self.run_in_executor(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
None, getaddr_func, host, port, family, type, proto, flags)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 86, in run
result = ctx.run(self.task)
File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 73, in run
return fn(*args, **kwargs)
File "/usr/local/lib/python3.14/socket.py", line 983, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -3] Try again
[2026-05-25 12:38:49 +0000] [10] [ERROR] Application startup failed. Exiting.
[2026-05-25 12:38:49 +0000] [10] [INFO] Worker exiting (pid: 10)
[2026-05-25 12:38:50 +0000] [9] [ERROR] Worker (pid:10) exited with code 3
[2026-05-25 12:38:50 +0000] [9] [ERROR] Shutting down: Master
[2026-05-25 12:38:50 +0000] [9] [ERROR] Reason: Worker failed to boot.

[CarlosOliveira-23]

Hey! Don't worry, this error is actually more common than it looks — and it has nothing to do with your login credentials or the Bracket app itself.

The real problem is happening before the app even starts. When the backend boots up, it tries to connect to your PostgreSQL database, and it simply can't find it. The line that gives it away is this one:

socket.gaierror: [Errno -3] Try again

That's a DNS resolution failure — meaning the backend container is looking for the database by hostname and coming up empty. Here are the most likely culprits:

1. Wrong database hostname in your .env file
   Double-check your PG_HOST variable. It should match the service name defined in your docker-compose.yml — typically something like "db" or "postgres". If you put "localhost" there, that won't work inside Docker.

2. Containers not on the same network
   If you started the backend and the database separately instead of using "docker compose up" together, they might not be able to talk to each other. Try bringing everything down and back up:

   docker compose down
   docker compose up
   

3. The database container isn't actually running
   Run "docker ps" and confirm the PostgreSQL container is listed and healthy. If it crashed on startup, the backend won't be able to reach it.

4. You're running Python 3.14
   The traceback shows python3.14, which is a very new (possibly pre-release) version. It might be worth switching to a stable, officially supported version just to rule out any compatibility issues with the dependencies.

A quick way to confirm the DNS issue: get a shell inside the backend container and try pinging the database hostname:

docker exec -it <backend_container_name> ping <your_db_hostname>

If that fails, you've confirmed the network/DNS issue and one of the steps above should fix it.

Hope this helps — let us know what you find!

[ypkoba]

Thank you for your information. I do have not much experience with docker, to what ip-adress needs the backend linking to?
I find difficult to get the right configuration for the docker file. I tried de simple route but it had login problems.
Can you point me to how to configure the docker file?
This is the docker file I have used.
services:
bracket-frontend:
image: ghcr.io/evroon/bracket-frontend
container_name: bracket-frontend
ports:
- "3003:3003" # I have changed this because olama runs on 3000
environment:
NODE_ENV: "production"
VITE_API_BASE_URL: "localhost:8400"
VITE_HCAPTCHA_SITE_KEY: ""
restart: unless-stopped

bracket-backend:
    image: ghcr.io/evroon/bracket-backend
    container_name: bracket-backend
    ports:
        - "8400:8400"
    environment:
        ENVIRONMENT: "PRODUCTION"
        PG_DSN: "postgresql://bracket_prod:bracket_prod@postgres:5432/bracket_prod"
        CORS_ORIGINS: postgres:5432
        JWT_SECRET: change_me
    volumes:
        - ./backend/static:/app/static
    restart: unless-stopped
    depends_on:
      - postgres

postgres:
    image: postgres
    restart: always
    environment:
      POSTGRES_DB: bracket_prod
      POSTGRES_USER: bracket_prod
      POSTGRES_PASSWORD: bracket_prod
    volumes:
      - ./postgres:/var/lib/postgresql

[CarlosOliveira-23]

SUMMARY

The backend container cannot connect to the PostgreSQL database on startup.
The worker crashes before the app is ready, which is why you see
"internal error" when trying to login. The login itself is never reached.

ROOT CAUSE

The traceback ends with:

socket.gaierror: [Errno -3] Try again

This means the backend tried to resolve the hostname in PG_DSN and failed.
DNS resolution returned "Try again" — the container could not look up the
database host at startup time.

Looking at your docker-compose config, there are two problems:

PROBLEM 1 — CORS_ORIGINS is set to a database address (wrong value)

CORS_ORIGINS: postgres:5432 <-- THIS IS WRONG

CORS_ORIGINS should be the URL of your frontend, not the database host.
For example:
CORS_ORIGINS: "http://localhost:3000"

or your actual frontend domain:

CORS_ORIGINS: "https://yourdomain.com"

This won't cause the boot crash directly, but it is a misconfiguration
that will cause CORS errors once the app is running.

PROBLEM 2 — Race condition: backend starts before postgres is ready

Your compose file has:

depends_on:
- postgres

depends_on only waits for the postgres CONTAINER to start, not for
PostgreSQL to be ready to accept connections. The backend starts,
tries to connect immediately, and fails because postgres is still
initializing.

Fix: use a healthcheck on the postgres service so the backend only
starts after the database is truly ready.

Updated docker-compose.yml:

  postgres:
    image: postgres
    restart: always
    environment:
      POSTGRES_DB: bracket_prod
      POSTGRES_USER: bracket_prod
      POSTGRES_PASSWORD: bracket_prod
    volumes:
      - ./postgres:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U bracket_prod -d bracket_prod"]
      interval: 5s
      timeout: 5s
      retries: 10



  bracket-backend:
    image: ghcr.io/evroon/bracket-backend
    container_name: bracket-backend
    ports:
      - "8400:8400"
    environment:
      ENVIRONMENT: "PRODUCTION"
      PG_DSN: "postgresql://bracket_prod:bracket_prod@postgres:5432/bracket_prod"
      CORS_ORIGINS: "http://localhost:3000"   # <-- fix this to your frontend URL
      JWT_SECRET: change_me                   # <-- change this to a real secret!
    volumes:
      - ./backend/static:/app/static
    restart: unless-stopped
    depends_on:
      postgres:
        condition: service_healthy            # <-- wait for healthcheck, not just startup

PROBLEM 3 — postgres volume path is incomplete

Your volume mapping is:

• ./postgres:/var/lib/postgresql

The correct path inside the container is:

• ./postgres:/var/lib/postgresql/data

Without /data, PostgreSQL will either fail to initialize or lose data
between restarts.

ALSO: Change your JWT_SECRET

Your config has:
JWT_SECRET: change_me

This is a security risk in production. Generate a strong secret:
openssl rand -hex 32

STEPS TO APPLY THE FIX

1. Stop and remove the existing containers:
   docker compose down

2. Update your docker-compose.yml with the fixes above.

3. Remove the old postgres data volume if initialization failed:
   rm -rf ./postgres

4. Start everything again:
   docker compose up -d

5. Check the backend logs:
   docker compose logs -f bracket-backend

USEFUL LINKS

• Bracket docs: https://evroon.github.io/bracket/
• Docker healthcheck docs: https://docs.docker.com/compose/compose-file/05-services/#healthcheck
• depends_on with condition: https://docs.docker.com/compose/compose-file/05-services/#depends_on

[ypkoba]

I got the following error.
Error: in 18+, these Docker images are configured to store database data in a
format which is compatible with "pg_ctlcluster" (specifically, using
major-version-specific directory names). This better reflects how
PostgreSQL itself works, and how upgrades are to be performed.
See also docker-library/postgres#1259
Counter to that, there appears to be PostgreSQL data in:
/var/lib/postgresql/data (unused mount/volume)
This is usually the result of upgrading the Docker image without
upgrading the underlying database using "pg_upgrade" (which requires both
versions).
The suggested container configuration for 18+ is to place a single mount
at /var/lib/postgresql which will then place PostgreSQL data in a
subdirectory, allowing usage of "pg_upgrade --link" without mount point
boundary issues.
See docker-library/postgres#37 for a (long)
discussion around this process, and suggestions for how to do so.

I solved this by placing the data folder from postgres in the home folder

• ./postgres:/home/falken/lib/postgresql/data

the postgres log gives the following.
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
syncing data to disk ... ok
Success. You can now start the database server using:
pg_ctl -D /var/lib/postgresql/18/docker -l logfile start
waiting for server to start....2026-05-27 20:37:35.133 UTC [53] LOG: starting PostgreSQL 18.3 (Debian 18.3-1.pgdg13+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-05-27 20:37:35.135 UTC [53] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-05-27 20:37:35.139 UTC [59] LOG: database system was shut down at 2026-05-27 20:37:34 UTC
2026-05-27 20:37:35.142 UTC [53] LOG: database system is ready to accept connections
done
server started
CREATE DATABASE
/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
waiting for server to shut down....2026-05-27 20:37:35.321 UTC [53] LOG: received fast shutdown request
2026-05-27 20:37:35.323 UTC [53] LOG: aborting any active transactions
2026-05-27 20:37:35.326 UTC [53] LOG: background worker "logical replication launcher" (PID 62) exited with exit code 1
2026-05-27 20:37:35.326 UTC [57] LOG: shutting down
2026-05-27 20:37:35.327 UTC [57] LOG: checkpoint starting: shutdown immediate
2026-05-27 20:37:35.363 UTC [57] LOG: checkpoint complete: wrote 943 buffers (5.8%), wrote 3 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=0.013 s, sync=0.020 s, total=0.038 s; sync files=303, longest=0.002 s, average=0.001 s; distance=4352 kB, estimate=4352 kB; lsn=0/1B9FBB8, redo lsn=0/1B9FBB8
2026-05-27 20:37:35.370 UTC [53] LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
2026-05-27 20:37:35.438 UTC [1] LOG: starting PostgreSQL 18.3 (Debian 18.3-1.pgdg13+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2026-05-27 20:37:35.438 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2026-05-27 20:37:35.438 UTC [1] LOG: listening on IPv6 address "::", port 5432
2026-05-27 20:37:35.441 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-05-27 20:37:35.445 UTC [75] LOG: database system was shut down at 2026-05-27 20:37:35 UTC
2026-05-27 20:37:35.449 UTC [1] LOG: database system is ready to accept connections
2026-05-27 20:37:48.578 UTC [105] ERROR: index "ix_users_email" does not exist
2026-05-27 20:37:48.578 UTC [105] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:37:53.388 UTC [124] ERROR: index "ix_users_email" does not exist
2026-05-27 20:37:53.388 UTC [124] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:37:58.139 UTC [143] ERROR: index "ix_users_email" does not exist
2026-05-27 20:37:58.139 UTC [143] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:38:03.154 UTC [162] ERROR: index "ix_users_email" does not exist
2026-05-27 20:38:03.154 UTC [162] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:38:08.540 UTC [182] ERROR: index "ix_users_email" does not exist
2026-05-27 20:38:08.540 UTC [182] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:38:14.723 UTC [201] ERROR: index "ix_users_email" does not exist
2026-05-27 20:38:14.723 UTC [201] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:38:22.588 UTC [228] ERROR: index "ix_users_email" does not exist
2026-05-27 20:38:22.588 UTC [228] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:38:33.845 UTC [256] ERROR: index "ix_users_email" does not exist
2026-05-27 20:38:33.845 UTC [256] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:38:51.329 UTC [300] ERROR: index "ix_users_email" does not exist
2026-05-27 20:38:51.329 UTC [300] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:39:21.531 UTC [361] ERROR: index "ix_users_email" does not exist
2026-05-27 20:39:21.531 UTC [361] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:40:17.458 UTC [463] ERROR: index "ix_users_email" does not exist
2026-05-27 20:40:17.458 UTC [463] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:41:22.107 UTC [573] ERROR: index "ix_users_email" does not exist
2026-05-27 20:41:22.107 UTC [573] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:42:26.780 UTC [691] ERROR: index "ix_users_email" does not exist
2026-05-27 20:42:26.780 UTC [691] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:42:35.515 UTC [73] LOG: checkpoint starting: time
2026-05-27 20:42:45.921 UTC [73] LOG: checkpoint complete: wrote 103 buffers (0.6%), wrote 3 SLRU buffers; 1 WAL file(s) added, 0 removed, 0 recycled; write=10.318 s, sync=0.031 s, total=10.407 s; sync files=71, longest=0.018 s, average=0.001 s; distance=704 kB, estimate=704 kB; lsn=0/1C4FEF8, redo lsn=0/1C4FEA0
2026-05-27 20:43:31.645 UTC [809] ERROR: index "ix_users_email" does not exist
2026-05-27 20:43:31.645 UTC [809] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:44:36.412 UTC [920] ERROR: index "ix_users_email" does not exist
2026-05-27 20:44:36.412 UTC [920] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:45:41.137 UTC [1038] ERROR: index "ix_users_email" does not exist
2026-05-27 20:45:41.137 UTC [1038] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:46:45.767 UTC [1156] ERROR: index "ix_users_email" does not exist
2026-05-27 20:46:45.767 UTC [1156] STATEMENT:
DROP INDEX ix_users_email
2026-05-27 20:47:35.995 UTC [73] LOG: checkpoint starting: time
2026-05-27 20:47:39.627 UTC [73] LOG: checkpoint complete: wrote 36 buffers (0.2%), wrote 1 SLRU buffers; 0 WAL file(s) added, 0 removed, 0 recycled; write=3.609 s, sync=0.018 s, total=3.633 s; sync files=32, longest=0.009 s, average=0.001 s; distance=202 kB, estimate=654 kB; lsn=0/1C829B0, redo lsn=0/1C82920
2026-05-27 20:47:50.419 UTC [1266] ERROR: index "ix_users_email" does not exist
2026-05-27 20:47:50.419 UTC [1266] STATEMENT:
DROP INDEX ix_users_email

and the log from the backend is:

module = load_module_py(module_id, path)

File "/app/.venv/lib/python3.14/site-packages/alembic/util/pyfiles.py", line 136, in load_module_py
spec.loader.exec_module(module) # type: ignore
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "", line 759, in exec_module
File "", line 491, in _call_with_frames_removed
File "/app/alembic/env.py", line 48, in
run_migrations_online()
~~~~~~~~~~~~~~~~~~~~~^^
File "/app/alembic/env.py", line 40, in run_migrations_online
context.run_migrations()
~~~~~~~~~~~~~~~~~~~~~~^^
File "", line 8, in run_migrations
File "/app/.venv/lib/python3.14/site-packages/alembic/runtime/environment.py", line 946, in run_migrations
self.get_context().run_migrations(**kw)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
File "/app/.venv/lib/python3.14/site-packages/alembic/runtime/migration.py", line 627, in run_migrations
step.migration_fn(**kw)
~~~~~~~~~~~~~~~~~^^^^^^
File "/app/alembic/versions/274385f2a757_add_on_delete_cascade_to_users_x_clubs.py", line 20, in upgrade
op.drop_index("ix_users_email", table_name="users")
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 8, in drop_index
File "", line 3, in drop_index
File "/app/.venv/lib/python3.14/site-packages/alembic/operations/ops.py", line 1142, in drop_index
return operations.invoke(op)
~~~~~~~~~~~~~~~~~^^^^
File "/app/.venv/lib/python3.14/site-packages/alembic/operations/base.py", line 441, in invoke
return fn(self, operation)
File "/app/.venv/lib/python3.14/site-packages/alembic/operations/toimpl.py", line 121, in drop_index
operations.impl.drop_index(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
operation.to_index(operations.migration_context),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**kw,
^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/alembic/ddl/impl.py", line 464, in drop_index
self._exec(schema.DropIndex(index, **kw))
~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/alembic/ddl/impl.py", line 246, in _exec
return conn.execute(construct, params)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1419, in execute
return meth(
self,
distilled_parameters,
execution_options or NO_OPTIONS,
)
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/sql/ddl.py", line 187, in _execute_on_connection
return connection._execute_ddl(
~~~~~~~~~~~~~~~~~~~~~~~^
self, distilled_params, execution_options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1530, in _execute_ddl
ret = self._execute_context(
dialect,
...<4 lines>...
compiled,
)
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1846, in _execute_context
return self._exec_single_context(
~~~~~~~~~~~~~~~~~~~~~~~~~^
dialect, context, statement, parameters
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1986, in _exec_single_context
self._handle_dbapi_exception(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
e, str_statement, effective_parameters, cursor, context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 2355, in _handle_dbapi_exception
raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context
self.dialect.do_execute(
~~~~~~~~~~~~~~~~~~~~~~~^
cursor, str_statement, effective_parameters, context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/default.py", line 951, in do_execute
cursor.execute(statement, parameters)
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedObject) index "ix_users_email" does not exist
[SQL:
DROP INDEX ix_users_email]
(Background on this error at: https://sqlalche.me/e/20/f405)
[2026-05-27 20:48:55 +0000] [10] [ERROR] Application startup failed. Exiting.
[2026-05-27 20:48:55 +0000] [10] [INFO] Worker exiting (pid: 10)
[2026-05-27 20:48:55 +0000] [9] [ERROR] Worker (pid:10) exited with code 3
[2026-05-27 20:48:55 +0000] [9] [ERROR] Shutting down: Master
[2026-05-27 20:48:55 +0000] [9] [ERROR] Reason: Worker failed to boot.

[CarlosOliveira-23]

SUMMARY

Good news: PostgreSQL is now running correctly. The new error is different —
the app is failing during the Alembic database migration, not at connection time.

The migration script tries to DROP an index that does not exist yet
in a freshly initialized database:

op.drop_index("ix_users_email", table_name="users")
-> sqlalchemy.exc.ProgrammingError: index "ix_users_email" does not exist

ROOT CAUSE

Alembic migration file:
274385f2a757_add_on_delete_cascade_to_users_x_clubs.py

This migration assumes the index "ix_users_email" already exists
(created by a previous migration), but your database is brand new and
the migrations are not being applied in the correct order, OR a previous
migration that created this index was skipped/failed silently.

This is a known issue when starting with a fresh database and the
migration chain has an implicit dependency on prior state.

FIX 1 — Wipe the database and let Alembic start from scratch (recommended)

Since this is a fresh database with no data, the cleanest fix is to
delete the postgres data folder and restart everything:

docker compose down

Remove the existing postgres data

rm -rf ./postgres

docker compose up -d

Watch the backend logs to confirm migrations complete successfully

docker compose logs -f bracket-backend

This forces Alembic to run ALL migrations in order from the beginning,
which will create the ix_users_email index before the migration that
tries to drop it.

FIX 2 — Run migrations manually inside the container (if you have data to keep)

If you already have data you want to preserve, connect to the backend
container and run migrations manually:

docker exec -it bracket-backend bash

Inside the container, stamp the database at the base revision

alembic stamp head

Or run all migrations step by step from the beginning

alembic downgrade base
alembic upgrade head

exit

Then restart the backend:
docker compose restart bracket-backend

FIX 3 — Apply the migration with IF EXISTS (temporary workaround)

If neither option above works, you can manually apply the failing
migration by connecting to the database and creating the index first,
so the DROP succeeds:

docker exec -it <postgres_container_name> psql
-U bracket_prod -d bracket_prod

-- Inside psql:
CREATE INDEX IF NOT EXISTS ix_users_email ON users (email);
\q

Then restart the backend:
docker compose restart bracket-backend

This lets Alembic drop and recreate the index as expected.

ABOUT THE POSTGRES 18 VOLUME WARNING (already resolved)

The error you saw earlier about /var/lib/postgresql/data was because
PostgreSQL 18+ stores data in a version-specific subdirectory
(/var/lib/postgresql/18/docker) instead of /data directly.

Your fix of using ./postgres:/home/falken/lib/postgresql/data is
non-standard. The correct and supported approach for PostgreSQL 18+
is to mount at the parent directory:

volumes:
- ./postgres:/var/lib/postgresql # <-- mount the parent, not /data

PostgreSQL 18 will then create ./postgres/18/docker/ automatically.
This also makes future pg_upgrade easier.

RECOMMENDED FINAL docker-compose.yml

postgres:
image: postgres
restart: always
environment:
POSTGRES_DB: bracket_prod
POSTGRES_USER: bracket_prod
POSTGRES_PASSWORD: bracket_prod
volumes:
- ./postgres:/var/lib/postgresql # correct for postgres 18+
healthcheck:
test: ["CMD-SHELL", "pg_isready -U bracket_prod -d bracket_prod"]
interval: 5s
timeout: 5s
retries: 10

bracket-backend:
image: ghcr.io/evroon/bracket-backend
container_name: bracket-backend
ports:
- "8400:8400"
environment:
ENVIRONMENT: "PRODUCTION"
PG_DSN: "postgresql://bracket_prod:bracket_prod@postgres:5432/bracket_prod"
CORS_ORIGINS: "http://localhost:3000" # your frontend URL
JWT_SECRET: your_strong_secret_here # generate with: openssl rand -hex 32
volumes:
- ./backend/static:/app/static
restart: unless-stopped
depends_on:
postgres:
condition: service_healthy

STEPS TO APPLY

1. docker compose down
2. rm -rf ./postgres
3. Update docker-compose.yml as shown above
4. docker compose up -d
5. docker compose logs -f bracket-backend
   (wait for "Application startup complete" — no migration errors)
6. Open the app and try to login

[ypkoba]

Unfortanly the migration error is still there.

module = load_module_py(module_id, path)

File "/app/.venv/lib/python3.14/site-packages/alembic/util/pyfiles.py", line 136, in load_module_py
spec.loader.exec_module(module) # type: ignore
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "", line 759, in exec_module
File "", line 491, in _call_with_frames_removed
File "/app/alembic/env.py", line 48, in
run_migrations_online()
~~~~~~~~~~~~~~~~~~~~~^^
File "/app/alembic/env.py", line 40, in run_migrations_online
context.run_migrations()
~~~~~~~~~~~~~~~~~~~~~~^^
File "", line 8, in run_migrations
File "/app/.venv/lib/python3.14/site-packages/alembic/runtime/environment.py", line 946, in run_migrations
self.get_context().run_migrations(**kw)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
File "/app/.venv/lib/python3.14/site-packages/alembic/runtime/migration.py", line 627, in run_migrations
step.migration_fn(**kw)
~~~~~~~~~~~~~~~~~^^^^^^
File "/app/alembic/versions/274385f2a757_add_on_delete_cascade_to_users_x_clubs.py", line 20, in upgrade
op.drop_index("ix_users_email", table_name="users")
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 8, in drop_index
File "", line 3, in drop_index
File "/app/.venv/lib/python3.14/site-packages/alembic/operations/ops.py", line 1142, in drop_index
return operations.invoke(op)
~~~~~~~~~~~~~~~~~^^^^
File "/app/.venv/lib/python3.14/site-packages/alembic/operations/base.py", line 441, in invoke
return fn(self, operation)
File "/app/.venv/lib/python3.14/site-packages/alembic/operations/toimpl.py", line 121, in drop_index
operations.impl.drop_index(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
operation.to_index(operations.migration_context),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
**kw,
^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/alembic/ddl/impl.py", line 464, in drop_index
self._exec(schema.DropIndex(index, **kw))
~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/alembic/ddl/impl.py", line 246, in _exec
return conn.execute(construct, params)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1419, in execute
return meth(
self,
distilled_parameters,
execution_options or NO_OPTIONS,
)
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/sql/ddl.py", line 187, in _execute_on_connection
return connection._execute_ddl(
~~~~~~~~~~~~~~~~~~~~~~~^
self, distilled_params, execution_options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1530, in _execute_ddl
ret = self._execute_context(
dialect,
...<4 lines>...
compiled,
)
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1846, in _execute_context
return self._exec_single_context(
~~~~~~~~~~~~~~~~~~~~~~~~~^
dialect, context, statement, parameters
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1986, in _exec_single_context
self._handle_dbapi_exception(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
e, str_statement, effective_parameters, cursor, context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 2355, in _handle_dbapi_exception
raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context
self.dialect.do_execute(
~~~~~~~~~~~~~~~~~~~~~~~^
cursor, str_statement, effective_parameters, context
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/app/.venv/lib/python3.14/site-packages/sqlalchemy/engine/default.py", line 951, in do_execute
cursor.execute(statement, parameters)
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedObject) index "ix_users_email" does not exist
[SQL:
DROP INDEX ix_users_email]
(Background on this error at: https://sqlalche.me/e/20/f405)
[2026-05-28 21:20:00 +0000] [10] [ERROR] Application startup failed. Exiting.
[2026-05-28 21:20:00 +0000] [10] [INFO] Worker exiting (pid: 10)
[2026-05-28 21:20:01 +0000] [9] [ERROR] Worker (pid:10) exited with code 3
[2026-05-28 21:20:01 +0000] [9] [ERROR] Shutting down: Master
[2026-05-28 21:20:01 +0000] [9] [ERROR] Reason: Worker failed to boot.

[CarlosOliveira-23]

Hey! Good news — the error has actually changed, which means we made progress.
The DNS/connection issue from before is gone. Now we're dealing with something
different and more straightforward.

Here's what's happening:

The migration "274385f2a757" is trying to drop an index called "ix_users_email",
but that index doesn't exist in your database. This usually happens when the
Alembic migration history gets out of sync with what's actually in the database
— pretty common when setting things up or after a fresh install.

---

THE QUICKEST FIX (recommended):

Just tell Alembic to mark that migration as "already done" without actually
running it. Jump into your backend container and run:

alembic stamp 274385f2a757

That's it. This tells Alembic: "hey, consider this migration applied" — without
touching the database. Then restart your backend container and it should boot up
just fine.

---

ALTERNATIVE — Create the index manually:

If the stamp approach doesn't feel right to you, you can go into your Postgres
container and create the index that the migration expects to find:

CREATE INDEX IF NOT EXISTS ix_users_email ON users (email);

After that, restart the backend and the migration will run cleanly (it'll drop
the index as expected and move on).

---

ANOTHER ALTERNATIVE — Check your current state and reapply:

If you want to do it "the proper way", you can check where your database
currently stands and work from there:

alembic current        <-- shows which migration is applied
alembic upgrade head   <-- applies everything up to the latest

---

Honestly, just go with the stamp command first. It's the fastest path and very
unlikely to cause any issues. Let me know what happens after you try it!

[ypkoba]

When i type the following command:

docker exec -it bracket-backend bash

this is the response:

OCI runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH

inside the database i got the following error:
ERROR: relation "users" does not exist

[ypkoba]

this is the log from the backend.
bracket-backend | )
bracket-backend | File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1218, in _connect
bracket-backend | conn = await _connect_addr(
bracket-backend | ^^^^^^^^^^^^^^^^^^^^
bracket-backend | ...<6 lines>...
bracket-backend | )
bracket-backend | ^
bracket-backend | File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1054, in _connect_addr
bracket-backend | return await __connect_addr(params, True, *args)
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 1099, in __connect_addr
bracket-backend | tr, pr = await connector
bracket-backend | ^^^^^^^^^^^^^^^
bracket-backend | File "/app/.venv/lib/python3.14/site-packages/asyncpg/connect_utils.py", line 969, in _create_ssl_connection
bracket-backend | tr, pr = await loop.create_connection(
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | ...<2 lines>...
bracket-backend | host, port)
bracket-backend | ^^^^^^^^^^^
bracket-backend | File "/usr/local/lib/python3.14/asyncio/base_events.py", line 1119, in create_connection
bracket-backend | infos = await self._ensure_resolved(
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | (host, port), family=family,
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | type=socket.SOCK_STREAM, proto=proto, flags=flags, loop=self)
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | File "/usr/local/lib/python3.14/asyncio/base_events.py", line 1505, in _ensure_resolved
bracket-backend | return await loop.getaddrinfo(host, port, family=family, type=type,
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | proto=proto, flags=flags)
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | File "/usr/local/lib/python3.14/asyncio/base_events.py", line 936, in getaddrinfo
bracket-backend | return await self.run_in_executor(
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | None, getaddr_func, host, port, family, type, proto, flags)
bracket-backend | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 86, in run
bracket-backend | result = ctx.run(self.task)
bracket-backend | File "/usr/local/lib/python3.14/concurrent/futures/thread.py", line 73, in run
bracket-backend | return fn(*args, **kwargs)
bracket-backend | File "/usr/local/lib/python3.14/socket.py", line 983, in getaddrinfo
bracket-backend | for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
bracket-backend | ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
bracket-backend | socket.gaierror: [Errno -2] Name does not resolve
bracket-backend |
bracket-backend | [2026-05-29 19:39:14 +0000] [10] [ERROR] Application startup failed. Exiting.
bracket-backend | [2026-05-29 19:39:14 +0000] [10] [INFO] Worker exiting (pid: 10)
bracket-backend | [2026-05-29 19:39:14 +0000] [9] [ERROR] Worker (pid:10) exited with code 3
bracket-backend | [2026-05-29 19:39:14 +0000] [9] [ERROR] Shutting down: Master
bracket-backend | [2026-05-29 19:39:14 +0000] [9] [ERROR] Reason: Worker failed to boot.

[CarlosOliveira-23]

---

WHAT THE OFFICIAL docker-compose.yml LOOKS LIKE

Looking at the official Bracket repository, the correct structure is:

services:
bracket-backend:
container_name: bracket-backend
environment:
PG_DSN: postgresql://bracket_dev:bracket_dev@postgres:5432/bracket_dev
image: ghcr.io/evroon/bracket-backend
networks:
- bracket_lan
...

postgres:                        <-- the DB service is named "postgres"
  environment:
    POSTGRES_DB: bracket_dev
    POSTGRES_PASSWORD: bracket_dev
    POSTGRES_USER: bracket_dev
  image: postgres
  networks:
    - bracket_lan
  ...

networks:
bracket_lan:

KEY POINT: The database hostname in PG_DSN must be "postgres" (the service name).
NOT "db", NOT "localhost", NOT "127.0.0.1" — it must be "postgres".

---

DIAGNOSIS CHECKLIST — RUN THESE COMMANDS FIRST

1. See what hostname your backend is actually trying to connect to:

   docker compose logs backend | grep -i "postgresql|postgres|PG_DSN|DSN"

2. See all running services and their names:

   docker compose ps

3. Check what network your containers are on:

   docker inspect bracket-backend | grep -A 20 '"Networks"'
   docker inspect | grep -A 20 '"Networks"'

   Both containers MUST be on the same network. If one shows "bracket_lan"
   and the other shows "bridge", that is your problem.

---

THE FIX — COMPLETE WORKING docker-compose.yml

Replace your docker-compose.yml with this (copy exactly):

---------- START OF docker-compose.yml ----------

services:
bracket-backend:
container_name: bracket-backend
environment:
PG_DSN: postgresql://bracket_dev:bracket_dev@postgres:5432/bracket_dev
image: ghcr.io/evroon/bracket-backend
networks:
- bracket_lan
ports:
- 8400:8400
restart: unless-stopped
depends_on:
postgres:
condition: service_healthy
volumes:
- ./backend/static:/app/static

bracket-frontend:
container_name: bracket-frontend
environment:
VITE_API_BASE_URL: http://localhost:8400
VITE_HCAPTCHA_SITE_KEY: 10000000-ffff-ffff-ffff-000000000001
image: ghcr.io/evroon/bracket-frontend
ports:
- 3000:3000
restart: unless-stopped

postgres:
container_name: bracket-postgres
environment:
POSTGRES_DB: bracket_dev
POSTGRES_PASSWORD: bracket_dev
POSTGRES_USER: bracket_dev
image: postgres:15
networks:
- bracket_lan
restart: always
healthcheck:
test: ["CMD-SHELL", "pg_isready -U bracket_dev -d bracket_dev"]
interval: 5s
timeout: 5s
retries: 10
volumes:
- postgres_data:/var/lib/postgresql/data

networks:
bracket_lan:

volumes:
postgres_data:

---------- END OF docker-compose.yml ----------

CRITICAL DIFFERENCES FROM WHAT YOU LIKELY HAVE:

• PG_DSN uses "@postgres:5432" — the hostname is the service name "postgres"
• Both bracket-backend and postgres are on the same network: bracket_lan
• "depends_on" with healthcheck ensures postgres is READY before backend starts
• A named volume "postgres_data" is used so data persists across restarts

---

STEP-BY-STEP RECOVERY PROCEDURE

Step 1 — Stop everything and remove containers:

 docker compose down

(Do NOT use -v yet, to preserve your data if you have any)

Step 2 — Replace docker-compose.yml with the version above.

Step 3 — Pull the latest images:

 docker compose pull

Step 4 — Start only the database and wait for it to be healthy:

 docker compose up -d postgres
 docker compose logs -f postgres

Wait until you see: "database system is ready to accept connections"
Then press Ctrl+C.

Step 5 — Start the backend:

 docker compose up -d bracket-backend
 docker compose logs -f bracket-backend

Wait until you see: "Application startup complete"
Then press Ctrl+C.

Step 6 — If the backend starts successfully, run migrations:

 docker exec -it bracket-backend sh -c "cd /app && alembic upgrade head"

If alembic is not in PATH, try:

 docker exec -it bracket-backend sh -c "cd /app && uv run alembic upgrade head"

Step 7 — Start the frontend:

 docker compose up -d bracket-frontend

Step 8 — Verify everything is running:

 docker compose ps

All three services should show "running" or "Up".

Step 9 — Access Bracket at http://localhost:3000
Default credentials:
Username: test@example.org
Password: aeGhoe1ahng2Aezai0Dei6Aih6dieHoo

---

COMMON MISTAKES THAT CAUSE [Errno -2] Name does not resolve

MISTAKE 1: Wrong hostname in PG_DSN
Wrong: PG_DSN: postgresql://user:pass@localhost:5432/db
Wrong: PG_DSN: postgresql://user:pass@db:5432/db
Wrong: PG_DSN: postgresql://user:pass@127.0.0.1:5432/db
Correct: PG_DSN: postgresql://user:pass@postgres:5432/db
(hostname must match the service name in docker-compose.yml)

MISTAKE 2: Containers on different networks
bracket-backend on network "bracket_lan"
postgres on no network (default bridge)
--> They cannot see each other. Both must be on the same named network.

MISTAKE 3: Backend starts before postgres is ready
Fixed by the "depends_on" with healthcheck in the docker-compose.yml above.

MISTAKE 4: Using an external/custom .env file that overrides PG_DSN
If you have a prod.env or .env file, check it for a PG_DSN or DATABASE_URL
line and make sure it also uses "postgres" as the hostname.

---

IF YOU STILL GET ERRORS AFTER THIS

Run this command and send the output:

 docker compose config

This shows the final resolved docker-compose configuration with all env vars
substituted, so you can see exactly what the backend is receiving.

Also run:

 docker network ls
 docker network inspect bracket_lan

To verify both containers are members of the same network.

[ypkoba]

so every container is heathy, however when I try to login I get an internal server error.
Here is the output you asked for.
docker compose config

name: bracket
services:
bracket-backend:
container_name: bracket-backend
depends_on:
postgres:
condition: service_healthy
required: true
environment:
PG_DSN: postgresql://bracket_dev:bracket_dev@postgres:5432/bracket_dev
image: ghcr.io/evroon/bracket-backend
networks:
bracket_lan: null
ports:
- mode: ingress
target: 8400
published: "8400"
protocol: tcp
restart: unless-stopped
volumes:
- type: bind
source: /home/falken/bracket/backend/static
target: /app/static
bind: {}
bracket-frontend:
container_name: bracket-frontend
environment:
VITE_API_BASE_URL: http://localhost:8400
VITE_HCAPTCHA_SITE_KEY: 10000000-ffff-ffff-ffff-000000000001
image: ghcr.io/evroon/bracket-frontend
networks: #<-- added this so it would get the same network
bracket_lan: null
ports:
- mode: ingress
target: 3000
published: "3003" # <-- had to change it because of a differnt service (openweb ui)
protocol: tcp
restart: unless-stopped
postgres:
container_name: bracket-postgres
environment:
POSTGRES_DB: bracket_dev
POSTGRES_PASSWORD: bracket_dev
POSTGRES_USER: bracket_dev
healthcheck:
test:
- CMD-SHELL
- pg_isready -U bracket_dev -d bracket_dev
timeout: 5s
interval: 5s
retries: 10
image: postgres:15
networks:
bracket_lan: null
restart: always
volumes:
- type: volume
source: postgres_data
target: /var/lib/postgresql/data
volume: {}
networks:
bracket_lan:
name: bracket_bracket_lan
volumes:
postgres_data:
name: bracket_postgres_data

docker network ls
docker network inspect bracket_lan

NETWORK ID NAME DRIVER SCOPE
0fe9dd10bf0f bracket_bracket_lan bridge local
a3fcd8ef4cc9 bridge bridge local
918ed37a6ce1 falken_default bridge local
f77a6cd83a71 host host local
5f2fc41cb8dc local-ai-packaged_demo bridge local
6a6561bce10c none null local
8c7fe08ec6c8 webui_default bridge local
[]
Error response from daemon: network bracket_lan not found
docker network inspect bracket_bracket_lan
[
{
"Name": "bracket_bracket_lan",
"Id": "0fe9dd10bf0f072317d5cffeff0b115b24ad63f7504a9cc92dd2e85362bed1be",
"Created": "2026-05-30T06:32:23.419608903+01:00",
"Scope": "local",
"Driver": "bridge",
"EnableIPv4": true,
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "172.21.0.0/16",
"Gateway": "172.21.0.1"
}
]
},
"Internal": false,
"Attachable": false,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Options": {},
"Labels": {
"com.docker.compose.config-hash": "bea98000201db73dd9d1dcbd40aa217b99a9b581256900dbe0b29de37717bdd7",
"com.docker.compose.network": "bracket_lan",
"com.docker.compose.project": "bracket",
"com.docker.compose.version": "5.1.4"
},
"Containers": {
"2ea9a5b8d735b8e0e8fda825e41fcc8697cf72d8eaf16c60af420f5870e551de": {
"Name": "bracket-frontend",
"EndpointID": "2c4e303072dec6970c2020e523dd001cb8111451e1bef4b90e97c6655d54b973",
"MacAddress": "fe:48:be:e6:20:73",
"IPv4Address": "172.21.0.4/16",
"IPv6Address": ""
},
"3ed69ca43e475031623df535bbd91600e40e69c0a45cd06cc090dbe8211b9c5e": {
"Name": "bracket-postgres",
"EndpointID": "0dfaf6164d8f7ea01912bfe1c76f0e580a8e8493f8f2fa029dbb7c79390d015f",
"MacAddress": "5e:97:1b:97:0f:f4",
"IPv4Address": "172.21.0.2/16",
"IPv6Address": ""
},
"64051e69fac3569ed6284658416d1afdf982f6a6c62df5675f0de203e598e3b7": {
"Name": "bracket-backend",
"EndpointID": "a3d1b1a541cfdd7ee32745ba0ecc23f41aefce90f5ffa703dc4635c7f7b7ae5f",
"MacAddress": "a6:49:d8:ed:07:9a",
"IPv4Address": "172.21.0.3/16",
"IPv6Address": ""
}
},
"Status": {
"IPAM": {
"Subnets": {
"172.21.0.0/16": {
"IPsInUse": 6,
"DynamicIPsAvailable": 65530
}
}
}
}
}
]

[CarlosOliveira-23]

GOOD NEWS: Your network is 100% correct.
All three containers are on bracket_bracket_lan and can reach each other:

• bracket-backend 172.21.0.3
• bracket-postgres 172.21.0.2
• bracket-frontend 172.21.0.4

THE PROBLEM NOW

"Internal server error" on login = the database is empty. Tables like "users"
do not exist because migrations have never been run.

The backend connects to postgres successfully, but when it tries to query a
table, it finds nothing there.

---

THE FIX — RUN MIGRATIONS + SEED THE DATABASE

Step 1 — Run database migrations (creates all tables):

docker exec -it bracket-backend sh -c "cd /app && alembic upgrade head"

If that fails, try with uv:

docker exec -it bracket-backend sh -c "cd /app && uv run alembic upgrade head"

You should see output like:
INFO [alembic.runtime.migration] Running upgrade -> xxxx, initial migration
INFO [alembic.runtime.migration] Running upgrade xxxx -> yyyy, ...
...

Step 2 — Seed the database with the default user and test data:

docker exec -it bracket-backend sh -c "cd /app && uv run --no-dev ./cli.py create-dev-db"

This creates the default login:
Username: test@example.org
Password: aeGhoe1ahng2Aezai0Dei6Aih6dieHoo

Step 3 — Restart the backend:

docker compose restart bracket-backend

Step 4 — Try logging in at http://localhost:3003
(You changed the frontend port to 3003, remember)

Username: test@example.org
Password: aeGhoe1ahng2Aezai0Dei6Aih6dieHoo

---

IF STEP 1 GIVES "alembic: not found"

Try these alternatives one by one until one works:

docker exec -it bracket-backend sh -c "cd /app && python -m alembic upgrade head"

docker exec -it bracket-backend sh -c "cd /app && .venv/bin/alembic upgrade head"

docker exec -it bracket-backend sh -c "cd /app && uv run alembic upgrade head"

---

IF STEP 2 GIVES "cli.py: not found" OR SIMILAR

Try:

docker exec -it bracket-backend sh -c "cd /app && uv run ./cli.py create-dev-db"

docker exec -it bracket-backend sh -c "cd /app && python cli.py create-dev-db"

docker exec -it bracket-backend sh -c "ls /app"

(the last command lists the files so you can see what's available)

---

VERIFY MIGRATIONS WORKED

Connect to the database and check tables exist:

docker exec -it bracket-postgres psql -U bracket_dev -d bracket_dev -c "\dt"

You should see a list of tables including: users, tournaments, players, etc.
If you see "Did not find any relations." then migrations did not run correctly.

---

FULL SUMMARY OF YOUR JOURNEY SO FAR

v1 - socket.gaierror [Errno -3]: DNS failure, wrong hostname in PG_DSN
v2 - socket.gaierror [Errno -2]: Containers on different networks
v3 - Internal server error on login: Migrations never ran, tables don't exist
--> YOU ARE HERE. Fix: run alembic upgrade head + create-dev-db

[ypkoba]

At step one I got the 'alambic not found'.
So i uded the second command you reccommened:
docker exec -it bracket-backend sh -c "cd /app && uv run alembic upgrade head"
And I get the following error.

x Failed to build pyrefly==0.46.0
|-> The build backend returned an error
-> Call to maturin.build_wheel` failed (exit status: 1)

  [stdout]
  Rust not found, installing into a temporary directory

  [stderr]
  Python reports SOABI: cpython-314-aarch64-linux-musl
  Computed rustc target triple: aarch64-unknown-linux-musl
  Installation directory: /home/bracket/.cache/puccinialin
  Rustup already downloaded
  Installing rust to /home/bracket/.cache/puccinialin/rustup
  warn: It looks like you have an existing rustup settings file at:
  warn: /home/bracket/.cache/puccinialin/rustup/settings.toml
  warn: Rustup will install the default toolchain as specified in the settings file,
  warn: instead of the one inferred from the default host triple.
  info: profile set to minimal
  info: setting default host triple to aarch64-unknown-linux-musl
  warn: Updating existing toolchain, profile choice will be ignored
  info: syncing channel updates for stable-aarch64-unknown-linux-musl
  info: default toolchain set to stable-aarch64-unknown-linux-musl
  warn: no default linker (`cc`) was found in your PATH
  warn: many Rust crates require a system C toolchain to build
  Checking if cargo is installed
  Error loading shared library libgcc_s.so.1: No such file or directory (needed by
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo)
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetIPInfo: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetDataRelBase: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetRegionStart: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_SetGR: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_FindEnclosingFunction: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetTextRelBase: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_Resume: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_DeleteException: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_RaiseException: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetIP: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_Backtrace: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetCFA: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_GetLanguageSpecificData: symbol not found
  Error relocating
  /home/bracket/.cache/puccinialin/rustup/toolchains/nightly-2025-09-14-aarch64-unknown-linux-musl/bin/cargo:
  _Unwind_SetIP: symbol not found
  Traceback (most recent call last):
    File "<string>", line 11, in <module>
      wheel_filename = backend.build_wheel("/home/bracket/.cache/uv/builds-v0/.tmpGquzbB", {}, None)
    File "/home/bracket/.cache/uv/builds-v0/.tmpWJxVkV/lib/python3.14/site-packages/maturin/__init__.py", line
  145, in build_wheel
      return _build_wheel(wheel_directory, config_settings, metadata_directory)
    File "/home/bracket/.cache/uv/builds-v0/.tmpWJxVkV/lib/python3.14/site-packages/maturin/__init__.py", line
  118, in _build_wheel
      env = _get_env()
    File "/home/bracket/.cache/uv/builds-v0/.tmpWJxVkV/lib/python3.14/site-packages/maturin/__init__.py", line
  83, in _get_env
      extra_env = setup_rust()
    File "/home/bracket/.cache/uv/builds-v0/.tmpWJxVkV/lib/python3.14/site-packages/puccinialin/_setup_rust.py",
  line 152, in setup_rust
      check_call([cargo, "--version"], env={**os.environ, **extra_env})
      ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/lib/python3.14/subprocess.py", line 419, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['/home/bracket/.cache/puccinialin/cargo/bin/cargo', '--version']'
  returned non-zero exit status 127.

  hint: This usually indicates a problem with the package or the build environment.

help: pyrefly (v0.46.0) was included because bracket-backend:dev (v0.0.1) depends on pyrefly

[ypkoba]

So I have it running on a raspberi pi under local host in the web browser.
As soon as i want to connect from a different laptop/pc i get a internal server error.
The browser gives the following error:
You should call navigate() in a React.useEffect(), not when your component is first rendered. index-BiIOi_9h.js:57:10843 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8400/clubs. (Reason: CORS request did not succeed). Status code: (null). 2 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8400/tournaments?filter_=OPEN. (Reason: CORS request did not succeed). Status code: (null). 2 Password fields present on an insecure (http://) page. This is a security risk that allows user login credentials to be stolen. login Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8400/token. (Reason: CORS request did not succeed). Status code: (null).