Connect to Linode Object Storage

istori · August 26, 2022, 10:43am

Some bugs where found, that interfere with configuring the connection and vault with Linode Object Storage. These have been fixed and they should be available in a future release.

With the current version (1.7.5) today, only configure one bucket as multiple buckets will fail and have a least one random file on the bucket before attempting to create the Cryptomator vault.

Thank you Julian!

Links to issues:

github.com/cryptomator/android

A folder can not be created thus also no vault if a S3 bucket is completely empty

opened 07:50AM - 24 Aug 22 UTC

closed 03:27PM - 24 Aug 22 UTC

SailReal

type:bug storage:s3

### Please agree to the following - [X] I have searched [existing issues](https…://github.com/cryptomator/android/issues?q=) for duplicates - [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/android/blob/develop/.github/CODE_OF_CONDUCT.md) ### Summary A folder can not be created thus also no vault if a S3 bucket is completely empty ### System Setup ```markdown - Android: X - Cryptomator: 1.8.0 ``` ### Cloud Type _No response_ ### Steps to Reproduce 1. Create empty S3 Bucket 2. Create a vault or folder ### Expected Behavior Vault or folder is created ### Actual Behavior An error has occurred is displayed ### Reproducibility Always ### Relevant Log Output _No response_ ### Anything else? _No response_

github.com/cryptomator/android

Using multiple cloud connections of the same type causes the second connection to use the connection parameters of the first one

opened 07:46AM - 24 Aug 22 UTC

closed 10:24AM - 24 Aug 22 UTC

SailReal

type:bug storage:pcloud storage:s3

### Please agree to the following - [X] I have searched [existing issues](https…://github.com/cryptomator/android/issues?q=) for duplicates - [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/android/blob/develop/.github/CODE_OF_CONDUCT.md) ### Summary Using multiple cloud connections of the same type causes the second connection to use the connection parameters of the first one. This continues, if there are more than two connections of one type, the first one is always taken as well. ### System Setup ```markdown - Android: X - Cryptomator: 1.8.0 ``` ### Cloud Type _No response_ ### Steps to Reproduce 1. Create a cloud connection of type a, a1 2. Create a cloud connection of type a, a2 ### Expected Behavior Cloud connection a2 uses cloud connection parameters of a2 ### Actual Behavior Cloud connection a2 uses cloud connection parameters of a1 ### Reproducibility Always ### Relevant Log Output _No response_ ### Anything else? All multiclouds are affected except WebDAV. It is not enough to create the connection (e.g. when the app is killed and freshly starts) but the first connection that was established is always reused per cloud type for these affected clouds.