Kevin Cox

I just ran another backup and it failed about about 10min 80% of the way through an almost 500MB file (so about 5.3 Mbps average). There were 0 logs generated.

I tried again and failed again after about 10min with no logs. This time it got to 38% before stopping. So quite possibly a 10min timeout somewhere. IDK if in...

Another attempt uploaded a few images first then failed on the large file after ~10min and 60%. This suggests that the timeout is per-file, but I wasn't paying enough attention...

Interesting idea. I checked the logs and it does look like the request is somewhat closed by nginx ```json { "cache_status": "", "connection_id": 110845, "connection_request_count": 39, "duration_s": 613.521, "protocol": "HTTP/1.1",...

So me and my partner both took loads of pictures and many large videos yesterday but when we went to sleep we started a foreground upload. Both finished without any...

Hi @jrasm91 what issues should I be following to know when this is resolved? Being able to background in the background is pretty important to me even if it takes...

Ah ok. I will try to reproduce and report back if I hit it.

In theory offline mode could be used as a workaround but https://github.com/jarnedemeulemeester/findroid/issues/766 ruins that. Edit: this is actually a viable workaround as the media is deleted despite the exception.

RFCSC: This RFC has not acquired enough shepherds. This typically shows lack of interest from the community. In order to progress [a full shepherd team is required](https://github.com/NixOS/rfcs/#shepherd-team). Consider trying to...

RFCSC: @AndersonTorres if you are able to spare the time it would be much appreciated as that would be enough to complete the shepherd team and move the RFC forward.