Skip to content

rclone

rclone is a popular tool for copying, synchronizing, and managing data in Object Storage services compatible with the Amazon S3 API.

You can use it with Cloud4You Object Storage S3 to:

  • list buckets,
  • upload files,
  • download files,
  • copy directories,
  • synchronize data,
  • automate tasks,
  • mount a bucket as a directory using FUSE.

Cloud4You Object Storage S3 parameters

Use the following values when configuring rclone:

Endpoint:
https://s3.cloud4you.pl

Region:
eu-pl-1

Provider:
Ceph or Other

You also need:

Access Key
Secret Key

Installation

Windows

After installation, check:

rclone version

macOS

If you use Homebrew:

brew install rclone

Check:

rclone version

Linux

After installation, check:

rclone version

Configuration

Run:

rclone config

Select the option to create a new configuration:

n) New remote

Enter a name, for example:

cloud4you

For the storage type, select:

s3

Then configure the connection.

Provider

If rclone displays a list of S3 providers, select:

Ceph

If your version does not contain an appropriate entry or the configuration requires a generic provider, you can use:

Other

Access Key and Secret Key

Enter the credentials received from Cloud4You.

Example:

access_key_id:
<Access Key>

secret_access_key:
<Secret Key>

Do not share the Secret Key

Treat the Secret Key like a password.

Do not publish the rclone configuration file or fragments of it that contain access credentials.

Region

Enter:

eu-pl-1

Endpoint

Enter:

https://s3.cloud4you.pl

ACL

If rclone asks about ACL and you do not have special requirements, leave the default setting.

Do not enable public access to data unless there is a deliberate need for it.

Example configuration

A configuration fragment may look like this:

[cloud4you]
type = s3
provider = Ceph
access_key_id = <Access Key>
secret_access_key = <Secret Key>
endpoint = https://s3.cloud4you.pl
region = eu-pl-1

Do not publish the real rclone.conf file

The configuration file may contain the Secret Key.

Configuration file location

To check where the configuration file is stored:

rclone config file

rclone will display the path to the currently used rclone.conf file.

Testing the connection

After saving the configuration, list the available buckets:

rclone lsd cloud4you:

Example output:

          -1 2026-08-27 12:00:00        -1 firma-backup
          -1 2026-08-27 12:00:00        -1 firma-archiwum

If the list is displayed without an error, the configuration works correctly.

Listing bucket contents

rclone ls cloud4you:firma-backup

For a more readable view of directories and objects:

rclone lsf cloud4you:firma-backup

Uploading a single file

rclone copyto \
  ./plik.zip \
  cloud4you:firma-backup/plik.zip

Downloading a single file

rclone copyto \
  cloud4you:firma-backup/plik.zip \
  ./plik.zip

Copying a directory to S3

Example:

rclone copy \
  ./dane \
  cloud4you:firma-backup/dane

The copy command copies missing and changed data but does not delete files that exist only at the destination.

Downloading a directory from S3

rclone copy \
  cloud4you:firma-backup/dane \
  ./dane

Synchronizing a directory to S3

rclone sync \
  ./dane \
  cloud4you:firma-backup/dane

sync can delete data

rclone sync makes the destination match the source.

Objects that exist at the destination but not at the source may be deleted.

If you only want to copy new or changed files without deleting data, use rclone copy.

Testing synchronization

Before running sync for the first time, we recommend using:

rclone sync \
  ./dane \
  cloud4you:firma-backup/dane \
  --dry-run

--dry-run shows planned operations without executing them.

Use --dry-run first

This is particularly important for large datasets and automated jobs.

Synchronizing from S3 to a computer

rclone sync \
  cloud4you:firma-backup/dane \
  ./dane

Remember that sync can also delete data at the destination in this direction.

Creating a bucket

rclone can create a bucket:

rclone mkdir cloud4you:firma-backup

Afterwards, check:

rclone lsd cloud4you:

Deleting an empty bucket

rclone rmdir cloud4you:firma-backup

