Valheim

Valheim

Incompatible version between client and dedicated server after patch
I'm running the Linux client and a Linux dedicated server. When I saw the Aug 30th update drop, I updated the server with steamcmd > app_update 896660 verify, everything worked and it reports as properly updated. The server console readout is showing a version *0.209.10* here:

09/01/2022 09:48:38: Using environment steamid 892970 09/01/2022 09:48:38: Using steam APPID:892970 [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. CAppInfoCacheReadFromDiskThread took 5 milliseconds to initialize Setting breakpad minidump AppID = 892970 [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded. 09/01/2022 09:48:38: Server ID 90071992547409920 09/01/2022 09:48:38: Authentication:k_ESteamNetworkingAvailability_Waiting 09/01/2022 09:48:38: Steam game server initialized 09/01/2022 09:48:38: Using default prefs 09/01/2022 09:48:38: Valheim version:0.209.10

My client is updated to the most recent non-beta branch via the Steam client GUI, and is still showing v0.210.6. When I try to connect to the dedicated server, I get an incompatible version error after providing the server password:

09/01/2022 09:57:37: New connection 09/01/2022 09:57:37: Accepting connection k_EResultOK 09/01/2022 09:57:37: Connecting to Steamworks.SteamNetworkingIdentity 09/01/2022 09:57:37: Got status changed msg k_ESteamNetworkingConnectionState_Connected 09/01/2022 09:57:37: Connected 09/01/2022 09:57:37: Got connection SteamID 76561197960703529 09/01/2022 09:57:37: Got handshake from client 76561197960703529 09/01/2022 09:57:40: VERSION check their:0.210.6 mine:0.209.10 09/01/2022 09:57:40: Peer 76561197960703529 has incompatible version, mine:0.209.10 remote 0.210.6 09/01/2022 09:57:40: RPC_Disconnect

So it looks like the Linux build of the dedicated server (appID 896660) is, or is incorrectly tagged internally as, 209.10, while the client (appID 892970) is correctly 210.6?

Environment:
Server - Ubuntu 18.04, 2007-era dual Xenon rack server of some kind. 16gb RAM.
Client: Debian 11, updated. CPU is intel something, I don't remember (i5 I think?) 1080GTX, 16gb ram. Steam client set to automatic update, no beta branch.
Last edited by He Who Has No Name; Sep 1, 2022 @ 10:13am
Originally posted by He Who Has No Name:
On my machine it ended up being that Steam lost track of where the VDS install was actually located, and it was "updating" a different one it created (one buried in the guts of the file structure somewhere), not the one I thought it was working with. So it was a Steam error, just not the one I thought. Verify your install location and what Steam THINKS is your install location, and that may help fix.
< >
Showing 1-4 of 4 comments
Irongate Smiffe  [developer] Sep 1, 2022 @ 11:50am 
Hi.
Some people have had issues updating linux. But it does work, you just have to close the server down, and push the update like always.

Some linux disps are more difficult than others to do this.
We have on our discord server many many linux users who help eachother out.
Cynnis†er Sep 6, 2022 @ 12:40pm 
I have been having the same issue, only I'm just running it on a Windows 10 PC. Everything has been working fine for months but now I can not get it to update past the 209.10. I have run the update though SteamCMD and it says it updates. I have even tried with .bat files and I get the same outcome. Yes, i'm kind of "new" the server stuff but this has been fun until now lol. I am at a standstill. Any guidance to correct this issue I will be very grateful.

-Thanks in advanced.
A moderator of this forum has indicated that this post answers the original topic.
On my machine it ended up being that Steam lost track of where the VDS install was actually located, and it was "updating" a different one it created (one buried in the guts of the file structure somewhere), not the one I thought it was working with. So it was a Steam error, just not the one I thought. Verify your install location and what Steam THINKS is your install location, and that may help fix.
Last edited by He Who Has No Name; Sep 6, 2022 @ 2:57pm
Cynnis†er Sep 6, 2022 @ 4:56pm 
Originally posted by He Who Has No Name:
On my machine it ended up being that Steam lost track of where the VDS install was actually located, and it was "updating" a different one it created (one buried in the guts of the file structure somewhere), not the one I thought it was working with. So it was a Steam error, just not the one I thought. Verify your install location and what Steam THINKS is your install location, and that may help fix. [/quote
I will give that a try and look around for what I can find. Thank you for the tip. Hopefully it will work.
< >
Showing 1-4 of 4 comments
Per page: 1530 50

Date Posted: Sep 1, 2022 @ 10:06am
Posts: 4