I continued docker after get off work, but the problem of connection reset by peer yesterday occurred again. In the article, I recorded that no error was reported when running in the root directory, but an error was still reported today. It seems that the key to the problem is not here. It is said on the Internet: 1. The server’s concurrent connections exceed its capacity, and the server will disconnect some of the connections. If you know that the number of concurrent clients actually connected to the server does not exceed the server's capacity, it may be a virus or Trojan that causes abnormal network traffic. You can use netstat -an to check the network connection status. 2. The customer closes the browser, while the server is still sending data to the customer. ... To sum up all the above, I now suspect that it is related to the network (I doubted the performance of my computer before), which is good and bad, so I am going to use domestic mirroring
I continued docker after get off work, but the problem of connection reset by peer yesterday occurred again. In the article, I recorded that no error was reported when running in the root directory, but an error was still reported today. It seems that the key to the problem is not here.
It is said on the Internet:
1. The server’s concurrent connections exceed its capacity, and the server will disconnect some of the connections.
If you know that the number of concurrent clients actually connected to the server does not exceed the server's capacity, it may be a virus or Trojan that causes abnormal network traffic. You can use netstat -an to check the network connection status.
2. The customer closes the browser, while the server is still sending data to the customer.
...
To sum up all the above, I now suspect that it is related to the network (I doubted the performance of my computer before), which is good and bad, so I am going to use domestic mirroring