Vassal start-up problem - error log below

Technical Support & Bugs
1

Suddenly no longer able to start Vassal.exe. The list of modules briefly flashes on the screen, and then disappears. It followed your instructions, and it is not the AV software (ESET). Here is the error log:
2021-10-23 14:17:33,843 [7060-main] INFO VASSAL.launch.StartUp - Starting
2021-10-23 14:17:33,859 [7060-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2021-10-23 14:17:33,859 [7060-main] INFO VASSAL.launch.StartUp - Java version 16
2021-10-23 14:17:33,859 [7060-main] INFO VASSAL.launch.StartUp - VASSAL version 3.5.8
2021-10-23 14:17:33,921 [7060-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2021-10-23 14:17:35,061 [7060-main] ERROR VASSAL.launch.ModuleManager - VASSAL: Problem with socket on port 59043
java.net.ConnectException: Connection timed out: connect
at java.base/sun.nio.ch.Net.connect0(Native Method)
at java.base/sun.nio.ch.Net.connect(Net.java:576)
at java.base/sun.nio.ch.Net.connect(Net.java:565)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:588)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333)
at java.base/java.net.Socket.connect(Socket.java:645)
at java.base/java.net.Socket.connect(Socket.java:595)
at java.base/java.net.Socket.(Socket.java:519)
at java.base/java.net.Socket.(Socket.java:293)
at VASSAL.launch.ModuleManager.main(ModuleManager.java:222)

Any help would be appreciated. I have never experienced any problems with Vassal prior to today.
Thank you.
Regards,
Howard

2

The error indicates that the Module Manager isn’t able to open a socket. That’s usually caused by AV software or an overzealous local firewall. What instructions are you referring to?

3

I was referring to the instruction to check the two executable files to see if the AV had blocked them. It had not. However, based on your kind suggestion, I disabled the firewall and the program started. I was able to enable it right afterwards. It is a new version of the AV software which I downloaded late yesterday.
Thank you very much for your assistance! -Howard

4

Having determined the cause of the problem, I’d check whether your local firewall has a setting for permitting connections on the loopback interface. That connection the Module Manager was trying to make is on a purely local network interface, which has your own machine on both ends—it’s not connection to the internet or even your local network.

5

Thanks, again for your assistance! I will check the Firewall program, and if necessary, contact ESET.