New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minio doesn't work #19
Comments
Thanks for creating this issue. Can I ask you to have a look in the logs section (please find instructions how to access logs: #16 (comment)) and post the error message? Are you trying to reach your Minio over http or https? Currently only https is supported. We will be looking to support (around ~Jan 2023):
|
I'm using SSL on a subdomain e.g. I see what the issue is. You are adding the bucket name as a subdomain to the s3 URL so it looks like this I feel like this would have been caught if you tested this locally, I find it weird to paywall a broken feature like this, was it ever tested? |
You're indeed right. Behind the scenes we're using AWS S3 SDK client which by default uses the DNS addressing instead of path style addressing. We haven't captured this issue, as we're using MinIO over IPv4 which actually makes AWS client to use path style addressing. This is something we shall be able to fix relatively fast. I will let you know personally once it's fixed. Speaking of bugs and pricing model. Software has bugs regardless if it's free or behind the payment. In Sep/Oct 2022 we've decided to make all major external back-ends free and only charge for self-hosted or custom S3. I would like you to thank you again for reporting this. Please find the promo code for Pro version over e-mail which certainly isn't worth your effort, but hopefully some small gratitude. |
Thanks for the response. I didn't mean to sound crass, I know software isn't bug free as I'm sure there are probably more. It was just discouraging seeing this feature locked behind a paywall that wasn't properly implemented or tested well. Anyways hope you get it all sorted. I'll be sure to update my review on the play store shortly. |
This is now fixed with the release of 1.5.8 which is now live. In other words, by default path-based addressing is used for MinIO. |
Hi, I'm still having issues connecting to the bucket I created. The method I used to create the bucket, username and password I documented here. https://onedr0p.github.io/home-ops/notes/s3-buckets.html#minio Logs from photosync
|
Hi, I didn't have much time today to follow the instructions exactly, however I've created test user and bucket using your IAM policy on MinIO sandbox and I can connect using PhotoSync just fine. Access key ID: test-bucket-write-2 Policy: https://play.minio.io:9443/policies/dGVzdC1idWNrZXQtd3JpdGUtMg== I will have a look on your instructions in more detail next year ! |
Hi again and Happy New Year ! I've tried the script on some test instance:
I've then printed out the:
Everything went fine. I've then removed:
Is it possible that: Perhaps proxy doesn't let the |
Since I haven't heard from you for quite a while, I am going to close this issue for now. |
I'm trying to connect to my local minio instance but this is not able to connect. I get an error but the popup message is truncated.
I'm able to connect to my minio instance using other Android apps like FolderSync.
The text was updated successfully, but these errors were encountered: