iOS backup is extremely slow on v1.142.1
Hi everyone, I just set up Immich v1.142.1 on my server and I'm trying to back up my photos from my iPhone 16 Pro (iOS 18.7). When I start the backup it'll upload 10-20 assets and then it comes to a complete halt unless I close the app and open it again. I'm keeping the app in the foreground with the screen on. I'm not sure why that's happening because I was able to sync all my photos to my Seafile instance on the same server through their iOS app and it was much faster (5200 photos backed up in 1 hour).
I have set the max request body size in Traefik to 2 GiB but that doesn't help.
Would appreciate any help!
9 Replies
:wave: Hey @icetwy,
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.I should note that I'm running Immich in a rootless Podman pod (just like Seafile) on Debian bookworm. The server has 2x 450 GB NVMe SSD in RAID1 and 32 GB RAM, nothing else is running on it at the moment. My iPhone is also getting pretty hot while backing up.
~/.config/containers/systemd/immich.pod
~/.config/containers/systemd/immich-redis.container
~/.config/containers/systemd/immich-database
~/.config/containers/systemd/immich-machine-learning.container
~/.config/containers/systemd/immich-server.container
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
Okay, I disabled the Beta timeline feature and it's much faster now
Do you have your photos and videos all in iCloud?
Yes they are all in iCloud
I was able to upload all of my photos & videos very quickly after I turned the beta timeline off, and my phone didn’t get hot either. Not sure what the new timeline is but it doesn’t seem to be handling backups very well.
The old version run upload sequentially and it doesn’t hash the assets, so if you switch phone, you will have to reupload them all. The new version run upload in parallel and it needs to hash the assets before running the upload. In the latest release, we improve the hashing process, especially for iCloyd users
Ah, dang, thanks for the info. I can see that it’s uploading in parallel but I have no clue why it’s getting stuck early on.
It was waiting for the assets to be hashed to it can matches with the server