Opened 10 years ago
Never ever recovers from a network failure. Can't resume a queue. Disconnect/reconnect doesn't fix, only restart
|Reported by:||matteo sisti sette||Owned by:|
|Component version:||Operating system type:||Linux|
|Operating system version:|
If the network becomes unavailable while Filezilla is processing a queue, in most cases the following happens.
When you try in any way to resume the queue that has been interrupted, you get this nonsense error message: "Waiting for replies to skip before sending next command" (I mean a [nonsense error][message], not a [nonsense][error message]).
The client does nothing and just wait forever. It even sends "keep alive commands" from tiem to time but never resume the upload/download queue.
Unchecking and checking the "Process queue" checkbox doesn't fix the issue: the error appears again.
Even disconnecting and reconnecting to the server doesn't help, which is the most nonsense thing.
The only way you can resume the queue is by exiting and restarting FileZilla. There should be a way to "completely reset" the connection and forget about everything as if you exited and reentered File Zilla - actually that should be done when you disconnect and reconnect to the server. Even without that, actually, the client should detect the timeout and do whatever is necessary to resume noral operation automatically.