Vassal crashes on startup

Hi there,

I’m having problems running Vassal. It opens normally, but after 5-10 seconds the program crashes without an error message. The window just simply goes away, no matter whether I try to open a module or just leave the program open. Given the error log, it seems java is trying (and failing) to do something, but I’m pretty bad at computers so who knows what.

I’m running Windows 10 64bits, latest version of Java (1.8.0_91) and Vassal (3.2.16)

Here’s the log:

2016-07-04 13:37:50,120 [0-main] INFO VASSAL.launch.StartUp - Starting
2016-07-04 13:37:50,122 [0-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2016-07-04 13:37:50,123 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_91
2016-07-04 13:37:50,123 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.16
2016-07-04 13:37:50,179 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2016-07-04 13:38:11,438 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 13743
2016-07-04 13:38:11,438 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,438 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.ConnectException: Connection timed out: connect
2016-07-04 13:38:11,438 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,439 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2016-07-04 13:38:11,439 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,439 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2016-07-04 13:38:11,439 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,439 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2016-07-04 13:38:11,439 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,440 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2016-07-04 13:38:11,441 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2016-07-04 13:38:11,442 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2016-07-04 13:38:11,442 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

Thanks for the help.

Your first port of call should be this page on the wiki: VASSAL Does Not Start. All the mentions of sockets in that error log usually result from some overly aggressive firewall or internet filtering software (Norton, Avast, et al).

Thanks for the quick answer.

Yeah, I read that, but couldn’t really fix it. I tried disabling the antivirus (AVG) for a bit and made sure that java.exe had access through windows firewall but it doesn’t work. Honestly " If your firewall is blocking the loopback device, set it to permit access to it." goes right over my head.

Any idea what should I tell my firewall to do?