Hi,
This is a request for practical rclone contingency and migration guidance rather than a rclone malfunction report.
What is the problem you are having with rclone?
I operate public-facing image-hosting services and use IDrive e2 as S3-compatible storage with rclone. IDrive has placed the entire e2 account under an internal review, so I currently cannot list buckets or access the data. The provider has confirmed that the review is ongoing; I have completed its requested actions and am seeking controlled reactivation. I am not asking anyone to bypass provider controls or access restricted material.
While the provider review is pending, I want to prepare a safe recovery and migration plan once legitimate access is restored. I would appreciate advice on preserving rclone configuration, logs, and any locally available inventory; planning an incremental migration or replication; and whether anyone has experience with account-level IDrive e2 restrictions and a legitimate support or escalation route.
rclone version
I cannot obtain a current command output from the affected production environment while this account-level access issue is pending. Once reactivated, I can provide the exact rclone version, a redacted configuration, and -vv logs if they are useful.
Which cloud storage system are you using?
IDrive e2 (S3-compatible).
The command you were trying to run
No single rclone command is currently failing; the blocker is account-level access at the storage provider.
Config and logs
I am deliberately not sharing access keys, bucket names, or sensitive material. I can provide a redacted configuration and -vv output after access is restored if that would help with migration planning.
Thank you.