The SSH connection of xshell frequently prompts socket error event: 32 error: 10053
1. Cancel the check at the tunnel
2 modify/etc/SSH/sshd_ Configuration file under config
Change the value of clientaliveinterval to 60
Then restart the ssh server
At present, there is no frequent SSH disconnection problem, which should be effective
Read More:
- Vue element El input search to achieve anti shake @ input event requests frequently
- When xshell 6 is connected normally for the first time, it will prompt could not connect to ‘127.0.0.1’ (port 61708): connection failed
- Error condition on socket for Sync: connection reused
- Solution of xshell error report on 2021.05.03
- The socket connection was aborted in WCF
- [Solved] VUE3.0 Warning: Added non-passive event listener to a scroll-blocking ‘mousewheel‘ event如何解决
- [resolved] exception java.net.ConnectException : Error opening socket to server Connection timed out.
- About connection reset by peer: socket write error
- Frequently asked questions about docker
- RTMP_Connect0, failed to connect socket. 110 (Connection timed out)
- Xshell 6 opens with an error prompt FlexNet_ Licensing
- Winscp failed to upload the file to the server, indicating permission denied with return code 3
- Error in installing RVM on MacOS raw.githubusercontent.com:443 Connection failure resolution
- What should be paid attention to in socket programming — bind socket error: address already in use
- Mongodb uses Mongo to report error: could’t connect to server 127.0.0.1:27017, connection attempt failed: socket
- Windows can’t delete the file, indicating that it is in use. (release of document occupation)
- Connection authorization failure occurred. Reason: local security service non retryable error solution
- The solution to frequently pop up “cannot find a valid baseurl for repo” error prompt box in CentOS 6.7
- Resolve the problem of “event ID 4107” or “event ID 11” errors recorded in the application logs of windows and windows server
- The problem of MySQL database connection failure errno: 1049 error