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
Interoperability with Minio #10888
Comments
THIS IS THE CONSOLE DEBUG OUTPUT IF I CONNECT TO THE MINIO SERVER IP AND PORT AND THEN ASK TO LIST CONTENTS TO MYBUCKET123
|
THIS IS THE CONSOLE DEBUG OUTPUT IF I USE THE VIRTUAL HOST METHOD IN MINIO e.g http://mybucket123.s3.myserver.com:9000 i have checked the XML output being returned from the minio server using Charles Proxy and its a VALID XML that gets returned with Contents listed for files
|
Please make sure to enable virtual-host-style requests in their Minio configuration. |
Replying to [comment:3 dkocher]:
this is already enabled, as i couldnt access it first time round without setting the MINIO_DOMAIN in docker as it generated a different error but after enabling it, im now getting this XML error as listed above |
ive just tried 7.1.2 with virtual-host-style and that doesn't work either just keeps getting same error
but the log drawer show it returns HTTP/1.1 200 OK with a valid XML too |
Can you provide the captured XML response? |
Replying to [comment:9 dkocher]:
|
ok i think i might have found the problem and maybe a bug but will try explain
|
Thanks for summarizing the issues. Accessing via the hostname set with |
The error when accessing using the bucket name in |
We have requested a documentation update for Minio in minio/docs#280. |
surely it would be a better option to give the user control over path-style or virtual-host-style than forcing the user to use virtual-host-style? |
Replying to [comment:15 si458]:
|
Replying to [comment:16 dkocher]:
thank you that would be helpful! or even a tick box saying saying 'USE PATH-STYLE' in the edit bookmarks window/open connection window |
Replying to [comment:11 si458]:
In e5e2a97. |
Pending change for |
Replying to [comment:11 si458]:
Set the bucket name in the Path setting in the bookmark instead. |
Trying to make cyberduck work with ceph S3, which only supports path style |
Replying to [comment:24 dimm00]:
|
Replying to [comment:25 dkocher]:
Yes. How can I send you credentials to access it? |
Replying to [comment:26 dimm00]:
Awesome. Please write to [mailto:support@cyberduck.io]. |
Replying to [comment:24 dimm00]:
Was that solved? I'm seeing the same problem with Ceph here. |
i dont have this issue anymore as its been fixed in latest cyberduck version using the S3 (HTTPS) profile from the minio help page the only issue i found was when using my home broadband 'virgin media' they take over my dns records, so when cyberduck was looking for 'mybucket.s3.myserver.com' is should of returned blank A record as i only have an A record for 's3.myserver.com' which ment cyberduck would then reverted back to using the path format, but 'virgin media' kept returning an IP address of theres for there stupid advanced search error page, so cyberduck kept trying to connect to them and just timing out instead of an error once i disabled the 'advanced search error page' and rebooted our router and cleared my dns cache on laptop, cyberduck started working without any issues |
Aha. What worked for me now, was to create a bookmark and add the bucket-url to the PATH there. So, worksforme now. Thanks. |
Documentation for Minio in Minio Cloud Storage. |
7.1.2 works without issues
7.2.0 onwards keeps getting an error on just simply listing a bucket contents
Request Error: null. Please contact your web hosting service provider for assistance.
server: minio 2019-10-12T01:39:57Z with --compat option
The text was updated successfully, but these errors were encountered: