When uploading files using the crypt layer I get an error "Failed to copy: file_id is required. (Error 400)". It seems to be with some specific files but I don't understand the reason for this failure.
Run the command 'rclone version' and share the full output of the command.
rclone v1.64.0
os/version: Microsoft Windows 11 Pro 22H2 (64 bit)
os/kernel: 10.0.22621.2283 (x86_64)
os/type: windows
os/arch: amd64
go/version: go1.21.1
go/linking: static
go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
OpenDrive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
Thank you very much for helping me, I have tried this solution by putting the 'm' but I still get the same error. --contimeout 10m --timeout 15m error: 2023/09/27 22:54:35 ERROR : video: Failed to copy: file_id is required. (Error 400)
I have noticed in my vps that the 'file_id' error only occurs in the new version, since I installed rclone rclone v1.50.2 from the default linux repositories and I did not get the error, but I updated rclone to rclone v1.64.0 and I do get the error.
At the moment I am using version 1.5 of rclone which does not give the error. But I have the problem that some files are not completely uploaded to opendrive and remain infinitely uploaded. As far as I understand it doesn't seem to be a problem with the encryption level.
I'm starting to suspect it's just opendrive being garbage and not processing the upload in a timely fashion. Sometimes this causes rclone to try to upload the files again from scratch even though they will suddenly appear in opendrive
The truth is that I have noticed something strange, although I use 1.5 I see that it stays in loop and at the end there are files that are not uploaded, but then appear in the cloud.
Followup/Update - was talking with opendrive support, sharing some logs and they said they were talking with their developers about it - I just got the following message back from them:
Admin Today at 18:49
We have identified the cause of this but it will take several days to roll the fix out to all servers. We will update you once this has completed.