S3Drive - Last error: multi-thread copy: failed to open source: not an encrypted file

Hi, I'm using Sync (Copy mode) from a remote S3 (rclone encrypted) to local. The majority of the files have been copied, but I get this error in the end, and I don't know if this interrupts the process immediately or not (i.e. are there files that haven't been copied aside from the problematic one?). Any hints on how to figure out the problematic file? (edited)

Hi Paper, are you using latest S3Drive version? Is it V1 or V2 cipher?

Tom

Hi Paper, are you using latest S3Drive version? Is it V1 or V2 cipher?

Hi, I'm using the latest S3Drive, V1 cipher

Paper

Hi, I'm using the latest S3Drive, V1 cipher

What's your underlying S3 provider? What's your OS? This error would usually indicate that there maybe some issues with RANGE request handling.

Any hints on how to figure out the problematic file?

At the moment that would likely mean running Rclone CLI and when its not showing the affected file then adding -vvv. Rclone logging in S3Drive isn't fully finished, we may release experimental version though.

Tom

What's your underlying S3 provider? What's your OS? This error would usually indicate that there maybe some issues with RANGE request handling.

Any hints on how to figure out the problematic file?

At the moment that would likely mean running Rclone CLI and when its not showing the affected file then adding -vvv. Rclone logging in S3Drive isn't fully finished, we may release experimental version though.

Backblaze B2 Windows, but files were uploaded through Linux rclone long time ago

Hi @Paper, After reviewing some Rclone code we've came up with two possible situations where this could happen. a) Filename encryption disabled and remote contains unencrypted file. b) Filename encryption enabled and your remote contains file with unencrypted contents, yet its name is properly decryptable according to your encryption password. E.g. file lT5Oi8fqL0nn-ycHlP2ylA translates to test for a password: potato I am not sure if you use filename encryption and I am not entirely sure how it could happen on your end, but I've just wanted to share two possible cases where this error gets generated. It also seems that rclone flag: --ignore-errors doesn't necessarily ignores these errors and -vvv doesn't show much more details... so either request logging needs to be enabled or perhaps there is some alternative way to enable more details. Please let me know if this helps a little. In next turn we could work together to find out why it happend and how to find out which file is at fault.