coop-cloud/immich
0
2
Fork 2
Code Issues 3 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Errors after upgrading to 1.4.0+v2.5.6 #6

New Issue
Open
opened 2026-03-02 20:37:46 +00:00 by notplants · 3 comments
notplants commented 2026-03-02 20:37:46 +00:00
Owner
Copy Link

after the upgrade, the app container is no longer starting, and I am seeing these errors:

app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    | PostgresError: password authentication failed for user "postgres"
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:817:22)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at handle (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:489:6)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:324:9)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at Socket.emit (node:events:508:28)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at addChunk (node:internal/streams/readable:559:12)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at Readable.push (node:internal/streams/readable:390:5)
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |     at TCP.onStreamRead (node:internal/stream_base_commons:189:23) {
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |   severity_local: 'FATAL',
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |   severity: 'FATAL',
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |   code: '28P01',
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |   file: 'auth.c',
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |   line: '343',
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |   routine: 'auth_failed'
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    | }
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    |
app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone    | Node.js v24.12.0

I guess because the db_password was now changed to be a secret?

need to debug this

after the upgrade, the app container is no longer starting, and I am seeing these errors: ``` app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | PostgresError: password authentication failed for user "postgres" app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at ErrorResponse (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:817:22) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at handle (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:489:6) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at Socket.data (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.8/node_modules/postgres/cjs/src/connection.js:324:9) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at Socket.emit (node:events:508:28) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at addChunk (node:internal/streams/readable:559:12) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at Readable.push (node:internal/streams/readable:390:5) app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | at TCP.onStreamRead (node:internal/stream_base_commons:189:23) { app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | severity_local: 'FATAL', app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | severity: 'FATAL', app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | code: '28P01', app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | file: 'auth.c', app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | line: '343', app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | routine: 'auth_failed' app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | } app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | app_autonomic_zone_app.1.pw1buurp46x4@app.autonomic.zone | Node.js v24.12.0 ``` I guess because the db_password was now changed to be a secret? need to debug this
notplants commented 2026-03-02 20:48:21 +00:00
Author
Owner
Copy Link

Commands I used to fix if anyone else runs into this:

abra app run yourdomain database -- cat /run/secrets/db_password

then

abra app run yourdomain -- psql -U postgres -c "ALTER USER postgres PASSWORD '<your_db_password>';"
Commands I used to fix if anyone else runs into this: ``` abra app run yourdomain database -- cat /run/secrets/db_password ``` then ``` abra app run yourdomain -- psql -U postgres -c "ALTER USER postgres PASSWORD '<your_db_password>';" ```
val commented 2026-03-12 02:22:01 +00:00
Owner
Copy Link

I just checked: db_secret was inserted in 1.2.0: 811fbf6f68

I didn't deploy it before, so thanks for this hint and glad you fixed it.
Perhaps we should edit the release notes of 1.2.0 with your hint?

I just checked: db_secret was inserted in 1.2.0: https://git.coopcloud.tech/coop-cloud/immich/commit/811fbf6f68db9bff8dcc240d0e98b0e1c327e8a6 I didn't deploy it before, so thanks for this hint and glad you fixed it. Perhaps we should edit the release notes of 1.2.0 with your hint?
notplants commented 2026-03-17 00:39:08 +00:00
Author
Owner
Copy Link

@val makes sense! and yes if there are not many users of this recipe than adding a release note would be the easiest way (or if we are the only users than maybe dont even need that, or folks would find this issue if they get confused)

in an ideal world, i would add an entrypoint to the container that automatically does that postgres command if its not done already, so that the migration would happen automatically (but probably only helpful if there were more users)

@val makes sense! and yes if there are not many users of this recipe than adding a release note would be the easiest way (or if we are the only users than maybe dont even need that, or folks would find this issue if they get confused) in an ideal world, i would add an entrypoint to the container that automatically does that postgres command if its not done already, so that the migration would happen automatically (but probably only helpful if there were more users)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se devydave fauno flancian Frando iexos jade javielico jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moritz nicksellen notplants p4u1 pau pharaohgraphy renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/immich#6
No description provided.
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?