starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-07-16 05:53:57 +03:00
Code Issues 396 Packages Projects Releases 21 Wiki Activity

[Bug]: DB connection failure - new deployment #826

New Issue
Closed
opened 2026-02-04 21:26:07 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 21:26:07 +03:00
Owner
Copy Link

Originally created by @alaricljs on GitHub (Sep 30, 2025).

Where is the problem occurring?

Container init

What browsers are you seeing the problem on?

No response

Current behavior

The container fails to start:

kanban_planka.1.oz74jonqdd8a@pmox1    | /app/node_modules/pg-protocol/dist/parser.js:285
kanban_planka.1.oz74jonqdd8a@pmox1    |         const message = name === 'notice' ? new messages_1.NoticeMessage(length, messageValue) : new messages_1.DatabaseError(messageValue, length, name);
kanban_planka.1.oz74jonqdd8a@pmox1    |                                                                                                  ^
kanban_planka.1.oz74jonqdd8a@pmox1    | 
kanban_planka.1.oz74jonqdd8a@pmox1    | error: password authentication failed for user "planka"

Using a bare test container to validate the DB & creds are not at issue:
❯ docker service create --name test --secret planka_db_password --network db_backend alpine:latest sleep 99999
❯ docker exec -it test.1.rmg9tu9rf53podp7sfiq05wiy /bin/sh
/ # apk add postgresql-client
fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/main/x86_64/APKINDEX.tar.gz
...  removed extraneous info ...
* Setting postgresql17 as the default version
OK: 12 MiB in 24 packages
/ # psql postgresql://planka:$(cat /run/secrets/planka_db_password)@postgres/planka
psql (17.6, server 15.14)
Type "help" for help.

planka=> 
\q
/ #

Hardcoding the password makes the container spin up with zero log output.

Desired behavior

Container to start.

Steps to reproduce

Basically stock compose file w/ env (per the example in the file):
- DATABASE_PASSWD__FILE=/run/secrets/planka_db_password
- DATABASE_URL=postgresql://planka:$${DATABASE_PASSWORD}@postgres/planka

Stand it up in Docker Swarm mode:
docker stack deploy --prune -d -c docker-compose.yml $(basename $(pwd))

Other information

The password is alphanumeric because it's in a URI, so not breaking URI encoding or shell behavior.

Originally created by @alaricljs on GitHub (Sep 30, 2025). ### Where is the problem occurring? Container init ### What browsers are you seeing the problem on? _No response_ ### Current behavior The container fails to start: ``` kanban_planka.1.oz74jonqdd8a@pmox1 | /app/node_modules/pg-protocol/dist/parser.js:285 kanban_planka.1.oz74jonqdd8a@pmox1 | const message = name === 'notice' ? new messages_1.NoticeMessage(length, messageValue) : new messages_1.DatabaseError(messageValue, length, name); kanban_planka.1.oz74jonqdd8a@pmox1 | ^ kanban_planka.1.oz74jonqdd8a@pmox1 | kanban_planka.1.oz74jonqdd8a@pmox1 | error: password authentication failed for user "planka" ``` ``` Using a bare test container to validate the DB & creds are not at issue: ❯ docker service create --name test --secret planka_db_password --network db_backend alpine:latest sleep 99999 ❯ docker exec -it test.1.rmg9tu9rf53podp7sfiq05wiy /bin/sh / # apk add postgresql-client fetch https://dl-cdn.alpinelinux.org/alpine/v3.22/main/x86_64/APKINDEX.tar.gz ... removed extraneous info ... * Setting postgresql17 as the default version OK: 12 MiB in 24 packages / # psql postgresql://planka:$(cat /run/secrets/planka_db_password)@postgres/planka psql (17.6, server 15.14) Type "help" for help. planka=> \q / # ``` Hardcoding the password makes the container spin up with zero log output. ### Desired behavior Container to start. ### Steps to reproduce Basically stock compose file w/ env (per the example in the file): - DATABASE_PASSWD__FILE=/run/secrets/planka_db_password - DATABASE_URL=postgresql://planka:$${DATABASE_PASSWORD}@postgres/planka Stand it up in Docker Swarm mode: `docker stack deploy --prune -d -c docker-compose.yml $(basename $(pwd))` ### Other information The password is alphanumeric because it's in a URI, so not breaking URI encoding or shell behavior.
OVERLORD commented 2026-02-04 21:26:25 +03:00
Author
Owner
Copy Link

@alaricljs commented on GitHub (Sep 30, 2025):

Erk, found it... DATABASE_PASSWD__FILE where'd the OR go? I'll never tell.

@alaricljs commented on GitHub (Sep 30, 2025): Erk, found it... DATABASE_PASSWD__FILE where'd the OR go? I'll never tell.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#826
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?