Rclone shows a directory which isn't there

Help and Support
1

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

Hello
I'm running rclone crypted and chunked for media stuff - this is the first time I'm running into this problem. I'm having a folder which is there for rclone, but not for Box - that's how it feels at least. I can't delete the folder because it isn't really there lol. And every script throws an error because of that Schrödingers Cat folder :slight_smile:

Run the command 'rclone version' and share the full output of the command.

rclone v1.66.0

  • os/version: debian 12.5 (64 bit)
  • os/kernel: 6.1.0-17-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

BOX

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone lsd -vvv "MyBOXChunker:/Filme/Scoop –– Ein royales Interview (2024) [tmdbid=1083658]"

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[MyBOX]
type = box
token = XXX
root_folder_id = XXX

[MyBOXBackup]
type = box
token = XXX

[MyBOXChunker]
type = chunker
remote = MyBOXcrypt:
chunk_size = 4G
hash_type = none

[MyBOXcrypt]
type = crypt
remote = MyBOX:
filename_encryption = obfuscate
password = XXX
password2 = XXX

A log from the command that you were trying to run with the -vv flag

rclone lsd -vv "MyBOXChunker:/Filme/Scoop – Ein royales Interview (2024) [tmdbid=1083658]"
2024/04/21 17:27:35 DEBUG : rclone: Version "v1.66.0" starting with parameters ["rclone" "lsd" "-vv" "MyBOXChunker:/Filme/Scoop – Ein royales Interview (2024) [tmdbid=1083658]"]
2024/04/21 17:27:35 DEBUG : Creating backend with remote "MyBOXChunker:/Filme/Scoop – Ein royales Interview (2024) [tmdbid=1083658]"
2024/04/21 17:27:35 DEBUG : Using config file from "/home/wlfx/.config/rclone/rclone.conf"
2024/04/21 17:27:35 DEBUG : Creating backend with remote "MyBOXcrypt:/Filme/Scoop – Ein royales Interview (2024) [tmdbid=1083658]"
2024/04/21 17:27:35 DEBUG : Creating backend with remote "MyBOX:/237.Knqrj/160.Vfrrs ‛ Hlq urBdohv Lqwhuylhz (9791) [wpgelg=8750325]"
2024/04/21 17:27:39 DEBUG : Creating backend with remote "MyBOX:/237.Knqrj/160.Vfrrs ‛ Hlq urBdohv Lqwhuylhz (9791) [wpgelg=8750325]"
2024/04/21 17:27:42 Failed to create file system for "MyBOXChunker:/Filme/Scoop – Ein royales Interview (2024) [tmdbid=1083658]": failed to make remote "MyBOXcrypt:/Filme/Scoop – Ein royales Interview (2024) [tmdbid=1083658]" to wrap: failed to make remote "MyBOX:" to wrap: is a directory not a file

The folder shows up in that directory listing:

rclone lsd MyBOXChunker:/Filme/

          -1 2024-04-20 22:16:59        -1 Scoop –– Ein royales Interview (2024) [tmdbid=1083658]

and also when I mount that folder.

But the encrypted folder

/237.Knqrj/179.oyKKL

is not there in Box WebUI.

Maybe something is wrong about the "--" in the title? The title should be
" Scoop - Ein royales Interview"
but it shows up as
"Scoop –– Ein royales Interview (2024) [tmdbid=1083658]" in rclone lsd.

I'm having around 16tb there without any issues - that's the first time this comes up.

I'd be happy about any idea,
thanks!

2

Looking at themoviedb, it is a
"–"
not a
"-"
in the title.
Are there any known issues about that symbol?

3

okay, got it.
On console the name of the folder was:

Scoop –– Ein royales Interview (2024) [tmdbid=1083658]

But in fact it is

Scoop – Ein royales Interview

It is NOT

Scoop - Ein royales Interview

So I got the encrypted folder name by the second name and removed it. All good now.
Looks like there seems to be some bug about that symbol.

4

I would recommend to use proper encryption instead.

"obfuscate" is home brewed method which even assuming that algorithm does not have bugs relies on remote perfect Unicode support. And this can be always problematic especially that Unicode is evolving standard with new characters added in every version.

Your supported remote unicode character can be "obfuscated" into something not supported for example.

Box supports base32768 encoding which allows to store filenames even longer than supported by remote itself so there is no single reason to use obfuscate here.

5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.