For the newly created remotes under Linux, there are errors in any operation related to the remotes, such as the copy command: rclone ls -vv test: ,But it works on windows .
What is your rclone version (output from rclone version)
v1.49.5
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Red Hat 4.8.5-16 x86_64
Which cloud storage system are you using? (eg Google Drive)
Amazon S3
This is the configuration:
[test]
type = s3
provider = Minio
env_auth = false
access_key_id =***
secret_access_key = ***
endpoint = http://cloud-gf.focuxy.com
acl = public-read-write
bucket_acl = public-read
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone ls -vv test:
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
2019/10/23 10:28:00 DEBUG : rclone: Version "v1.49.5" starting with parameters ["rclone" "ls" "-vv" "test:"]
2019/10/23 10:28:00 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2019/10/23 10:28:00 Failed to ls: SerializationError: failed to decode REST XML response
status code: 200, request id:
caused by: XML syntax error on line 17: invalid character entity & (no semicolon)
I used the same Linux kernel to do the same configuration and operation on another machine, but it was successful. It should not be the problem of Minio. It's not good to change the latest rclone beta. Is there any software rclone relies on in Linux environment? What else may be the cause of this problem?
2019/10/24 17:07:54 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2019/10/24 17:07:54 Failed to ls: SerializationError: failed to decode REST XML response
status code: 200, request id:
caused by: XML syntax error on line 17: invalid character entity & (no semicolon)
It looks like it's blocked by the company's firewall. I'll ask the network administrator later to see if it can be solved. Thank you very much!