Frequently Asked Questions



CWSRestart can't kick players

Make sure that you are running CWSRestart as administrator. If CWSRestart has elevated privileges, you should see a message in the log right after starting the tool.

What are the requirements for CWSRestart?

I test all my builds on a Windows 8 Professional x64 machine. In addition, I have a Windows Server 2008 R2 VM, where I test the tools as well. However, the compatibility is given be the .Net Framework 4.5. This supports Windows Vista SP2, Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2008 SP2, Windows Server 2012 and Windows 8 (everything in x64 and x86).

Feature such as kicking and banning require administrative privileges.

Why is CWSWeb asking for administrative privileges?

CWSWeb needs to enter itself into your access control list, to listen for traffic. This is only required on the first startup, or if you change the port of CWSWeb.

How do I get the web interface?

The web interface is not part of the default CWSRestart package. You can download it seperately. Just look for CWSWeb. In order to use CWSWeb, you need to enable CWSProtocol.

CWSWeb is displaying "Could not connect to CWSRestart" or "Connection to CWSRestart timed out"

Please make sure that you have started CWSProtocol in CWSRestart. There is a button on the left hand site.

How do I change the port of CWSWeb?

You can specify the port of CWSWeb, by starting it with CWSWeb Port. For instance, you can use CWSWeb 80 to listen for traffic on the default port 80.