I've noticed recently (after upgrading to the latest version and also in 3.4.2 - I had been using an old old one 3.1 I think...), that if I leave an SFTP window open for a period of time (I would guess about an hour), and then I try to perform any action, Cyberduck will show the "spinner" at the bottom of the window, but nothing happens. Not even a time out.
I have the following in my ~/.ssh/config file - which used to be enough to stop this problem:
Do newer version of CyberDuck ignore what is present in this file? I've tried version combinations of the commands in the file, and also have a file named ~/.ssh/ssh_config (which some sites suggest it should be), but to no avail.
The text was updated successfully, but these errors were encountered:
The timeout settings are not read from .ssh/config but can be set in the Connection Preferences. However, there must be an issue with stalled SSH connections as noted previously in #3941 and #4214.
I've got a time out setting of 30 seconds (as per default), but the connection "hangs" for a lot longer than that. The "spinner" in the window will simply keep going, as far as I can tell indefinitely (certainly for 10+ minutes).
Regarding the other two bugs, it does sound very similar. Is there a way to stop the session from going stale, and thus working around these issues? It never used to be a problem, but is since I did an upgrade.
I've noticed recently (after upgrading to the latest version and also in 3.4.2 - I had been using an old old one 3.1 I think...), that if I leave an SFTP window open for a period of time (I would guess about an hour), and then I try to perform any action, Cyberduck will show the "spinner" at the bottom of the window, but nothing happens. Not even a time out.
I have the following in my
~/.ssh/config
file - which used to be enough to stop this problem:Do newer version of CyberDuck ignore what is present in this file? I've tried version combinations of the commands in the file, and also have a file named ~/.ssh/ssh_config (which some sites suggest it should be), but to no avail.
The text was updated successfully, but these errors were encountered: