iturnedintoanewt

Pixels with grapheneos can reboot automatically after a number of hours with the screen off (unattended because you are sleeping). But this would also interfere with Whatsapp backup, which happens overnight.

I...Think I found the issue. A classic case of "increase max upload size on your reverse proxy". Which I thought I did... https://lemm.ee/comment/12234368

Thanks for all the help through the process!

O.M.G....so many hours wasted. One of my first searches already returned "you should increase client_max_body_size to something like 50000M", and I was like I aLreAdy iNCreAseD mY client_max_body_size tO zERo sO its uNLimIteD DuH <spongebob.jpg> Well turns out my client_max_body_size 0 parameter was in a section defining parameters for a different container/server. So of course it wasn't applying to Immich. Just added the same line to Immich section too, restarted nginx...and the backed up asset count is already wayy ahead of the ceiling it would always hit at 180ish assets. I think I might have found my issue.

Thanks for all the help and following up!

You mean to docker logs immich_server ? I think this would be about the only error kinda it's outputting once in a bluemoon.

[Nest] 6 - 05/29/2024, 2:40:17 PM WARN [ImmichServer] [ExpressAdapter] Content-Type doesn't match Reply body, you might need a custom ExceptionFilter for non-JSON responses

Everything else is Websocket Connect, Websocket Disconnect.

You mean, without defining additional paths for thumbs, profile etc? Will it work without declaring them?

Thanks!

Thanks for all the help. I changed the paths as I was mentioning a bit on the .env, so they matched the ones on the docker-compose.yml. But no dice. I think it gets stuck at the same picture, although I'm not 100% sure which one. After I rebuilt the container, the number of assets increased by two, but I also realized that I took a couple pics earlier. So it added those two and crashed a while later at the same spot as before...Is a picture/video capable of corrupting the whole backup?? Also, I'm not sure how to properly track which one is messing it, because the backup seems to have skipped a lot of pictures in what it copied.

Yeah, also my thought. Seems it's still not working. I've seen it repeat the uploads multiple times, and still have quite a limited amount of pictures on the server.

I mean, the NAS is already mounted. It's an NFS share, it gets mounted at boot, and it should be just another regular folder, transparent to docker (or anything else).

I mean, my concern is...it would seem in docker-compose.yml that these paths would match:

${THUMB_LOCATION} = ${UPLOAD_LOCATION}/thumbs
${ENCODED_VIDEO_LOCATION} = ${UPLOAD_LOCATION}/encoded-video
${PROFILE_LOCATION} = ${UPLOAD_LOCATION}profile

, which might explain why I'm getting a thumbs folder inside my /media/MyNAS/Immich/immich-files...same with profile and encoded-video. The thumbs clearly is being used (the one inside Immich/immich-files/thumbs), while the root-located one (Immich/thumbs) is not. The root-based folders might be created due to the .env file, but then not used...and maybe it's confusing Immich? Can I remove the entries from the .env, leaving just the UPLOAD_LOCATION one? Or am I making myself a mess this way? Maybe I should make them point equally in the .env to the same sub-paths inside immich-files so they match the structure in the docker-compose.yml? Sorry...kinda new to docker compose.

The docker container where the DB lives has still another 2GB free to go (I'll increase this). The pictures storage goes to a NAS drive with nearly 10TB of storage left. The docker container has 4GB RAM to run, only immich is running on this at this moment...I didn't seen running too high just yet.

Good point about media storing. I seem to have some loop folders issue. My Immich folder has encoded-video (empty), profile (empty), thumbs (with stuff), and immich-files...and immich-files has encoded-video (again, empty), library (with all the stuff), profile (empty), thumbs (empty) and upload (empty). This is my .env:

UPLOAD_LOCATION=/media/MyNAS/Immich/immich_files
THUMB_LOCATION=/media/MyNAS/Immich/thumbs
ENCODED_VIDEO_LOCATION=/media/MyNAS/Immich/encoded-video
PROFILE_LOCATION=/media/NASdata/MyNAS/Immich/profile

And...this is my docker-compose.yml:

    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - ${THUMB_LOCATION}:/usr/src/app/upload/thumbs
      - ${ENCODED_VIDEO_LOCATION}:/usr/src/app/upload/encoded-video
      - ${PROFILE_LOCATION}:/usr/src/app/upload/profile
      - /etc/localtime:/etc/localtime:ro

Is there anything obviously wrong that would make Immich place stuff in weird folders? Should I remove all the additional paths from .env, leaving only UPLOAD_LOCATION?

Thanks! I never walked through that screen yet...I'll try that!

EDIT: Seems...not to have done much. Backup keeps tracking and uploading a ton of files. Many more than what the server actually displays, as in, I've seen the backup go through pictures with dates the server doesn't seem to show. I've seen it slowly go through at least 15-20 videos for example, but the server only acknowledges a grand total of 2 video assets.

EDIT2: Oops, seems the screen eventually turned off and backup stalled...Let's see what it does now... ....aaaand back to May 25th. Yup, still the same problem here :(