Problems:

If you don’t want to bother, restart your computer. But there could be problems next time.

This paper gives two schemes for reference only.

  • Solution a: like other bloggers give solution, using netstat – aon in CMD | findstr searches “1080”, find take up port process of PID, the end of the process in task manager.

  • Solution 2: Possible cause: Many times, however, no process is occupying port 1080, you will find:

Yes, no process is occupying port 1080, but an error is reported.

The problem is not that the port is occupied. You can’t find the program using the port in netstat. In fact, last-error is 10013 (WSAEACCESS), insufficient permissions.

According to known issue KB4074588 published on February 13, 2018, this patch will adjust the reserve Port ranges of the operating system, which can be viewed by running the following command.

netsh interface ipv4 show excludedportrange protocol=tcp
Copy the code

In my own environment, 1027 through 1126 are forcibly reserved by the system, so other applications cannot listen on this port, such as 1080.

In addition to the system patches will retain the port, the Windows 10 hyper-V will also retain the port

Solution:

Change the local port of SSR

Change the localPort to “localPort”: 1780. Here I randomly selected an unreserved port.