#Lost all settings in immich after upgrade to to 1.89. Possible to recover?

1 messages · Page 1 of 1 (latest)

sleek hedge
#

Hello everyone, I've probably did something very stupid during upgrade faze. I went the steps according to github:

Bring down the stack with docker compose down --remove-orphans
Update the docker-compose.yml file
Remove immich-proxy service
Remove immich-web service
Expose port 2283:3001 in the immich-server service
Run docker compose pull
Bring up the stack with docker compose up -d

After that, I had to setup new admin password and I knew, something is very wrong. Immich is empty.

Any possible way to restore it now?

worldly pilotBOT
#

:wave: Hey @sleek hedge,

Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :blue_square: I have tried an incognito window, 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)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

rocky coral
#

not helpful now, but this is why i run it in proxmox in LXC and snapshot before updating just in case i need to roll back..

paper rapids
#

Did you add the name: immich line to your compose file? If so, try commenting that out

sleek hedge
#

what should be the correct procedure?

#

1.docker compose down --remove-orphans
2.docker compose up -d?

#

I am getting after that error, that there is conflict, because /container name /immich_typesense is already in use by container ID.....

#

great, thank you!. I've killed old containers, renamed them and docker compose pull & up again

#

everything works!