But, it also happened when SSH'ing into the server. It happened mostly when transferring files to the server hosting the Beamtic websites. The sad detailsįirst I suspected this was a configuration problem, but I later learned it can be caused by a NAT firewall dropping idle connections. The alive messages will be sent through the encrypted channel, so it will not be spoofable. Probably the settings are controlled by the server entirely, so you need to change these settings on the server-side. We probably need to use both ClientAliveInterval and ServerAliveInterval, but I have not tested this personally. It will try to send a package 3 times before the connection in finally dropped. The above will instruct the SSH client to send a type of "keep alive" package after the client has been inactive for 100 seconds. In order to fix the problem, I SSH'ed into my server and modified a configuration file, first we have the /etc/ssh/sshd_config file: I actually thought it was an issue with FileZilla at some point.ġ. This might also help explain why I have not had this problem before, until very recently, where it starting to get really bad. This means that even your home router could be the cause of the problem. Probably, there is still some use for long timeouts, such as when on bad WiFi-so I do not recommend lowering it too much.Īpparently the problem with dropped connections happens due to routers and firewalls dropping idle connections. I do not know if there is a technical reason for timeouts to be so long, now that many of us have very fast and stable internet connections. There is quite an annoying problem with both ssh and SFTP (SSH File Transfer Protocol) connections dropping constantly, this is especially annoying when connecting via SFTP in FileZilla, since, typically, network timeouts is extremely long which causes a delay of several seconds before reconnecting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |