Question
Problem with rclone spaces. Failed to copy.
- Posted on December 15, 2020
- DigitalOcean Spaces
Asked by Adriano Romagnoli
As the tutorial said, I configured the Rclone to copy files from sfo2 to nyc3. Here is the problem: (i used rclone -vv copy spaces-sfo2:source spaces-nyc3:target)
2020/12/14 22:43:02 DEBUG : rclone: Version “v1.53.3” starting with parameters [“rclone” “-vv” “copy” “spaces-sfo2:source” “spaces-nyc3:target”] 2020/12/14 22:43:02 DEBUG : Using config file from “/root/.config/rclone/rclone.conf” 2020/12/14 22:43:02 DEBUG : Creating backend with remote “spaces-sfo2:source” 2020/12/14 22:43:02 DEBUG : Creating backend with remote “spaces-nyc3:target” 2020/12/14 22:43:10 ERROR : prontuarios/1000.pdf: Failed to copy: s3 upload: 400 Bad Request: <?xml version=“1.0” encoding=“UTF-8”?><Error><Code>InvalidArgument</Code><BucketName>target</BucketName><RequestId>tx000000000000000eef8ff-005fd814ae-2a11968-nyc3c</RequestId><HostId>2a11968-nyc3c-nyc3-zg03</HostId></Error> 2020/12/14 22:43:11 ERROR : prontuarios/100.pdf: Failed to copy: s3 upload: 400 Bad Request: <?xml version=“1.0” encoding=“UTF-8”?><Error><Code>InvalidArgument</Code><BucketName>target</BucketName><RequestId>tx000000000000000eef94b-005fd814ae-2a11968-nyc3c</RequestId><HostId>2a11968-nyc3c-nyc3-zg03</HostId></Error>
What is wrong here?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello, @AdrianoRomagnoli
Is there any additional messages that are generated with the error? Usually there will be once more field after the InvalidArgument which is a message that usually indicates the exact error, e.g Unsupported Authorization Type and so on.
Also would you mind to double check your rclone.conf file and make sure that the details for the space are correct?
Hope that this helps! Regards, Alex
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
I found the problem! the configuration for target section must be “acl = private”. And its worked!
[spaces-target] type = s3 env_auth = false access_key_id = xxxxxx secret_access_key = yyyyy endpoint = nyc3.digitaloceanspaces.com acl = private