rclone: failed to open source object: open file failed: cannotDownloadAbusiveFile

What is the problem you are having with rclone?

When trying to download some APK or EXE files that I have on GDrive, I receive this error message:

file: Failed to copy: failed to open source object: open file failed: googleapi: Error 403: This file has been identified as malware or spam and cannot be downloaded., cannotDownloadAbusiveFile

What is your rclone version (eg output from `rclone -V`)

rclone v1.41

os/arch: darwin/amd64
go version: go1.10

Which OS you are using and how many bits (eg Windows 7, 64 bit)

macOS High Sierra 10.13.4

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

Google Drive

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

rclone sync remote:folder local/Folder

Possible solution

If we add the flag acknowledgeAbuse=true we can bypass this error: https://github.com/prasmussen/gdrive/issues/182

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 24 (14 by maintainers)

Commits related to this issue

drive: Add --drive-acknowledge-abuse to download flagged files - fixes #2317 Also if rclone gets the cannotDownloadAbusiveFile suggest using the --drive-acknowledge-abuse flag. — committed to rclone/rclone by ncw 6 years ago
drive: Add --drive-acknowledge-abuse to download flagged files - fixes #2317 Also if rclone gets the cannotDownloadAbusiveFile suggest using the --drive-acknowledge-abuse flag. — committed to rclone/rclone by ncw 6 years ago

Most upvoted comments

@Fabian42 thanks for testing. You can set it as an environment variable for now - you’ll be able to set it in the config file in about a week after v1.41 is released (I’ll merge my config unification changes once v1.41 is released).

ncw on Jun 14, 2018

By having it be a command line argument, scripting programs like RCloneSync still don’t work. It would be better as an option in rclone config or something else that’s permanent. Should this be reopened or should I make a new report?

On 20:48, Wed, 13 Jun 2018 Jacob Hands, notifications@github.com wrote:

Can you run it again with -vv and post the output here?

On Wed, Jun 13, 2018, 1:34 PM Fabian Röling notifications@github.com wrote:

I just tried it and it did not synchronise the file. It didn’t give out an error message (it had absolutely no output) and it synchronised everything else, but it didn’t synchronise the two blocked files.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ncw/rclone/issues/2317#issuecomment-397041086, or mute the thread < https://github.com/notifications/unsubscribe-auth/AKOQXUdmaIglL88F9o0NP_hZVqithlKdks5t8VsugaJpZM4UL_IB

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ncw/rclone/issues/2317#issuecomment-397045580, or mute the thread https://github.com/notifications/unsubscribe-auth/AJ_vYmY2SHyaQgtQgqpr32vSi7d0zMRDks5t8V5ygaJpZM4UL_IB .

Fabian42 on Jun 14, 2018

I would very much appreciate this. I have a ton of legitimate files getting flagged as abusive.

jahands on Jun 7, 2018