Problem with socket on port 52834

Technical Support & Bugs
1

When I start Vassal it stops within a couple of seconds. When I look in the error log I see the following:

2022-09-17 00:17:06,853 [21368-main] INFO VASSAL.launch.StartUp - Starting
2022-09-17 00:17:06,861 [21368-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0 amd64
2022-09-17 00:17:06,862 [21368-main] INFO VASSAL.launch.StartUp - Java version 18.0.1
2022-09-17 00:17:06,862 [21368-main] INFO VASSAL.launch.StartUp - Java home C:\Program Files\VASSAL-3.6.7\jre
2022-09-17 00:17:06,862 [21368-main] INFO VASSAL.launch.StartUp - VASSAL version 3.6.7
2022-09-17 00:17:06,946 [21368-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2022-09-17 00:17:10,099 [21368-main] ERROR VASSAL.launch.ModuleManager - VASSAL: Problem with socket on port 52834
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:579)
at java.base/sun.nio.ch.Net.connect(Net.java:568)
at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:585)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
at java.base/java.net.Socket.connect(Socket.java:633)
at java.base/java.net.Socket.connect(Socket.java:583)
at java.base/java.net.Socket.(Socket.java:507)
at java.base/java.net.Socket.(Socket.java:287)
at VASSAL.launch.ModuleManager.main(ModuleManager.java:229)

2

What’s happening is that the Module Manager isn’t able to connect to the socket it opens for communication with itself.

You should check whether something on your machine is blocking connections over the loopback interface—possibly a firewall or Windows Defender.