Cannot decrypt any files

Suspected Bug
1

Everything works great. I can upload to remotes and crypt remots without issue.

I cannot download (decrypt), i don’t know why.

Password and password2 are ok. It works in CLI.

log :

Message: Corrupted on transfer: sizes differ src(Encrypted drive ‘crypt2:’) 2301003 vs dst(Filen xxxxx@gmail.com at /) 131072
Details: Transfer failed due to errors.
File: xxxx

Using Filen custom Rclone which is not official yet. It works perfectly, except for that one point.

2

I think i’ve isolated it, it seems to work with a webdav remote and not the filen rclone one, not sure why since this version was supposed to be pushed to main

3

I take that back, it does not work anymore either, just loads indefinitely.

I don’t understand really, everything else is so smooth; I can’t upload or download with webdav, but files are read just fine. it loads in the void without errors

With filen, i can upload, but can’t download or drag anywhere elese

4

Have you seen anything like it @rcloneview ? :slight_smile:

5

Thanks for the detailed updates and for isolating the behavior.

To address your main concern: We have just performed fresh tests using crypt on top of a webdav remote, and it is working without issues on our end. We are able to upload, download, and decrypt files normally.

Since you mentioned that this works perfectly in the CLI but fails in the GUI (or specific integration), and given the error log you provided (Corrupted on transfer: sizes differ... dst... 131072), here are a few insights:

  1. The 128KB Cutoff: The destination size showing as 131072 (exactly 128KB) suggests the download stream is being terminated immediately after the first chunk. This often happens if the specific Rclone binary being used clashes with the mount/VFS settings, or if the GUI is timing out waiting for a specific output format.
  2. Custom Binary: You mentioned using the “Filen custom Rclone.” Since this is a non-official fork, it may handle standard output or streams differently than the official binary, which can cause the GUI to interpret the transfer as “stalled” and kill it.

Suggestions:

  • Test with Official Rclone: Please try pointing the application to the standard, official Rclone binary (latest version) using the WebDAV protocol. This will confirm if the issue is the custom Filen binary.
  • Debug Log: If possible, please run the transfer with -vv (debug) enabled in the extra flags and post the full output here so we can see exactly where the pipe is breaking.

Let us know if the official binary resolves the issue.

6

@rcloneview

Thank you very much for the quick and detailed answer.

Webdav : I’ve tried with the latest official release this morning. It works for 0b or very small files, otherwise it just says “waiting for available workers” and just loads forever. There is no log since it does not fail, so I don’t know how to send you that…

For a 10mb file for example, it gets stuck at 5%, 508kb everytime

Actually I’ve tried again with small files now and it does not work anymore, just loads indefinitely.

I’ve tried mounting with your GUI, then uploading/downloading , and it works fine. But I would like to avoid that, as mounting is slow, clunky and I dislike cache settings with a passion

Filen : can’t test with the officiel rclone yet

S3 : Never managed to set it up with Filen

7

@rcloneview Do you have any other idea on what I could try ? I don’t understand why uploading works flawlessly for the filen client (crypt or not), downloading for classic filen works well too, but only downloading the filen crypt bugs ?

Why would it only work in one direction ?

8

I’ve tried creating the crypt from rclone view, but same issue. Tried without a salt, same issue.

I don’t know how to have detailed logs when copying directly from your GUI, could you tell how to do that ?

9

Hello, so it seems I had leftovers from a previous installation that were interfering with the config file, I’m not entirely sure what happened to be honest.

I deleted all Rclone versions and GUI, used BCuninstaller to get rid of whatever traces were staying in registry or elsewhere, reinstalled everything, and now it works. Not Filen’s or Rcloneview’s fault. Thanks for the help !

1 Like