src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '123.123.123:0'

[jrhow2]

I am running the image on an ubuntu system. I have attempted to forward through both the default ports as well as 27015-27016. In both cases, I am getting the following error in the log right when I first try to connect (I have replaced my IP address with '123.123.123.123':

[Server] Startup Completed - Disabling Scene Loading Systems [Server] Shutting down Asynchronous Streaming Registered WarEventMapNode in Chunk: 16,14 Registered WarEventMapNode in Chunk: 16,15 Registered WarEventMapNode in Chunk: 15,16 Registered WarEventMapNode in Chunk: 18,16 Registered WarEventMapNode in Chunk: 16,17 Registered WarEventMapNode in Chunk: 17,17 Registered WarEventMapNode in Chunk: 15,18 src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '123.123.123.123:0' SteamNetworking - SteamNetConnections.ConnectionUpdate: k_ESteamNetworkingConnectionState_Connecting, 4091264416, 131073 SteamServerTransport - Update 4091264416 - k_ESteamNetworkingConnectionState_Connecting src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '123.123.123.123:0' src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '123.123.123.123:0'
Has anyone else experienced this and are there any suggestions on how to get through this?

The strangest thing is that it was working after the new update - I logged on last night and connected like normal, then a few minutes later it just wouldn't connect even though nothing else was changed on my end.

[FabD86]

I thought i was alone with this problem... a few days ago it worked flawless, but since a few days i can't connect anymore. The Server is visible for a few minutes on Steam and vanishes after a while. I also can not connect to the server.
I already fetched the savegame and ran it locally, which worked fine so the savegame is not broken.
Further i looked into the logs and the last successfull login was on the 23rd of july:
src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (825) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0' src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (825) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0' SteamNetworking - SteamNetConnections.ConnectionUpdate: k_ESteamNetworkingConnectionState_Connecting, <SomeID>, <SomeNumber> SteamServerTransport - Update <SomeID> - k_ESteamNetworkingConnectionState_Connecting src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (825) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0' src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (825) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0' SteamNetworking - SteamNetConnections.ConnectionUpdate: k_ESteamNetworkingConnectionState_Connected, <SomeID>, <SomeNumber> SteamServerTransport - Update <SomeID> - k_ESteamNetworkingConnectionState_Connected PlatformSystemBase - BeginAuthSession for SteamID: <SomeSteamID> Result: k_EBeginAuthSessionResultOK

I don't think the Assertion Failed: GetBestRoute2 failed with result 50 is the problem, as this also happened during successfull logins.
But here was the last entry of k_ESteamNetworkingConnectionState_Connected and k_EBeginAuthSessionResultOK.

Here an snippet of a failed login...
src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0' SteamNetworking - SteamNetConnections.ConnectionUpdate: k_ESteamNetworkingConnectionState_Connecting, <SomeID>, <SomeNumber> SteamServerTransport - Update <SomeID> - k_ESteamNetworkingConnectionState_Connecting src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0' src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address '12.34.56.78:0'

SteamServerTransport update seems to be stuck on state k_ESteamNetworkingConnectionState_Connecting.
As it worked before without changes of the container (i did not update before it was broken) and no changes to V Rising (https://steamdb.info/app/1604030/patchnotes/) and the dedicated server (https://steamdb.info/app/1829350/patchnotes/) i assume that there might be changes of steams network layer, which are somewhat incompatible with the dedicated server or client.

[jrhow2]

I've figure out a workaround but I don't really understand the problem. I noticed that if I connected my PC to the network via wifi, then I could connect to the server just fine. Also, my friends on external networks were able to connect just fine. It was only when I connected via ethernet that the server crashed and gave these error. After a BUNCH of troubleshooting, I noticed that if I use "direct connect" with my internal ip (e.g. 192.168.0.128:27015) WITHOUT checking the LAN connection box, then it works just fine and the server doesn't crash. My friends externally/on my wifi network can still connect via the server list as usual. I think this must have something to do with how the server/Steam are handling networking, but I don't know nearly enough about this to say what/why this is happening. For now it is annoying, but this seems to work. The only issue is that if I accidentally hit "Continue" then it tries to connect via the server list and the server crashes.

[FabD86]

I think i found the culprit. At least for me but this might also explain why your workaround works.
Playing with the game settings did not do anything. Then i transfered the save files to my local PC. downloaded via steam the Dedicated server started it via lutris + proton and tested locally. Worked flawless. (Note: With Password i needed to NOT check the local network hook, w/o password i needed to select the local network hook). Now i adjusted the port forwarding and it worked also online... When changing the port forwarding i realized a difference between my server and my machine. My server only had an IPv4, but my machine had IPv4 and IPv6... Enabled IPv6 in the dhcpcd config of my Server and reset the connection config in the router. And since then it worked. But why the IPv6 is now needed, i don't know.

tldr;
IPv6 was disabled on my server, enabled and it worked...

[jrhow2]

I enabled IPv6 on my router and my container is on "host" networking mode. Having IPv6 doesn't seem to have fixed the problem for me unfortunately.

[FabD86]

Just tested today to connect with the ipv6 port forwarding disabled (not disabled ipv6)... maybe it was more the resetting of the connection in the router...

[egardan]

I am also experiencing this issue. The container is hosted on a QNAP NAS. Going to provide some details here in case this helps anyone.

• Connecting to the game on a local network through the game browser causes the server to crash
• Connecting to the game on a local network directly to the server's IP works fine
• IPV6 settings seemed to have no effect
• Players outside of the local network can connect without issues but then some specific players cause the server to crash when disconnecting

[TrueOsiris]

investigating.

[sammychurchill]

I am having the same issue running this in Unraid and also didn't have any luck with ensuring IPv6 is on. My issue is when anyone does not connect locally leaves it causes the server app to "crash" (on any connection attempt after a non-local user leaves, the connection fails and logs src\steamnetworkingsockets\clientlib\steamnetworkingsockets_lowlevel.cpp (901) : Assertion Failed: GetBestRoute2 failed with result 50 for address 'xxx.xxx.xxx.xxx:0')

The thing that might be interesting is that I was previously using https://hub.docker.com/r/ich777/steamcmd/ on my Unraid server using the community app https://forums.unraid.net/topic/79530-support-ich777-gameserver-dockers/ and was getting the same error so I swapped to using this repo/container setup to try and resolve the issue but it is occurring in both...

This leads to the conclusion that there is something with the game server itself or an interaction with Wine/networking/steam connect but this is as far as I could track things down

[Kenitosa]

investigating.

update still a problem

I did an update on the server today, with updated docker, seems to have fixed the issue for now.

[Kenitosa]

investigating.

Hey and sorry for pinging, have you figured out the issue?

[brynmathias]

Seeing the same
I've tried a container rebuild locally, but to no effect
I am assuming given the steam libraries haven't updated in 11 months that there's something wrong in the game server, or wine

[Kenitosa]

Was running ubuntu 22. upgraded to 24 now, seems to have done the trick atleast been stable for almost 24 hours it crased within 5 minutes earlier so might be fixed.

update 5 days later
Was stable for 5 days, now back to being the same

[jedis00]

Having the same issue.

https://www.reddit.com/r/Amp/comments/1m9svtn/comment/n7p8c1x

Setting the "LanMode": true in my ServerHostSettings.json seems to have fixed it. Players did also have to click the LAN checkbox, even if they weren't on the LAN.

[jedis00]

investigating.

Any update?

[intangir]

I've been seeing this frequently on my own server , that isn't even running in docker

sometimes within less than a day (usually about a day and a half)

it runs on a VM in wine, similarly, but not the same

also my other server running brutal runs for weeks without an issue, the exact same configuration... (except brutal)

and it doesn't crash out, it just sits there 'running' doing nothing, if it at least crashed out i could auto restart