Immich not woring after update 1.143.1
I have a backup on 1.131.3!
After update and restart can't access immich on :2283.
immich is runnig on server like I can see!? Se attachment!
26 Replies
:wave: Hey @lavijadje,
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. :ballot_box_with_check: 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.Could you check / post your logs?
Seems you jumped too far, there were breaking changes between 1.131 and 1.143, so you should update to an intermediate version.
See if there is "Invalid upgrade path" error in the log. Then follow https://docs.immich.app/errors/#typeorm-upgrade
Recent similar thread https://discord.com/channels/979116623879368755/1421276180241453107
Errors | Immich
TypeORM Upgrade
where do I find the logs? how do I do that?
or how do I uppdate to v1.132.3?
i have changed in yml file the "image"-line to:
name: immich
services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:1.132.3
but I'm getting an error:
lavijadje@lavijadje-HP-ZBook-15v-G5:~/immich-app$ docker compose pull [+] Pulling 4/4
ā redis Pulled 0.4s ā immich-server Error manifest unknown 0.7s ā database Pulled 0.2s ā immich-machine-learning Pulled 0.6s Error response from daemon: manifest unknown
ā redis Pulled 0.4s ā immich-server Error manifest unknown 0.7s ā database Pulled 0.2s ā immich-machine-learning Pulled 0.6s Error response from daemon: manifest unknown
where do I find the logs? how do I do that?See the auto-posts from bot. "Container Logs" section has a link to docs.
Error response from daemon: manifest unknownCheck version in compose, it should be
v1.132.3why 1.132.3 @Sergey Katsubo ?
In my experience
v1.136.0 works best, then straight to latest@Mraedis there is that nasty
multiple primary keys for table "geodata_places" are not allowed bug when upgrading pre-1.132 to 1.136, you've seen it already. Details in https://github.com/immich-app/immich/pull/22033
Apart from that, yeah, 136 would be the best.[Pull Request] chore(docs): TypeORM error: force recommend v1.132.3 and avoid v1.136 (immich-app/immich#22033)
Ah right, but also if they have vectorchord 0.4.3 then v1.133.0 at least complains about it being >0.4, is that the same for v1.132.3 too?
Arrgh
Jammed between bugs/versions like between Scylla and Charybdis š
It really only happens if they go straight to latest with included compose š
help me downgrade to working version, how do I do that!?
in your env file, put
IMMICH_VERSION=v1.132.3 for instance
then docker compose pull and docker compose up -dchanged to 1.132.3 version in env file, pulled and started immich, but still can't access localy!?
ssh to server works, but remote desktop has stoped working after ubuntu update
I can't connect with the mobile app either!
As always, check the logs
^^ This.
Check the logs of Immich container (as described/linked in the first auto-comment from bot right after your initial post). Are there errors about database extensions in logs? Please post your logs.
Most likely you need to use compose file from v1.132.3 as well. At a minimum, the
database: service section <- if there are DB-related errors. (Your current compose uses postgres with vectorchord0.4.3 which is too new for v1.132.3)
After you have up and running v1.132.3, follow https://docs.immich.app/install/upgrading/Upgrading | Immich
Immich is currently under heavy development, which means you can expect breaking changes and bugs. You should read the release notes prior to updating and take special care when using automated tools like Watchtower.
ERROR [Api:StorageService] Failed to read upload/encoded-video/.immichThen it makes sense to revert
immich-server service section as well to 1.132.3. At minimum, in the volumes
${UPLOAD_LOCATION}:/data -> ${UPLOAD_LOCATION}:/usr/src/app/upload
(Immich tries to find its subdirectories in upload/... but fails because recent versions / compose files switched to /data, while earlier versions such as 1.132 expects /usr/src/app/upload. Therefore the error.)
Or simply use compose from v1.132.3 release.