"connection lost"

[cyrrelsneer]

Hi there,

there was a new update on the Valheim client today coming from Steam and I think ever since then, I cannot connect to the server.
It is probably due to the server running 0.145.6 and the clients version is now 0.146.8, or at least that's my best guess.

Can you confirm this? Is this expected behavior? In case it is, I am going to remove the autoupdate feature in Steam and will first update after your server is being updated.

By the way -thanks so much for this container, highly appreciated! Runs like a charm (before that update ;-) )

[Henchway]

Yep, we're experiencing the same issue.

[prthlr]

same here!

[cyrrelsneer]

Thanks for the confirmation.

Just out of curiosity - do you know how I could continue playing with the backup files that are being created?

[cyrrelsneer]

ah okay, maybe I'll try it, but I am using it as multiplayer so not sure what to do out of it. For now I'll just wait ;-)

The running version shows up when you start the Valheim client, search for your server and in the list it will show the version of the server.

[cyrrelsneer]

so, just downloaded the backup (which contains the whole server, that explains why it's like 600MB in size, maybe I'll deactivate the autobackup feature or so, not sure yet what to do there).
Well the map was like 12mb or so in size and works like a charm being importet into Windows locally.
Would be great to see if I can do changes, upload again into the docker container and check if the changes are there, maybe I'll try that one later as well ;)

[Henchway]

I've got it back up, i had to follow these steps:
#125 (comment)

However, once i did that i had a new seed, i'm guessing it doesn't load the old savegame directly. I then reinitialized the container and everything was back to normal. This updated the server version:

[cyrrelsneer]

Thanks - I just did something else to make it up and running which is a bit easier I guess.

I have recreated the container and changed the autoupdate value to now+5 minutes (I am GMT+2, so I updated at 3pm and 10min):

AUTO_UPDATE_SCHEDULE
10 15 * * *

[Henchway]

Nice, i assumed that it would auto_update at startup anyway. So far i was a bit unsure whether the auto_update was referring to the docker image or the game.

[HeadcaseFargone]

I was able to connect to my world again through Steam after running the auto_update.sh script, but my world was gone. It was a completely new one. Not sure how to restore my old one, though I have multiple backups of the server and world volumes.

[cyrrelsneer]

my .db files are around 12mb in size.

you can read through the thread above - I have copied it locally and it works, you could verify that for you as well.
But other than that I am also out of options, maybe someone else could step in

[HeadcaseFargone]

where can i find the auto_update.sh file?

docker exec -it ContainerName "/bin/bash"
/home/steam/scripts/auto_update.sh

[prthlr]

same problem here @HeadcaseFargone
after reconnecting to the server, the whole map is new.

[HeadcaseFargone]

same problem here @HeadcaseFargone
after reconnecting to the server, the whole map is new.

Okay after running auto_update.sh I had to stop my container, overwrite the files in the world volume with the ones from my backup, restart the container, and then wait about 10 whole minutes before it would respond. It never did show the Game Server connected message, but I was finally able to connect with my old world intact. Phew.

[KyneSilverhide]

Yep, same here. I ran the auto_update.sh script manually, and my entire world was gone... but fortunately I had backups and eevrything seems to be back to normal after moving them back to the docker volume.

I guess the next docker container will include the update, but now I'm a bit scared regarding the AUTO_UPDATE feature...

[Devidian]

Same for me, additionally it seems that if i restart one container (i run 2 servers without problems until now) the other gets broken (game crash but container runs with only the log tail command) But even only one container running does not work.

[TaylorTWBrown]

I had the same issue.

I resolved it by emptying (deleting and recreating) the SteamCMD and server docker volumes. The components were redownloaded and my world came back as expected.

[Devidian]

worked for me too

[npanagop]

Worked for me too. More specifically I deleted valheim/server/ and then run docker-compose up --detach --force-recreate. After a while the server was up and my world loaded normally.