Not able to anonymously directly connect to subfolder of s3.amazonaws.com #9647
Comments
I cannot reproduce this issue with below connection details. |
See attached a recommended bookmark configuration. |
Please let us know if you still see this issue with the latest snapshot build available for testing for macOS [1]. Please let us know if that resolves the bug reported. [1] https://snapshots.mountainduck.io/Mountain%20Duck-1.5.0.4585.zip |
With the newest snapshot, I got the same error ("Listing directory RocklandSample failed"). but when I clicked on "Retry" it suddenly worked. This was not the case before (had clicked Retry several times). This is already great! Thanks so much for your quick response & help! Best, Andy |
Dear Cyber/Mountainduck staff,
I recently purchased mountainduck to connect to a folder of the s3 bucket system which is available using an anonymous account (http://fcon_1000.projects.nitrc.org/indi/enhanced/sharing_neuro.html).
However, both Cyber and Mountainduck report errors when connecting to the folder directly.
(The folder is under fcp-indi/data/Projects/RocklandSample on the s3.amazonaws.com).
Strangely, if I connect to the s3 root with cyberduck and choose "Go to Folder..." and enter the folder, I can access it.
A colleague told me that he could access the folder directly on a mac using an older version of CyberDuck.
So I think there is a timeout issue when connecting to the folder directly.
It would be awesome to get feedback on this!
Best, Andy
Attachments
Screen Shot 2016-08-09 at 17.49.20.png(111.7 KiB)fcp-indi.s3.amazonaws.com – S3.duck(0.6 KiB)The text was updated successfully, but these errors were encountered: