Shulou(Shulou.com)06/01 Report--

VPS loaded with lnmp Times network error:software caused connection abort solution, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Yesterday, opened a new VPS, in repeated installation of lnmp has been forced to stop because of an error prompt, and I also found a lot of ways, one of which is to add a value to the sshd_config file: TCPKeepAlive yes, I did not use this, I used another method, the same is to modify this file!

Step 1: SSH instruction input: vi / etc/ssh/sshd_config and then enter

Step 2: press the key until you find the end here, and you will see a sentence about the penultimate line 20: ClientAliveInterval 0

Step 3: change the number 0 to 60

Step 4: press esc, press ctrl+Q, enter wq, enter and save!

Step 5: service sshd restart restart the service

The above methods are given to me by the supplier of the VPS, but I think the most important thing is that the ping value of this VPS is a little high!

Option 1:

1. Set "Sending of null packets to keep session active" in putty's Connection project, that is, to send a null packet every few seconds so that session will not timeout

two。 In the / etc/ssh/sshd_config setting of sshd host: TCPKeepAlive yes

Option 2:

Modify the / etc/ssh/sshd.config file in the server, set the value of LoginGraceTime to 0, the default is 2m, set TCPKeepAlive to yes, and then use service sshd restart to restart the sshd service, which is fine.

Add:

In sshd_config, there is a LoginGraceTime variable, whose value parameter is seconds, indicating that when the user logs in with ssh, but does not enter a password, the link will be broken automatically after how many seconds.

This variable works fine under x86 and S9 of S10. But when it comes to the sparc model of S 10, it doesn't work.

Although at the specified time, sshd [3968]: [ID 800047 auth.crit] monitor fatal: Timeout before authentication for 135.252.106.61 will be printed in the system / var/adm/messages

But in fact, it will not break the chain, still waiting for the user to enter the password. And it must be entered correctly before the chain is broken automatically.

Option 3:

Step 1: SSH instruction input: vi / etc/ssh/sshd_config and then enter

Step 2: press the key until you find the end here, and you will see a sentence about the penultimate line 20: ClientAliveInterval 0

Step 3: change the number 0 to 60

Step 4: press esc, press ctrl+Q, enter wq, enter and save!

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.