It could be because the computer is idle for more than 15 minutes. But I am pretty that the internet was not disconnected.
I wonder why FileZilla disconnects itself, maybe my computer's connection has gone for more than 20 seconds while I am gone. To prevent FileZilla in disconnecting itself you need to disable it by setting “Timeout in seconds” to “0” Its description reads: "If no data is sent or received during an operation for longer than the specified time, the connection will be closed and FileZilla will try to reconnect". In the "Timeout in seconds" you can set it to "0" to disable it. I did a second look on the settings and I found out two settings that is somewhat related to being online.
Looking at the settings I could not find any "direct" settings that let FileZilla online all the time (including during idle time and or the screen is locked). But to my surprise when I unlocked my computer, I found out that FileZilla disconnects itself.
Filezilla keeps disconnecting download#
I left the computer feeling confident that FileZilla will continue to download without interruption. Before I left my computer, I did lock it pressing "Winkey + L" on the keyboard. In my case I went out of the office during break time. The countdown animation could be optional if it's too much programming effort to do so.For those who are using FileZilla for uploading and downloading files on FTP servers you may find it annoying that it disconnects automatically after a period of time (especially when the computer is idle). The 30 seconds can then be an option inside configuration or use the same value as the existing reconnect option (which I assume is for Foreground transfers). Where the 30 seconds would count down and when it reaches 0 it will press that button. Now I don't know how complex that would be in your program, but I can't believe it would be "that" complex compared to how the rest of the program functions. I've seen many programs that offer simelair dialogs, but then they have a countdown timer go that if no other option is selected, that option is automatically selected. The dialog on disconnect with the "ok" or "reconnect" options is indeed a bad one to wake up to when you find out a background file transfer only worked for half an hour and has been sitting with that prompt the entire night. I think the first idea is the best - use UI cues to indicate that the connection has been lost, and automatically reconnect as soon as the user tries to do anything (e.g., refresh, change working directory, etc.). The bottom line is, it *is* very inconvenient to have that alert box popping up all the time when there is a connection lost, for whatever reason. On Network error: Connection reset by peer (when Idle) automatically reconnect (in combination with sftp accounts above). Kill the Idle mode (send a ftp command or whatever) every X seconds (this in combination with different sftp accounts so a user can chose if he/she wants this option on/off, just like auto resume transfer thingie) I would gladly reconnect on my own convenience (trust me Alert boxes ARE annoying). Lose the Alert box (leave the rest as is, graying out the remote side as n00ge suggests would be great). I would like to suggest a couple of options: I have the same issue and it IS annoying, especially when you are working outside WinSCP.
0 kommentar(er)