The bucket must be empty.

Deleting a single object

rclone deletefile cloud4you:firma-backup/plik.zip

Destructive operation

Before deleting anything, carefully check the bucket and object name.

Deleting multiple objects

Example:

rclone delete cloud4you:firma-backup/test

This command may delete many objects.

Before running it, you can use:

rclone delete \
  cloud4you:firma-backup/test \
  --dry-run

Checking storage usage

You can calculate the number of objects and their total size:

rclone size cloud4you:firma-backup

Example output:

Total objects: 1250
Total size: 85.123 GiB

The value may differ from the data reported by the billing system or quota due to factors such as versioning and the way storage usage is calculated.

Checking differences

rclone can compare the source and destination:

rclone check \
  ./dane \
  cloud4you:firma-backup/dane

This is useful after larger migrations or copy operations.

More information during transfers

To display progress:

rclone copy \
  ./dane \
  cloud4you:firma-backup/dane \
  --progress

You can also use the shorter form:

rclone copy \
  ./dane \
  cloud4you:firma-backup/dane \
  -P

Logging

Example of writing a log file:

rclone copy \
  ./dane \
  cloud4you:firma-backup/dane \
  --log-file /var/log/rclone-cloud4you.log \
  --log-level INFO

Check the log before sharing it

Logs may contain bucket names, object names, and other technical information.

Before sending a log to a third party, review its contents.

Mounting a bucket as a directory

On systems that support FUSE, you can use rclone mount.

Example:

mkdir -p ~/Cloud4You-S3

rclone mount \
  cloud4you:firma-backup \
  ~/Cloud4You-S3 \
  --vfs-cache-mode full

After running the command, the bucket contents will be visible under:

~/Cloud4You-S3

S3 is not a POSIX filesystem

rclone mount creates a layer that emulates a traditional filesystem.

The behavior of such a mount differs from a local disk, NFS, or SMB.

We do not recommend using rclone mount as direct storage for:

  • active databases,
  • virtual machine disks,
  • applications that require file locking,
  • workloads that require full POSIX semantics.

Automation

rclone can easily be used in scripts and scheduled tasks.

Example:

#!/bin/bash

rclone copy \
  /srv/archive \
  cloud4you:firma-backup/archive \
  --log-file /var/log/rclone-cloud4you.log \
  --log-level INFO

When automating rclone, it is especially important to:

  • protect rclone.conf,
  • monitor exit codes,
  • monitor logs,
  • test commands with --dry-run,
  • use sync carefully.

Permissions for rclone.conf

On Linux systems, it is worth restricting access to the configuration file.

First check its location:

rclone config file

Then set appropriate permissions, for example:

chmod 600 ~/.config/rclone/rclone.conf

Adjust the path to the location shown by rclone config file.

Most common problems

AccessDenied

Check:

  • Access Key,
  • Secret Key,
  • bucket name,
  • user permissions.

SignatureDoesNotMatch

Check:

Region:
eu-pl-1

and:

Endpoint:
https://s3.cloud4you.pl

Also verify the Secret Key and system time.

The bucket is not visible

First run:

rclone lsd cloud4you:

If the bucket does not appear in the list, check the credentials and permissions.

Connection problem

Run the command with more detailed output:

rclone lsd cloud4you: -vv

-vv produces detailed logs

Before publishing or sending the log, check that it does not contain information you do not want to share.

Most commonly used commands

List buckets:

rclone lsd cloud4you:

List objects:

rclone lsf cloud4you:firma-backup

Upload:

rclone copyto \
  ./plik.zip \
  cloud4you:firma-backup/plik.zip

Download:

rclone copyto \
  cloud4you:firma-backup/plik.zip \
  ./plik.zip

Copy a directory:

rclone copy \
  ./dane \
  cloud4you:firma-backup/dane

Synchronization:

rclone sync \
  ./dane \
  cloud4you:firma-backup/dane \
  --dry-run

Check size:

rclone size cloud4you:firma-backup