I get this quite frequently actually, it can be fixed by running this on terminal:
sudo lsof -i :53640
Then enter your password if prompted
This will show you a list of processes using port 53640
Then take the PID number in the list and use it in this command:
sudo kill -9 PID
I think what happens is the server process fails for what ever reason, and fails to close itself, which is why you can’t start another server.
So on my iMac I got a list of things using that PID number, and killed them, that seemed to work. I went to test another psuedo server, and it booted the server like before, but again the client failed. And now when I run that cmd you gave me again, it shows even more D:
Might not want to mark solution yet, because this is definitely still a problem with Studio. The test server fails to open properly about 50% of the time, and then the port becomes completely glitched (preventing any subsequent test servers from starting) until you manually clear the port, either by restarting your computer or using the very helpful process posted by @Baumz.
When I do this, and I do it frequently because it often breaks, I get a list of PIDs, and then I kill them using the command Baumz. I get the problem at home and when I’m at school (I’m at a boarding school). They both use BT internet.
I’ll post the output specifically when I have this issue again.
Unsure quite what you mean. In the times before it breaks, I seemed to notice that all three (1 server, 2 clients) seemed to snap shut rather than the client, client, server order it used to be, however I haven’t had this problem much recently, so I can’t really say how accurate these recollections are.
Sorry I couldn’t be of more use , but thanks for looking into it!