After the update to the new version of v1.140.1, server not responding
Hi, I need help with my server running back again. When I run
docker compose pull
, it pulls new versions but stops at 95% with a certificate error related to Tailscale. After trying again, it worked, but now my PostgreSQL and Immich server containers keep restarting, as shown in their status. Also, I cannot access my server using Tailscale MagicDNS.
I tried to move back to the older version, which is v1.139.4, but the issue is still there. Now, I cannot run Immich.
Please bear with me as I am not a powerful user.
Details about my system. I am currently running Immich on Raspberrypi5:
Details about my storage:
15 Replies
:wave: Hey @mngo,
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. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.
your postgres looks borked
please bring down the stack and purge all the images, then re pull a fresh copy
When you say purge all images, do you actually mean to delete all the images and re-upload on a brand new database?
Asking because I have the same problem.
no? the docker image itself doesn't contain any of your data
I mean purge the docker images
not the images from within immich
on CLI it would be
docker compose down; docker image prune -a; docker compose up -d
Ahh okay. Makes sense. Thank you!!
IDK how to do it on these other platforms
I'm not the OP.
I'm running immich on Debian. This should do it. Thank you very much.
Thank you @Zeus I got it working again
This thread has been closed. To re-open, use the button below.
@Zeus Helped you. I just tagged along and solved my own issue. 😅
oh sorry I tagged the wrong person
Okay. Now only immich_server container keeps restarting as soon as I start the upload. Couple of photos get uploaded and then the container restarts.
I'll read the logs and create a new issue if needed.
Add
VIPS_NOVECTOR=1
to the .env
file and restart the stack will fix this issueThanks @Alex . I'll try that and let you know.
Amazing, This fixed my issue.