istori
August 17, 2022, 4:37pm
1
I am trying to connect to S3-compatible Linode Object Storage on the Android app and I get an error. No such bucket.
A globally-available, S3-compatible method for storing & accessing data. Files are stored in flat data structures alongside their own rich metadata.
Est. reading time: 7 minutes
I am using
Endpoint:
https://us-southeast-1.linodeobjects.com
Region:
us-east-1
Hey and welcome to the Cryptomator Community ,
No such bucket.
Did you create the bucket before adding the connection?
istori
August 17, 2022, 5:41pm
3
Yes. I do have one created. I put in the value in the Existing Bucket field. I filled in all the fields with the correct values.
Okay. Then we need log files. Can you please enable debug mode, reproduce the problem and send us the log file? How do I enable debug mode on Android?
istori
August 17, 2022, 6:34pm
5
To what email address I send the log?
Should be prefilled, if for whatever reason not, support@cryptomator.org
Thanks for the log file. It would be really helpful to run test against the s3 implementation of Linode, is it possible for you to provide us test-credentials or is that not an option?
istori
August 18, 2022, 2:07pm
8
Yes, I will create a new bucket and keys for you.
1 Like
istori
August 26, 2022, 10:43am
9
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:
opened 07:50AM - 24 Aug 22 UTC
closed 03:27PM - 24 Aug 22 UTC
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_
opened 07:46AM - 24 Aug 22 UTC
closed 10:24AM - 24 Aug 22 UTC
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.
1 Like
Thanks again for reporting these bugs
1 Like