I
Immich•3y ago
linuxguy

Images not showing up after upload

I've got about 2000 photos selected across various albums and the mobile app has completed a complete upload/backup session. After completion, however, I only see some 200 images in the server status counts. When I start another backup, it tries to upload the same images again. I've checked logs for all the containers and don't see any errors. How can I debug why 9 out of 10 of my images "upload" to /dev/null?
19 Replies
Alex Tran
Alex Tran•3y ago
Do you see those images on your mounted UPLOAD_LOCATION?
linuxguy
linuxguyOP•3y ago
Edit: The ~200 images are on the filesystem, the rest are not
Alex Tran
Alex Tran•3y ago
This is probably related to your setup, why don't you provide those info?
linuxguy
linuxguyOP•3y ago
GitHub
immich/kubernetes at main · gregwalters/immich
Self-hosted photo and video backup solution directly from your mobile phone. - immich/kubernetes at main · gregwalters/immich
Alex Tran
Alex Tran•3y ago
I don't know any thing about k8s, you might have to wait for someone with the expertise to come in
linuxguy
linuxguyOP•3y ago
The fact that some pictures are making it to the filesystem makes it seem like everything is OK but obviously there's an error somewhere 😛 I'm curious how to turn on debug/request logging. Any pointers?
Alex Tran
Alex Tran•3y ago
You can enable nginx logging did you run from local ip or through a reverse proxy?
linuxguy
linuxguyOP•3y ago
reverse proxy
Alex Tran
Alex Tran•3y ago
why don't you try running it from local ip first and see if all the asset get uploaded
linuxguy
linuxguyOP•3y ago
Good call on the nginx logging.
nginx-ingress-controller-h8zr9 controller 192.168.200.7 - - [25/Jan/2023:20:13:50 +0000] "POST /api/asset/upload HTTP/1.1" 413 176 "-" "Dart/2.18 (dart:io)" 500 0.189 [-] [] - - - - 2c5cb8089c676ccb5461a6a1b77d76f8
nginx-ingress-controller-h8zr9 controller 2023/01/25 20:13:50 [error] 21682#21682: *372197608 client intended to send too large body: 2191437 bytes, client: 192.168.200.7, server: <removed>, request: "POST /api/asset/upload HTTP/1.1", host: "<removed>"
nginx-ingress-controller-h8zr9 controller 192.168.200.7 - - [25/Jan/2023:20:13:50 +0000] "POST /api/asset/upload HTTP/1.1" 413 176 "-" "Dart/2.18 (dart:io)" 500 0.189 [-] [] - - - - 2c5cb8089c676ccb5461a6a1b77d76f8
nginx-ingress-controller-h8zr9 controller 2023/01/25 20:13:50 [error] 21682#21682: *372197608 client intended to send too large body: 2191437 bytes, client: 192.168.200.7, server: <removed>, request: "POST /api/asset/upload HTTP/1.1", host: "<removed>"
Alex Tran
Alex Tran•3y ago
probably you need to update your max body size setting
linuxguy
linuxguyOP•3y ago
Already did Funny that 1/10 pictures was below the max limit 😂 Thanks for sounding boarding this with me
Alex Tran
Alex Tran•3y ago
Hye no problem, sorry couldn't be more help, I haven't had a chanced to play with k8s
linuxguy
linuxguyOP•3y ago
My next TODO is a PR to add a link to the helm charts to the immich.app documentation so I wouldn't have wrote my own stuff >.<
Alex Tran
Alex Tran•3y ago
We did that 😛
Alex Tran
Alex Tran•3y ago
Kubernetes | Immich
You can deploy Immich on Kubernetes using the official Helm chart.
linuxguy
linuxguyOP•3y ago
Oh, yes I see that now! Damn, moving fast There's a third (and best, IMO) way to fix that DNS issue called out on the install page:
dnsConfig:
options:
- name: ndots
value: "2"
dnsConfig:
options:
- name: ndots
value: "2"
Kryptonian
Kryptonian•3y ago
Did you deploy the proxy container too?
Kryptonian
Kryptonian•3y ago
GitHub
k8s-cluster/cluster/apps/default/immich/app at main · samip5/k8s-cl...
GitOps/Flux2 managed full-stack Kubernetes cluster. - k8s-cluster/cluster/apps/default/immich/app at main · samip5/k8s-cluster

Did you find this page helpful?