Win10 port binding failedEn

Phenomenon:

bind to b'0.0.0.0':8086 fail:OSError(10013, 'An attempt was made to access a socket in a way that is not permitted by access permissions.', None, 10013, None) OSError: [WinError 10013] An attempt was made to access a socket in a manner not permitted by the access privileges.

Possible Causes:

• The port is occupied by other applications, which can be determined by the following command: netstat -ano |findstr 8085 8085 is the port number of the failed binding, modify it according to the situation.

  If this is the case, closing other applications can fix it. Or modify the port that XX-Net monitors, you can refer to here: [Modify XTunnel port] (Change-Smart-Router-Config) Modify configuration page management port

• The port is reserved by Hyper-V as a dynamic port, which can be determined by the following command:

  netsh int ipv4 show dynamicport tcp

  If it is indeed occupied, it can be modified by the following command:

  netsh int ipv4 set dynamic tcp start=49152 num=16384

  netsh int ipv6 set dynamic tcp start=49152 num=16384

  The computer needs to be restarted after modification.

  Reference article