CLI tool stuck uploading assets
I'm trying to import my existing files into Immich but after a (several hours long) hashing and checking for duplicates process, the process seems to hang, when I --skip-hash it immediately hangs. See attached image.
Perhaps worth noting that the actual server is https instead of http (trying to import with that address now, not expecting it to work), caddy provides the valid cert (via cloudflare and DNS rewrites using adguard on my Tailnet).
Could it be that I just have to wait longer?

9 Replies
:wave: Hey @Freek,
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. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: 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.Here is the container status:
I have the most current docker-compose file (installed yesterday). I see no GitHub issues with the term "Uploading assets". I am on NixOS, installed npm with a shell.nix. Authentication reportedly works so I guess that is fine. The storage is a ZFS dataset. This is the server info:
Also worth noting, the npm cli tool is running on the server itself (where the immich instance also runs).
Ok, so it does work when logging into the https address I see now (I do run it without --skip-hash this time to save time). So this is a bug as logging in is reported as succesful, but the upload just hangs. So consider this a bug report? Or should I post this on Github as well?
You should test with HTTP, port 2283, local IP
It is currently uploading, and I think the dedup is then handled later so I'll leave it like this now, thank for the tip. Is this worth a bug report on GitHub you think?
Not without first testing with http and local port, no
Ok, sorry for any inconvenience then. It is of course weird (although my mistake!) that it reports successful login over http but then just hangs when uploading. Anyway, I just provided the wrong address in my first try.
Oh interesting
You’re saying the URL was totally incorrect but it said “logged in”..?
Can you replicate with a random address and post a new screenshot?
Not exactly, I mean, I didn't specify https but http, caddy probably redirected the login to https, but then the upload fails. One would expect both to either fail or succeed together, right?
Please show a simple example