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.

Sign up for GitHub

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

Connection failure with email address as username #11759

Closed
cyberduck opened this issue Aug 9, 2021 · 2 comments
Closed

Connection failure with email address as username #11759

cyberduck opened this issue Aug 9, 2021 · 2 comments
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

f253da5 created the issue

As per #6066, I'm not able to connect using a (registered) latest Cyberduck version (7.10.0, 35184) on Windows 10 when connecting to Koofr service through WebDAV (HTTPS) having an email address as username.

Workaround: edit the saved favourite connection removing the username. Open the connection and when being asked for username and password (the application key) then Cyberduck connects properly.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

The 500 service error indicates a server problem.

@cyberduck
Copy link
Collaborator Author

f253da5 commented

Might be true, but then why the workaround works?

@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.
Assignees
No one assigned
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck