--import working for one user and not another
I tried not to ask for help but I can't figure this out.
I have two users on immich. setup was done using portainer on casaOS.
one directory per user, both in same dir, mounted locally from NAS using nfs.
configured same way (with exception of path) in:
- user option within Immich app
- docker-compose
one user (wife) successfully imports all photos from directory
my user fails at:
Comparing local assets with those on the Immich instance...
Error getting device's uploaded assets
Error: socket hang up
at connResetException (node:internal/errors:720:14)
at Socket.socketOnEnd (node:_http_client:519:23)
at Socket.emit (node:events:526:35)
at endReadableNT (node:internal/streams/readable:1376:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
I cannot figure out why mine fails and wife's works as intended.. all configs seem identical.. permissions identical. running as sudo in ubuntu server where casaOS is installed
20 Replies
Do the container logs have any errors?
ive been rerunning the import and looking for errors across all containers... i dont see anything related to this.
Can you post the logs?
any specific container you want to see?
Server would be the most likely culprit
theres a job running thumbnails in the bg so its a lot
ok let me show server
i have attempted to run import several times within the last 30 min as you can see no log at all related
reposting longer log
What about the proxy container? And are you using your own reverse proxy as well?
I am not using a reverse proxy - heres that
2023/09/17 17:01:53 [error] 43#43: *16042 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.21.0.1, server: , request: "POST /api/asset/import HTTP/1.1", upstream: "http://172.21.0.8:3001/asset/import", host: "casa.lan:2283"
Hmmm
It's timing out the request
@jrasm91 thoughts?Import generates a hash server-side. For bigger files (videos) it sometimes takes longer than the default Nginx timeout.
You can hit the immich-server container directly to avoid the issue or update the proxy container to use a custom config with longer timeout.
ok - this is promising since I do have longer videos, and it seems like its timing out at the default 60s.. although, I am not getting this error as I try to run the import currently
im trying to locate the nginx.conf in relation to this container, which was installed using portainer
Where are you running the import command from?
from the ubuntu server where casaos / portainer is installed
theres no actual nginx on the server itself just through your autoconfig via immich proxy
But is it easy to connect to the immich-server container from where you are running the command?
Instead of using immich-proxy:2283/api, use immich-server:3001/
kk
Somebody should make a PR to extend the timeout on this specific endpoint 😁
running import directly from immich_server container... "Its Working, Its working!" -anakin skywalker 32 BBY
thank you both for helping me
Let's go!