I
Immich•2w ago
mike

microservices worker error: Error: connect ENOENT /run/postgresql/.s.PGSQL.5432

hi, how do I fix this: 
May 28 21:24:25 nas immich[3566328]: Starting api worker
May 28 21:24:25 nas immich[3566328]: Starting microservices worker
May 28 21:24:26 nas immich[3566328]: [Nest] 3566328  - 28/05/2025, 21:24:26     LOG [Microservices:EventRepository] Initialized websocket server
May 28 21:24:26 nas immich[3566328]: microservices worker error: Error: connect ENOENT /run/postgresql/.s.PGSQL.5432, stack: Error: connect ENOENT /run/postgresql/.s.PGSQL.5432
May 28 21:24:26 nas immich[3566328]:     at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1634:16)
May 28 21:24:26 nas immich[3566328]: microservices worker exited with code 1
May 28 21:24:26 nas immich[3566328]: Killing api process
May 28 21:24:25 nas immich[3566328]: Starting api worker
May 28 21:24:25 nas immich[3566328]: Starting microservices worker
May 28 21:24:26 nas immich[3566328]: [Nest] 3566328  - 28/05/2025, 21:24:26     LOG [Microservices:EventRepository] Initialized websocket server
May 28 21:24:26 nas immich[3566328]: microservices worker error: Error: connect ENOENT /run/postgresql/.s.PGSQL.5432, stack: Error: connect ENOENT /run/postgresql/.s.PGSQL.5432
May 28 21:24:26 nas immich[3566328]:     at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1634:16)
May 28 21:24:26 nas immich[3566328]: microservices worker exited with code 1
May 28 21:24:26 nas immich[3566328]: Killing api process
5 Replies
Immich
Immich•2w ago
:wave: Hey @mike, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time). 2. :blue_square: read applicable release notes. 3. :blue_square: reviewed the FAQs for known issues. 4. :blue_square: reviewed Github for known issues. 5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed.
mike
mikeOP•2w ago
by starting postgres
Mraedis
Mraedis•2w ago
Post your compose please
mike
mikeOP•2w ago
nah sorry i figured it out already aha didn't delete the post so it shows up in search
Immich
Immich•2w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?