Closed wes1993 closed 1 year ago
Hi, I have noticed a similar beheviour where images from certain devices don't want to upload. For me the problem was that the extention of the files were writen with capital letters. After renaming the files, it worked as intended. Example: video.MOV failed without any visible error messages in the GUI but video.mov worked fine. Besides renaming the files I have not found a way to upload the version with the capitals. I hope this helps you.
Look like the server timeout. How much resources did you allocate for Immich?
Hello @alextran1502 and @gotje for your replies :-D I have some files that is in capital letter, but i have seen in the changlog that with new update this problem is fixed.
@alextran1502 i have configured immich in docker on my server running debian this are the specs: CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz RAM: 16 Gb GPU: GeForce GTX 850M SSD: 128 GB
Can you see if the file is in the main timeline? I bet it imported correctly.
You can also solve this by connecting to the immich-server container directly, instead of using Nginx. This avoids the Nginx timeouts you are hitting from Nginx.
I am in a similar boat where a large import of an existing library fails for specific files (most of them seem to be large-ish .MOV clips). As suggested by @jrasm91, one of the files that keep on failing is indeed imported successfully and is playable within Immich.
However, how can I be certain that the same is true for all files that the import has failed for? According to immich-cli, there are close to 3000 images/videos that have "failed" and I couldn't possibly check them all:
Indexing complete, found 38373 local assets
Comparing local assets with those on the Immich instance...
A total of 2833 assets will be uploaded to the server
You can avoid using Nginx and hit the API server directly, or you could increase the Nginx request timeout, or you could upload without --import, or you could do some database queries / scripting to compare the file lists, or you could wait for the CLI to be improved and fix these types of issues or log errors to a file for easier verification/action.
Hello, I have the same issue of 504 timeout with around 800 mp4 files. I tried using the API server directly by exposing port 3001 to the host. but the CLI upload command is not able to connect to the server
immich upload --key dp4oouSv9F2CSkj5aJu5JgiHzia53SkknNKhcKGQoA --server http://192.168.2.246:3001/api /DATA/Gallery/Events --recursive --import --album
Checking connectivity with Immich instance...
Error connecting to server - check server address and port
whereas it works fine with the proxy
immich upload --key dp4oouSv9F2CSkj5aJu5JgiHzia53SkknNKhcKGQoA --server http://192.168.2.246:2283/api /DATA/Gallery/Events --recursive --import --album
port seems well opened: nc -zv 192.168.2.246 3001 photos.somedomain.com [192.168.2.246] 3001 (?) open curl gives a 404 on /api for both 3001 and 2283
Any idea ? Thanks a lot for any help
@floco 3001 is the internal port used for docker container communication. You should use port 2283
Hello, I have the same issue of 504 timeout with around 800 mp4 files. I tried using the API server directly by exposing port 3001 to the host. but the CLI upload command is not able to connect to the server
immich upload --key dp4oouSv9F2CSkj5aJu5JgiHzia53SkknNKhcKGQoA --server http://192.168.2.246:3001/api /DATA/Gallery/Events --recursive --import --album Checking connectivity with Immich instance... Error connecting to server - check server address and port
whereas it works fine with the proxy
immich upload --key dp4oouSv9F2CSkj5aJu5JgiHzia53SkknNKhcKGQoA --server http://192.168.2.246:2283/api /DATA/Gallery/Events --recursive --import --album
port seems well opened: nc -zv 192.168.2.246 3001 photos.somedomain.com [192.168.2.246] 3001 (?) open curl gives a 404 on /api for both 3001 and 2283
Any idea ? Thanks a lot for any help
You can use it, but when you hit the immich-server directly you need to remove /api
from the url
Thanks a lot @jrasm91 😀, below did the trick:
You can use it, but when you hit the immich-server directly you need to remove /api from the url
immich upload --key dp4oouSv9F2CSkj5aJu5JgiHzia53SkknNKhcKGQoA --server http://192.168.2.246:3001
Will report back if that solves the timeouts, importing now ...
@alextran1502
3001 is the internal port used for docker container communication. You should use port 2283
Thanks, I indeed usually use tcp/2283 from the proxy but I did map the immich server internal docker port tcp/3001 to tcp/3001 on the host to test bypassing the proxy for the import.
Import ran 100% successfully (no more 504). Thanks @jrasm91 ! Might be good adding a note to https://documentation.immich.app/docs/features/read-only-gallery ? Thanks again again Alex and all contributors for this great project !
The bug
When i try to import my existing gallery many files are not imported, i will attach the log below.
The OS that Immich Server is running on
Debian GNU/Linux 11 (bullseye)
Version of Immich Server
v1.66.1
Version of Immich Mobile App
v1.66.1
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
The LOG: