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

SFTP connection failed #9477

Closed
cyberduck opened this issue Apr 19, 2016 · 0 comments
Closed

SFTP connection failed #9477

cyberduck opened this issue Apr 19, 2016 · 0 comments

Comments

@cyberduck
Copy link
Collaborator

741f09b created the issue

Hi again,

Please disregard my message. I wanted to update my previous description. It seems like it was our servers error and this had nothing to do with Cyberduck whatsoever. I am so sorry for the inconvenience. Keep up the great job! Thanks again!

Best,
Magda.

Hi,

I am working on a Macbook Air running OSX El Capitan 10.11.4 with Cyberduck Version 4.9.1 (19769). I used to establish that particular SFTP connection a lot a couple of days ago but something happened and I needed to format my Mac so now that I updated my OSX and the Cyberduck I am getting "Connection failed: Server closed connection during identification exchange. The connection attempt was rejected. The server may be down, or your network may not be properly configured." This is whenever I try to establish an sftp connection I used to establish with the same settings before the format and the new versions. I have my firewall off in the Mac settings and file sharing and remote login checked as well (enabled) in my settings. I have also disabled SIP for Mac just in case this interferes. Do you have any ideas what is causing the problem and could you help me fix it because my work relies on that connection? Thanks a lot.

P.S. I should also mention that the connection I was using before with Cyberduck regards a connection through and ssh tunnel. I am using the program ssh tunnel for mac to establish the tunnel to the second server for my work and then I use Cyberduck in order to connect localhost to that second server from my local 1024 port giving the username and password of the second server. This is exactly what I did before and it was working normally with previous versions before the format and update. Now even though ssh tunnel connects normally, cyberduck does not allow me to connect this way.

Best regards,
Magda.

@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