Websocket server can sometimes fail to bind

[qdot]

We're getting multiple reports of users on windows 10 getting the following message:

'Failed to bind: Os { code: 10013, kind: PermissionDenied, message: \\\"An attempt was made to access a socket in a way forbidden by its access permissions.\\\" }': 
C:\\\\Users\\\\runneradmin\\\\.cargo\\\\registry\\\\src\\\\github.com-1ecc6299db9ec823\\\\buttplug-4.0.2\\\\src\\\\connector\\\\transport\\\\websocket\\\\websocket_server.rs:165\\n   

While I'm not sure we can do much about it on our end, it'd be nice to know why this failure happens and how we can tell them to remedy it.

[Yiyiyimu]

Hi @qdot I met with this problem several times and I believe it's due to hyper-v already reserves that port. People could refer to this solution https://github.com/docker/for-win/issues/3171#issuecomment-459205576

[qdot]

@Yiyiyimu Huh, thanks! I'm going to try to improve the error message when this happens, and will also include the link you provided so people can try and free up the port themselves.