luckyy

That might be, because I had been on the beta branch for a few weeks before Mistlands update became public. Then I took the beta tags out of my docker settings, and at that time it did update to "stable" Mistland release just fine and have been playing with that for a week or two fine. But perhaps that is what led it to take this "public test" beta they pushed out, and my local steam client didn't, which led me to finding what happened Thanks for the tips, will try those later and see if it does revert the docker to the non-beta build.

I ran into this issue too, and I think I've figured out what's going on... it appears that the Docker is auto-updating to a public testing branch that Valheim released on the 16th. But in the Steam Client, you have to select that beta for your game client to update... I had to go to Properties->Betas->select "public-test" beta. Then my steam client updated, and I was able to connect to the docker again without the "incompatible version" issue. I don't have any real customized settings on my Valheim docker, and no game params defined... it just seems it has auto-selected that "public-test" branch and updated itself from it. And so you must do the same on your steam client, or you'll get the version mismatch. @ich777 any thoughts on why it might be grabbing that test build they put out on 12/16, instead of the default standard branch? I can't see anything in the logs/settings about why it might chose that over the standard build. I am wondering if it was the way they Irongate published it to steam? @Fletcher98 just so you see this-incase you are still stuck.

I have a similar built server to bing's and idles at about ~200 watts from my observation, the smart plug its on reports a 4.95kwh daily average, which puts it closer to a 206watt average over 30 days. Case: Norco 4224 MB: Supermicro X10SLR-F CPU: Xeon E5-2630L v3 @ 1.8ghz (8c/8t) RAM: 32gb DDR4 ECC GPU: none (just onboard vga) ARRAY: 23 drives for 131TB (most are 5400rpm), 2x 512gb NVME in raid-1 cache (supermicro pcie addon board) NETWORK: Mellanox 10gbe fiber pcie 3x 120mm Noctua fans, plus the CPU fan (standard kit it came with) are the only fans in it. Runs 27c in the case, 40c for CPU. Drives are usually around 32-35c idle, upwards of 40-42 if under heavy access. I do let disks spin-down, however only a handful really ever do because of dockers, VMs, other activity. As of this writing only 6 of 23 drives are spun down. And it's reporting 195watts as of this writing. And usually is running about a dozen dockers and 2 VMs at all times for reference. Mover just runs once daily to migrate any cached data to the array (and thus spinning up all drives). Hope that is useful for folks!

I actually set up user scripts this morning to do that, so it would restart/auto update in the wee morning hours. Just "docker restart Valheim" worked as a user script For me I did a custom schedule cron entry of "0 5 * * *" which means 5am, daily. And I made some world changes, and then logged out and immediately restarted my Docker, and those changes were gone when I logged back in (just threw down some ladders as a test). So I would say no, an immediate restart of the docker is NOT saving the world file. I also tried it at about waiting 10 minutes, then restarting and looking for the changes/save. But they were missing then as well. That said, I waited about 30 minutes after I logged out, and restarted the Docker and went back in, the changes were preserved. So I think it's more a matter that the server is auto-saving the world file every so often. And that generally restarting the docker will not lose any changes/progress. But that said, if you were just building or doing something, and the docker restarted immediately, some progress would be lost. I'll update if I can figure out anything more specific in my trials

You can just open the OS console by clicking the Valheim docker icon and selecting "console". That will get you to a Linux shell prompt, but do note that anything you setup in there would get wiped out in a docker container update, or if you changed a docker setting that redeployed the docker (such as server name, ports, etc.)

Restarting the Docker worked for updating my server, it came back up with the latest version. Maybe make sure you've stopped the Docker entirely, and then start it? It should just auto-update. I would say if it's not showing up within a half hour, I'd look to make sure you have the correct ports forwarded on your firewall (and are forwarded correctly). And also make sure your docker "server name" field is correct, that is going to be the name it shows up as in the public server list. By default if you didn't change it on deploying the docker, it's called "Valheim Docker".

Just thought I'd share my experience setting up a Valheim server with this docker app from @ich777(thank you!) You don't need to worry about Steam authentication for Valheim, the default anonymous user can download and host a server (yay!), so no fuss with Steam users or Steam Guard to worry about. Deploy the docker as provided, leaving username & password blank. The Server Name field is important, this is how your name will appear in the public server list in Valheim. (as of this writing there are 7 "Valheim Docker" server names, good luck finding yours! So choose something unique that you and your friends can find. World Name is the name of your world, this can be anything, if you wish to import a single-player or self-hosted save file in your docker, this name must be set to the same name/spelling as your save game world. Save the docker/let it install. You'll want to make sure your firewall or router has UDP ports 2456-2458 forwarded to your Unraid server's IP so the game can work as intended. In 10-15 minutes typically you should see your server name in the public server list in Valheim, you're done! * if you wish to import a previous save file, you need to make sure the Docker is Stopped first. Then browse your local computer's profile, typically in "%appdata%\..\LocalLow\IronGate\Valheim\worlds" you will find your save games. You'll want to take a copy of your world files, database, everything named the same as your world name over to your docker data files, by default with this docker settings should be: \\<your unraid server IP or name>\appdata\valheim\.config\unity3d\IronGate\Valheim\worlds Place your save game files in there, and overwrite any existing newly generated world of the same name with your save game. Start the Docker, wait for it to appear in Valheim, join & play! I hope this was helpful for someone, took a bit to figure out the exact steps to follow