Ole could it be the range header not working as expect resulting in the start of the file always been returned? For an un-encrypted file it likely would not error the download but the file would be junk if using multi threads or multi requests and ok if single thread / single download request. For an encrypted file it would instead break the encrypted data because you are going back to the start of the stream.
Not sure if someone has an easy way to test it to see but could be worth it to see if a say a file directly downloaded from Dropbox webui vs the same file downloaded but not decrypted by reclone was binary same or if the binary where it differs matches the start of the file.
The file would need to be big enough to trigger multi download threads to be a valid test
All the symptoms above seem to point to a problem with Range requests. In particular rclone copy not working unless --multithread-streams is 0. The mount not working for large files agrees with this also.
Are you able to do this request without the decryption amd compare it to the original file to see if the data in the response is correctly offset and the issue is just a difference in the header as some claim or if the data is actually not offset and the issue is the data not the content type inthe header.
honestly i would not think the content type should really effect rclone unless it is using some sort of manual parsing of the http response instead of a standard lib for making http calls and getting response streams
I actually noticed this starting maybe a day ago? I figured I had some odd bad files mingled in, but when I woke up this morning, I had about ~1000 emails about files reporting this message as I was rescanning a library so something is definitely afoot as I can't imagine I suddenly have that much bad media.
It looks like Dropbox have failed to unwrap the GRPC used internally. The data is OK just that the HTTP response is corrupted. We'll have to wait for dropbox to fix it.
Note that this bug appeared in the integration tests I run daily at 06:00 UTC today 2023-04-25 so it hasn't been around long, and hopefully they will fix it soon.
I was monitoring dropbox mount 24/7 and this problem started exactly yesterday at 22:00 UTC+2 (there was just few corrupted responses, and few correct responses) But after 30 minutes - all files started showing wrong response.
I know this is basically the wrong Forum for this specific question, but the current issue above leads me to this question.
I'm currently migrating from Google to DB this is why TV and Movies still work, but Anime and Pron is broken. I just tried to MergerFS DB:Google but since the files are still present in DB it still tries to load them and therefor it doesn't work. Any ideas for this usecase without the need to interfere manually in the future?
That's what I'm asking for, automatically. I can't just manually switch around. Or at least, don't want to.
I just somehow need MergerFS to understand that there is an issue so it uses the second mount automatically on the fly.