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

Jump to bottom

Open Connection > Amazon S3 Doesn't Allow Custom S3 Servers Anymore #10133

Closed
cyberduck opened this issue Nov 10, 2017 · 1 comment
Closed

Open Connection > Amazon S3 Doesn't Allow Custom S3 Servers Anymore #10133

cyberduck opened this issue Nov 10, 2017 · 1 comment
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Milestone
6.3

Comments

@cyberduck
Copy link
Collaborator

01c024f created the issue

The "Server:" and "Port:" boxes have been grayed out and can't be put in focus to type in.

I'm not sure if this was done on purpose because I don't see the change listed in the changelog.

This was working in version 6.2.9.

Custom S3 servers that I have in my bookmarks and history still work. However, bookmarks cannot be edited to use another S3 server.

This was useful for a Ceph S3 server

Image
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Duplicate for #10120.

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

No branches or pull requests
1 participant
@cyberduck