cshellen

yes it was working fine, yesteraday steam client updated, and since then i am not able to join. i've already attempted to restart / uninstall / reinstall the game client ,and server container several times. i must be missing something.

when i launch the game client from steam, and attempt to join, i get the following error; "The version of the game and server are different"

error when trying to update craftopia server Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory ^ pulled this from the logfiles, after getting error mismatch after a steamclient update. rebooting the container in unraid doesn't udpate the server. If you also navigate to the steamcmd and attempted to update that way. same issue; /serverdata/steamcmd# ./steamcmd.sh did some scowering and found this article; https://forum.scssoft.com/viewtopic.php?t=319994 LsHallo wrote: ↑15 May 2023 11:02 Hello, I have used the dedicated server inside my docker container: https://github.com/LsHallo/ets2-dedicated-convoy-server. I worked fine and I could play on the server just fine. Since yesterday I got reports that the server crashes while starting: https://github.com/LsHallo/ets2-dedicat ... r/issues/6 I can replicate these issues when downloading a fresh install of the server. I have also searched the steamcmd and ets2 server directory for "steamservice.so" using find (find /app -name "steamservice.so", find /root/.steam/ -name "steamservice.so") but I could not find the required library file anywhere. Is there a new dependency that is missing with the latest server or have I not looked hard enough to find "steamservice.so"? Where can I get the required file? Hello, missing steamservice.so is not an issue. Problem in your case is that logOn to your account has failed (error code from steam simply states - denied). If you are using logOn token for game servers, please check that it is still valid (it can deprecate) - https://steamcommunity.com/dev/managegameservers Also check that you are not logged elsewhere or that this token is not used twice. If you remove logOn token and use anonymous account it should work also (without persistent id).