This article explains how to handle a specific error from the Dropbox API that occurs when a file is blocked from being migrated due to content restrictions.
1. Symptom
During a migration from Dropbox, one or more files fail to transfer. When you review the CloudM Migrate logs for the failed items, you see an error message similar to this:
{"error_summary":"path/restricted_content/","error":{".tag":"path","no_account":null,"path":{".tag":"restricted_content"}}}
2. Cause
This error is not generated by CloudM Migrate. It is an error sent directly from the Dropbox API, which CloudM Migrate then reports in its logs.
The path/restricted_content message means that Dropbox is actively blocking access to the file because its system has flagged the content as restricted. This can happen for several reasons, including:
-
Copyright Claims: The file matches a known copyrighted file (e.g., a movie, song, or software installer).
-
Malware or Security Risk: The file has been identified as potential malware or a security threat.
-
Policy Violation: The content violates Dropbox's Acceptable Use Policy.
Because Dropbox is refusing to allow access, CloudM Migrate cannot read or transfer the file.
3. Resolution
CloudM Migrate cannot bypass this restriction. The resolution must be handled between you and Dropbox directly.
Step 1: Identify the Restricted Files
Review the migration logs in CloudM Migrate. For each file that fails with this error, note down the File ID and Filename, as you may need this information for a support request.
-
Example from logs:
File Id: id:xxxxxxxxxxxxxxxxxFilename: example.jar
Step 2: Review the Content or Contact Dropbox Support
You have two options:
-
Option A: Acknowledge and Skip If the file is non-essential or you believe it genuinely violates policy, the only course of action is to acknowledge that this specific file cannot be migrated.
-
Option B: Report the Issue to Dropbox If you believe a file has been flagged incorrectly and does not violate any policies, you must report it to Dropbox Support for a review.
-
Go to the Dropbox support page: https://www.dropbox.com/support
-
Create a support ticket explaining the situation.
-
Provide them with the File ID and Filename of the incorrectly flagged file from your migration logs.
-
Dropbox should then be able to review the file and, if appropriate, remove the restriction, which would allow the file to be migrated on a subsequent pass.