Skip to content
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

S3 minio creates untitled folder instead of named folder in mountain duck #11018

Closed
cyberduck opened this issue Apr 5, 2020 · 2 comments
Closed
Assignees
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

1c67bf1 created the issue

Im having a strange issue at the moment and im not sure if its a bug or something else

But every time I create a folder using mountain duck against my minio server,

its just creating an ‘untitled folder’ or ’new folder’ instead of the actually folder name?

But then if I leave the folder named as is ‘untitled folder’ or ’new folder’ and then change the folder name

It just says ’no longer located’ or ‘permission denied’ and then refreshes to show ‘untitled folder’ or ’new folder’ again

ALSO I am then unable to delete the folder as well, I have to go into the backend storage and delete the folder manually

Im using the latest 3.3.6 mountain duck, on both Mac and Windows

My minio is being accessed by https with Traefik as frontend proxying back to minio RELEASE.2020-04-04T05-39-31Z

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Relates to e042ae1.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In cce0377.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants