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

CANNOT LOG IN AFTER CHANGING & SAVING NEW PASSWORD. UNABLE TO SAVE NEW PASSWORD. #10085

Closed
cyberduck opened this issue Sep 20, 2017 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

7bfb912 created the issue

I use CyberDuck on Windows 10. I recently changed the password to one of my servers that I regularly access with CyberDuck via SFTP. I have the server bookmarked in the app. However, even though I updated and saved my new password for this server on CyberDuck I am unable to log in. I keep getting the pop-up message:

"Socket closed. The connection attempt was rejected. The server may be down, or your network may not be properly configured. Please contact your web hosting"

It's become clear to me, that CyberDuck won't save the new password, no matter how many times I try. I know this because in the pop up message, I'm asked to enter my credentials again, and I noticed that the password that is saved, has much fewer characters that my new password. Which means CyberDuck didn't save it even though I asked it to.

I am only able to log in when I manually enter my password which is annoying because I have to do it constantly. I want CyberDuck to save my new password.

I have tried deleting the bookmark, and opening a new connection, with a new bookmark, but it doesn't work. CyberDuck still remembers the old password for this server instead of saving the new one.

How do I solve this problem?

NOTE: I am using CyberDuck 5.4.4. because there because the ability to queue transfers (a feature I need & use regularly) has stopped working since the release of CyberDuck 6.

I posted a ticket about and even shared my complaint publicly, but the issue has yet to be fixed. Until it is, I won't be updating CyberDuck.

Complaint: http://bit.ly/2uogBBO
Support Ticket: https://trac.cyberduck.io/ticket/10044

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please try to remove the file %AppData%\iterate_GmbH\Cyberduck.exe_Url_*\user.config.

@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.
Projects
None yet
Development

No branches or pull requests

1 participant