500connect ECONNREFUSED 172.22.0.2:3001
Hi, just updated to today's release and after trying to connect I get the attached screenshot message. Running on unraid latest version through docker-compose. Will post env and compose below. I added quite a few files through cli today but it was working until restart.
58 Replies
Google Docs
Compose
Compose version: "3.8" services:  immich-server:    container_name: immich_server    image: ghcr.io/immich-app/immich-server:release    command: ["start-server.sh"]    volumes:      - ${UPLOAD_LOCATION}:/usr/src/app/upload    env_file:      - .env    depends_on:      - redis      - d...
Did you check whether the containers are all running and what their logs are?
Google Docs
Env
Env ################################################################################### # Database ################################################################################### # NOTE: The following four database variables support Docker secrets by adding a *_FILE suffix to the variable n...
All containers are currently running, should I send all of their logs?
Check the logs for errors and send them here if that doesn't get you further, yes
Is your host ip 172.22.0.2? Sounds like it is a docker ip and not host ip. Just my 2c.
the typesense log is the file in the immich appdata and the others are from docker logs as the typesense log window kept closing immediately
The logs from the server are incomplete so it's hard to tell for sure, but I think it's failing to start because it can't connect to typesense
If you remove the
part from the typesense section in the compose file, you should be able to see the typesense logs via docker as well
is this correct?
Can you try shutting down the whole stack, deleting the tsdata volume, and then starting it back up?
is that the one with these in it?
Based on your docker-compose.yml, it's the
tsdata docker volumeoh ok
that worked thanks!
I have another question
is this normal
I made the size smaller to show the whole gap
Does it still happen if you refresh the page?
If so, check the server logs to see what the error is
yep, which containers logs should i check
server
That is... strange
Do you have any assets which might have an exif date absurdly far into the future somehow?
cc @Alex @jrasm91 this is an interesting one lol
Uhhh what
:BO_Nani:
my time-issues counter just resetted again damnit
I haven't changed any but have run exiftool on these as they are exported from google photos via takeout
Is the datetime wrong and it's making a bad request because of it?
I have a feeling that process might have gone wrong and register incorrect date info to the assets
In the dev tools network request list can you see a count by time bucket request? Can you copy the response here?
Is it the bit in console?
Can you put
time-bucket to the filter box and refresh the pageThen capture this
and this
Should i do this for all of them?
Can you navigate to
http://ip:2283/api/asset and take a screenshot of the pagethere is quite a lot should i send a txt
You can see the
fileCreatedAt date is incorrectah thats weird
They're all instagram boomerangs made in the seperate app
count-by-time-bucket is what we wanted fyi
That gets a list of dates + counts. Should show a few invalid dates.
There are a few groups at the top that are probably wrong
And there is one group at the bottom that looks wrong as well (1970).
Would probably good to delete those assets, fix the dates in them and reupload them.
ok will do that
thanks so much everyone!!
Those almost look like phone numbers lol
just wondering how I should remove them as i moved them out of the library folder but they still show up in the web and cause the the econnrefused again
Changing files on disk won't have any effect
You need to delete them from the UI
Which is a bit tricky here, hmmmm
Is there a way you can do it through cli or is that only for importing
It is in the backlog to add, but not yet.
What can I do about the photos then or should I just wait for a patch for this sort of thing?
Can you delete them through the UI or what do you mean?
Yeah how do you delete them as they don't show up
Oh, right they don't show up because of the timeline bucket issue... hmm
Is there a way to reindex the library?
Depends on what exactly you need
Just found out for anyone else with this issue they actually show up on mobile but not for web
So you can delete them from the app easily
How does the mobile app look like?
Just like normal but with the crazy high dates, so can interact and delete fine from there
I'm not sure if I am right but submitted a bug that the images do not show on web with very high creation year on github
I saw that, thank you
It is invalid data, yes. But also we should handle it better and not just blow up 😛