Dedicated server

[LeftyRedd]

The 212.9 update happened and now I can't play on my dedicated server, which is 212.7 even though the dedicated server app you can download also updated. I'm really new to dedicated servers and wondering how to fix this or do I have to wait for another update to the DS?

[Fadeway]

If it's still on the old version then it clearly didn't update. You could manually run the updater, or do as I did and just rename the server and create a new one in its spot. You only need to keep your old save, for me its in a folder called "worlds_local".

[Aldoss]

Publicado originalmente por Fadeway:

If it's still on the old version then it clearly didn't update. You could manually run the updater, or do as I did and just rename the server and create a new one in its spot. You only need to keep your old save, for me its in a folder called "worlds_local".

Any chance you can elaborate any more? I initially had this exact same error, but only on my wife's pc. For me, I was able to begin the connection, but would immediately fail to connect. After I restarted the server, my wife no longer sees the incorrect patch error and now just fails to connect as well as me.

I'm not quite sure what you mean by "create a new on in its spot".

Does that mean I should rename the original batch file (mine is called "run_me_for_server.bat") to something new (e.g. "old_server_do_not_use.bat") and make a new .bat file with the correct world information? Do I need to change the server name in the .bat file or can it be what it was before?

Thanks

[GlassDeviant]

Or server remained on 212.7 while our clients updated to 212.9. I had to log into my host provider and stop the server, click the update button, then restart the server.

[Aldoss]

Publicado originalmente por GlassDeviant:

Or server remained on 212.7 while our clients updated to 212.9. I had to log into my host provider and stop the server, click the update button, then restart the server.

In my case, steam says this is fully updated, but the server still seems to be failing to run. It's getting hung up on loading shaders and not progressing past that point.

Here's the hang up:

12/21/2022 14:15:56: Loading 232885 zdos , my id 1448856856 data version:29
12/21/2022 14:15:57: Loaded 100000 dead zdos
12/21/2022 14:15:57: Removed 0 OLD generated ZDOS
12/21/2022 14:15:57: Loaded 10036 locations
The shader Hidden/Dof/DepthOfFieldHdr (UnityEngine.Shader) on effect Main Camera (UnityStandardAssets.ImageEffects.DepthOfField) is not supported on this platform!
The image effect Main Camera (UnityStandardAssets.ImageEffects.DepthOfField) has been disabled as it's not supported on the current platform.
The shader Hidden/SunShaftsComposite (UnityEngine.Shader) on effect Main Camera (UnityStandardAssets.ImageEffects.SunShafts) is not supported on this platform!
The shader Hidden/SimpleClear (UnityEngine.Shader) on effect Main Camera (UnityStandardAssets.ImageEffects.SunShafts) is not supported on this platform!
The image effect Main Camera (UnityStandardAssets.ImageEffects.SunShafts) has been disabled as it's not supported on the current platform.

After that it just stops.

Edit - I can run the original "start_headless_server.bat" and even though it outputs the same shader errors, it moves on and a server starts. But when I copy that file and change the info in it to the correct world, it still hangs up on this shader load error.

[GlassDeviant]

Hmm...I don';t even know what hardware my server runs on; it's a generic host, probably running in a VM.

[LeftyRedd]

I just use the Valheim Dedicated Server thingy you get from Steam. For those doing it that way, Fadeway was right. I just right clicked and edited the start_headless_server batch file in the VDS folder and changed the server name. Just that, for some reason, put the server to 212.9 and made it playable.

[Fadeway]

Personally I use https://github.com/lloesche/valheim-server-docker
This runs in a VM (docker container), so I deleted the container to force it to recreate everything. That fixed things for me. If you are also in a docker environment, like cloud hosted or whatever, type "docker container ls" and then "docker container rm <container id>" or "docker container rename <name> <newName>".
I'm not sure how the VHDS thing from Steam works in terms of backend, I am a bit surprised that you got it working by just renaming the server, but thats good. I would expect it to be necessary to delete the valheim-server binary, and my naive first attempt would have been to just delete/archive the folder and create it anew. If VHDS is virtualized, same deal as above, need to find the docker container and get rid of it.
Obviously, if you start nuking folders, make sure to backup your world files.