Re-setup on Synology: PG is not connecting
Been running for over a year, but my immich instance got borked, so tried to start-over.
I wrote the community guide for Synology set-up, but it's out of date now. So instead tried using the Portainer guide in docs. Also tried Container Manager in Synology as well as Docker compose throug the SSH - all run into the same problem. My Immich can't connect to my PG database. I've tried chatgpt/etc for help, but I'm at a loss. Spent 2 days on this - hoping I'm missing something stupid.
HAS ANYONE SUCCESSFULLY DEPLOYED 2.3.1 ON A SYNOLOGY?
Here's the error in the logs:
Error: write CONNECT_TIMEOUT database:5432
at connectTimedOut (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:257:20)
at Timeout.done [as _onTimeout] (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:1039:8)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'CONNECT_TIMEOUT',
errno: 'CONNECT_TIMEOUT',
address: 'database',
port: 5432
}
I wrote the community guide for Synology set-up, but it's out of date now. So instead tried using the Portainer guide in docs. Also tried Container Manager in Synology as well as Docker compose throug the SSH - all run into the same problem. My Immich can't connect to my PG database. I've tried chatgpt/etc for help, but I'm at a loss. Spent 2 days on this - hoping I'm missing something stupid.
HAS ANYONE SUCCESSFULLY DEPLOYED 2.3.1 ON A SYNOLOGY?
Here's the error in the logs:
Error: write CONNECT_TIMEOUT database:5432
at connectTimedOut (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:257:20)
at Timeout.done [as _onTimeout] (/usr/src/app/server/node_modules/.pnpm/postgres@3.4.7/node_modules/postgres/cjs/src/connection.js:1039:8)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'CONNECT_TIMEOUT',
errno: 'CONNECT_TIMEOUT',
address: 'database',
port: 5432
}
