@OrezBodajoy can you try systemctl restart box ? Usually that fixes the 'Starting..' situation

@girish Thank you, I'll try writing there and let you know.

I found an solution to this issue by switching to rsync for backups (with hetzner storage box).
Since each backup is incremental, it doesn't matter how many backups are stored.
The backup size pretty much matches the app size.

Circling back after some testing.
Rsync with backblaze didn't seem to perform very well. Tho i'm not sure i had it configured correctly. It looked like it tried to sync everything each time.
Rsync set up with hetzner storage box works like a charm. Each sync after the first one is fast.

This fixed, thank you, @kubasbimbas, I appreciate it.

Indeed, I've pushed a package patch version, please check for updates on immich again and this time it contains the correct 1.117.0

I am not quite sure where those errors are from and why its a screenshot. However:

can you check if the redis container together with immich is up and running? seems to be an issue due to 1) This is an error I can reproduce and will investigate, however it has nothing to do with the admin creation issue you seem to have Looking at the folder name, this comes from the host system and not the immich app instance? Is this while uninstalling or updating the app?

I guess we first have to find a way to pre-setup necessary config variables programmatically and ideally lock only those in the UI. Currently most of the settings UI is locked once a config file exists.

Maybe you could create a feature request upstream to only lock settings in the UI which are set in the config file.

@shrey I think it might be better to just set the data directory and just disable backups for immich instead. As you know, it's still in active development and moving around files will cause things to go out of sync with the database. This will just cause unnecessary headaches if we make this configurable. It is similar to nextcloud in this aspect (whose data directory can also not be configured in Cloudron package)

For some unexplainable reasons I doubt Immich will ever be stable officially.
I’m sure it’s a real feat of development, but something puts me off it.

@privsec a quick workaround (until we have a fix) is to stop the app and take a backup. This will most likely succeed. Stopped apps cannot be backed up ...

Also see: https://docs.cloudron.io/guides/import-postgresql/ and https://docs.cloudron.io/guides/connect-postgresql/

I guess you can change the model name frmo that mentioned list in the settings and it might fetch it?

Reminder: We changed to settings file, so immich locks most of the settings UI https://docs.cloudron.io/apps/immich/#settings

yeah, i noticed some poeple requested that feature too - so i added my spam to their github page too :d

@nebulon Yes, I just ran in the admin jobs section, extract metadata. Thank you very much for your help.

This does not apply to Cloudron packages, only to the upstream composer deployment as far as I understand.

@eandwal this forum is for immich deployments on Cloudron . For other deployments, you have to contact the upstream forum - https://github.com/immich-app/immich/discussions

Hm so you have to update immich again even if it is in non-responding mode.