Server Crash - Address already in use

[Simeon Weigel]

I have an issue with the new Version of the Vintagestory server. When I execute the start command it says:

VintagestoryServer.exe is up and running!

But it always produces the following output in the server-crash.txt:

Version: v1.15.10 (Stable)12/29/2021 9:17:56 AM: Critical error occurred
System.Net.Sockets.SocketException (0x80004005): Address already in use
  at System.Net.Sockets.Socket.Bind (System.Net.EndPoint localEP) [0x00043] in <4e15bbae9d7043d8afd6cfd50bd9bd5a>:0 
  at Vintagestory.Server.ServerNetManager.StartServer (System.Int32 port, System.String ipAddress) [0x0007d] in <be10c4c7e7ee4ac5b68783f6507c58a7>:0 
  at Vintagestory.Server.TcpNetServer.Start () [0x00000] in <be10c4c7e7ee4ac5b68783f6507c58a7>:0 
  at Vintagestory.Server.ServerMain.AfterSaveGameLoaded () [0x000f1] in <be10c4c7e7ee4ac5b68783f6507c58a7>:0 
  at Vintagestory.Server.ServerMain.Launch () [0x001c9] in <be10c4c7e7ee4ac5b68783f6507c58a7>:0 
  at ‬‏‬‎‭‎‮‌‮‪‭‎‬‫‏‪‬‎‍‍‮.‫‌‏‍‬‏‮‪‮‎‎‏‎‬‌‬‮‮‍‮ () [0x000c8] in <8bc5c61efe484c1d9f0b9dde9f42dc5f>:0 
  at _E5WqgB878qvAOVUQ9yfqu340l7G._XiZO0qHpODOJko3v6YCZBF7Z5Se (System.Threading.ThreadStart ) [0x00007] in <be10c4c7e7ee4ac5b68783f6507c58a7>:0 

When I check the status of the server a few seconds later it will then most likely say:

Data path is /var/vintagestory/data
VintagestoryServer.exe is not running.

[Adolf_Tiller]

same issue with me, there is litterally no information on any of this

 

[Streetwind]

Have you tried restarting the PC completely, to ensure that no zombie process is hogging the address?

[BenLi]

address already in use - most probably not the address, but the TCP port is taken by another process.

two options:

1) there's some dead process taking the port. It also may be that the port was not released by that process when abnormally killed.

2) some other program uses VS' port number 42420

 

in first case - restart helps.

in the second case - replace line "Port": 42420, in serverconfig.json with another port. Or try to see what exactly program takes 42420 port and re-configure it there.

If changing the port number - make sure you connect the client to that new port such as 42425