Starting with Resilio Connect v2.11 Administrators can check a connection to a configured cloud storage before using it in a job. It helps to avoid some possible errors and misconfiguration before creating jobs.
To start a test click the test button after creating or while editing storage configuration. By default, the Management Console Agent will be used to probe the connection. If a different Agent is preferred, the admin has the option to select another Agent. (The chosen agent must be licensed to access "Cloud Storage".)
If a bucket (container or share) is specified in the configuration, the agent will check the connection to that bucket only.
If bucket (container or share) is not specified, the agent will first try to list all the buckets using the entered keys.
Listing of buckets/containers/shares requires special permissions be granted:
- Amazon S3 credentials must provide full access to all S3 buckets in the account.
- Google Cloud credentials must provide full access to the storage service of the selected project (service account role “Storage Admin”).
Google Cloud requires a Project ID to be able to browse through buckets instead of Project Name. For updates from the older version of Resilio Connect, manually update the configuration and change it to Project ID. Otherwise browsing through buckets and testing connections to the configured Google Cloud storage won't work.
- Azure Blob Storage and Files Storage key authorization should work without any special configuration, however, the SAS token must include the minimum permissions described below.
If the permission to list buckets is not granted, the admin will be prompted to choose an available bucket.
If a connection to the cloud is not possible for any reason, the agent will display the error returned by the cloud storage provider.
The error itself may be ambiguous though. For example, the same error may be returned if the account name is wrong, or the endpoint was mistyped.
Backblaze storage may report "SE_ENC_PEER_VERIFY_ERROR" in Windows when testing connection.
The error is caused by the missing certificate. To resolve the issue run the following two commands in Command Prompt or PowerShell
curl.exe -O https://letsencrypt.org/certs/isrgrootx1.pem certutil -addstore -f "Root" isrgrootx1.pem
And reboot the server.