Unable to Connect to Server, Connection Refused - site down?

[LZappa]

Hello,

My friend Dan and I were in the middle of a turn of Normandy '44 when the connection was lost. Both of us have internet connectivity, so it's not our service. Neither of us can reconnect and we get the message I used in the subject line of this message. Is the VASSAL server down? If so, is there an expected time when it will be back up? Thanks!

Regards,
Leo Zappa

[uckelman]

Thus spake LZappa via messages:
> Hello,
>
> My friend Dan and I were in the middle of a turn of Normandy '44 when
> the connection was lost. Both of us have internet connectivity, so it's
> not our service. Neither of us can reconnect and we get the message I
> used in the subject line of this message. Is the VASSAL server down? If
> so, is there an expected time when it will be back up? Thanks!

The game server was down briefly earlier today. It should be up again
now.
--
J.

[SCataldo]

Hi!

Same problem here.

I've read that turning off the firewall should work, but I'm still unable to connect to server.

What shall I do?

[SCataldo]

Model: Lenovo ThinkPad E15
OS: Windows 10 Pro
CPU: Intel Core i7-10710U CPU 1.10GHz 1.60 GHz
Memory: 32GB
Video: Not sure where to find this info, but I guess is not quite relevant here...
VASSAL: 3.4.12
Java: 15.0.1.0
Module: Paths of Glory 10.1

[uckelman]

Our server hasn't been down today. You're likely having some other sort of connectivity issue.

[SCataldo]

So are there any usual suspects in terms of connectivity (besides internet access of course)? I tried connecting from a Mac, which is not mine, and it worked, so the problem must be my own laptop. What can I do to fix this issue?

Btw, happy new year!

[SCataldo]

It seems to be a problem with Java I guess:

2021-01-01 12:24:36,407 [0-main] INFO VASSAL.launch.StartUp - Starting
2021-01-01 12:24:36,422 [0-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2021-01-01 12:24:36,423 [0-main] INFO VASSAL.launch.StartUp - Java version 15.0.1
2021-01-01 12:24:36,423 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.4.12
2021-01-01 12:24:36,677 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2021-01-01 12:24:41,590 [0-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\santi\Downloads\Paths_of_Glory_10.1 (1).vmod
2021-01-01 12:24:41,760 [0-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2021-01-01 12:24:41,763 [0-SwingWorker-pool-2-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module Paths of Glory
2021-01-01 12:24:41,770 [0-SwingWorker-pool-2-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files\VASSAL-3.4.12\jre\bin\java -Xms256M -Xmx512M -DVASSAL.id=1 -DVASSAL.port=51259 -Duser.home=C:\Users\santi -Duser.dir=C:\Program Files\VASSAL-3.4.12 -cp lib\Vengine.jar VASSAL.launch.Player --load -- C:\Users\santi\Downloads\Paths_of_Glory_10.1 (1).vmod
2021-01-01 12:24:43,041 [1-main] INFO VASSAL.launch.StartUp - Starting
2021-01-01 12:24:43,051 [1-main] INFO VASSAL.launch.StartUp - OS Windows 10 10.0
2021-01-01 12:24:43,051 [1-main] INFO VASSAL.launch.StartUp - Java version 15.0.1
2021-01-01 12:24:43,051 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.4.12
2021-01-01 12:24:43,052 [1-main] INFO VASSAL.launch.Launcher - Player
2021-01-01 12:24:45,872 [1-AWT-EventQueue-0] WARN VASSAL.i18n.BundleHelper - No Translation: Paths of Glory - AP Chat Color
2021-01-01 12:24:45,873 [1-AWT-EventQueue-0] WARN VASSAL.i18n.BundleHelper - No Translation: Paths of Glory - CP Chat Color
2021-01-01 12:24:48,117 [1-AWT-EventQueue-0] INFO VASSAL.launch.BasicModule - Paths of Glory versión 10.1
2021-01-01 12:24:52,815 [1-AWT-EventQueue-0] ERROR VASSAL.chat.node.NodeClientFactory -
2021-01-01 12:24:54,136 [1-AWT-EventQueue-0] INFO VASSAL.build.GameModule - Exiting
2021-01-01 12:24:55,023 [0-IPC receiver for 1080031774] ERROR VASSAL.tools.ipc.IPCMessageReceiver - Error while reading IPC message
java.net.SocketException: Connection reset
at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:323)
at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350)
at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803)
at java.base/java.net.Socket$SocketInputStream.read(Socket.java:981)
at java.base/java.net.Socket$SocketInputStream.read(Socket.java:976)
at java.base/java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2892)
at java.base/java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:3219)
at java.base/java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:3229)
at java.base/java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1663)
at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:519)
at java.base/java.io.ObjectInputStream.readObject(ObjectInputStream.java:477)
at VASSAL.tools.ipc.IPCMessageReceiver.run(IPCMessageReceiver.java:35)
at java.base/java.lang.Thread.run(Thread.java:832)

[uckelman]

It seems to be a problem with Java I guess:

No, not on the basis of the errorLog you posted.

2021-01-01 12:24:55,023 [0-IPC receiver for 1080031774] ERROR VASSAL.tools.ipc.IPCMessageReceiver - Error while reading IPC message

Though this looks like an error, it's not. This happens on Windows a good chunk of the time when you close a socket but the listener doesn't receive the final "close" message before the socket is entirely shut down. From 3.5.0, you won't see this message any more. Additionally, this message is unrelated to communication with our server---the socket in question is one that the Module Manager uses to communicate with any Players or Editors you have open.

I would check for any local firewalls or anti-virus programs blocking traffic. You might also try running VASSAL as Administrator to see if that makes a difference---if so, then it's some sort of account permissions problem that you're having.

[SCataldo]

Thanks for your reply and explanation.

Unfortunately I've already switched off my every single firewall and anti-virus but I'm still unable to play. Neither running VASSAL as administrator worked I'm affraid.

It's so frustrating. I've never had any issues with VASSAl using my good old PC, but it seems that my new laptop, which is so much better than its predecessor, has certain configuration that doesn't work well with VASSAL.

If there isn't any other possible solution to this problem, I'll eagerly look forward to 3.5.0. I hope it is released soon