Open projecthate opened 7 months ago
@projecthate Which versions do you use of NppFTP, N++, Windows and which kind of connection? There are some open issue on this e.g. https://github.com/ashkulz/NppFTP/issues/290 or https://github.com/ashkulz/NppFTP/issues/1
In the profile settings for a connection you can set a timeout value.
@chcg I just updated the plugin, without noting the former version number. Truthfully, I didn't realize N++ didn't auto-update plugins. Currently 0.29.13 - I'll post again with an update after seeing if it solved the issue.
N++ is v8.6.2
Windows 10
Passive/Binary connection. I believe I've tried the other 3 permutations and they either don't work for my server or the same issue persists.
Thanks for your assistance.
@chcg It's still happening after NppFTP update
Anyone who has an insight and inclined to share would be greatly appreciated
Seems current NppFTP 0.29.13 could recover successfully from timeout in case of a plain FTP connection, but not for FTPS/FTPES. Unclear how SFTP behaves. It seems the spontaneous server response 421 for inactivity never reaches the client code or at least is not handled there. The response just appears at the start of the next FTP request.
@chcg my connection is plain FTP and is still experiencing the issue
I'm not sure I can provide a use case. It seems to be specific to my environment, and I wouldn't want to post credentials for others to test. Hosting support has been no help.
I am connected to one server most of the day, if I have 15+ minutes without any traffic to it, when I trigger an upload, it invariably fails, after almost 2 minutes of attempting.
So, the question is: 1) Is there a way to hasten this attempt interval? I have server timeout set to 5s, but I guess that's just for initial connection attempt? 2) Is there a way to force the plugin to close the connection on an interval?