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

Can't use Cyberduck on my new computer #10684

Closed
cyberduck opened this issue Apr 17, 2019 · 1 comment
Closed

Can't use Cyberduck on my new computer #10684

cyberduck opened this issue Apr 17, 2019 · 1 comment
Labels
bug s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

c2b5e58 created the issue

I entered the wrong ID and PW when I was setting up software on my new computer. Apparently what I found was from 2015 and doesn't work. My boss came me the new information to use but now when I try to enter the correct information I still can't do my work. I know at one time I donated under my own name but for the life of me I can't find that information. So here's what my boss provided. Oh and my new computer is running Windows 10 if that makes any difference.

U:

PW:

Can someone help so I can get back to work?

Thanks!
@cyberduck
Copy link
Collaborator Author

@AliveDevil commented

Please do not post login information online.

To troubleshoot this issue:

  • You can open Cyberduck, but you are unable to connect to the server? What is the error message?
    • You already got the login credentials, please delete any relevant entries from Windows Credential Manager.
  • You cannot open Cyberduck, but get an error message? Can you send a screenshot of that?
  • You can open Cyberduck, connect to your server, but you see a donation prompt: Please recover your license from (https://cyberduck.io/help/)

@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 s3 AWS S3 Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck