...
[caringo]
type=s3
access_key_id=${S3_ACCESS_KEY}
secret_access_key=${S3_SECRET_KEY}
# Must NOT include default port 443 or 80 with rclone >1.47 to avoid signature errors!
endpoint=${S3_PROTOCOL}://${DOMAIN}:${S3_PORT}
location_constraint=
# The --s3-no-check-bucket option is required with rclone > v1.50 and gateway < 7.1 to avoid 409 errors (CLOUD-3213)!
no_check_bucket=true
For example, if your S3 domain / endpoint is "https://mydomain.cloud.caringo.com" you can create a token with:
...
[caringo]
type = s3
# Do NOT use V2 sigs, have seen signature problems.
# region = other-v2-signature
access_key_id = c63d5b1034c6b41b119683a5e264abd0
secret_access_key = secret
endpoint = https://mydomain.cloud.caringo.com
location_constraint=
# The --s3-no-check-bucket option is required with rclone > v1.50 and gateway < 7.1 to avoid 409 errors (CLOUD-3213)!
no_check_bucket=true
If you prefer a GUI client to manage your copy and sync jobs try https://martins.ninja/RcloneBrowser/. Just download the binary from https://github.com/mmozeiko/RcloneBrowser/releases and point it to your rclone.conf. It's very flexible, you can configure any of the below options.
...