ich777

Sorry but I can't reproduce this error nor do I know why this happens. I run the container on my own Server (granted I'm not on Unraid anymore) and have no issues whatsoever.

Sorry but no, I don't forgive such reports anymore. These are a mess and have too much information a human would never write. However I'll drop the container since I don't support Wayland, you can use the old version but I'm not sure if there are old versions out there.

If my container isn't working for you please try the other one, I simply can't tell why it on some machines doesn't work. Maybe it's the path or better speaking the mount point or something else, I really can't tell. For me it works just fine.

No issue over here with the latest client version and the newest container version. The server is on the latest version 1.1.6, please see here and here. Please check your certs for your domain if they are still valid and the keys are correct.

Please create a post in the General Subforums with your request and why you are requesting those Kernel modules.

Please disable BepInEx.

Please don't change the AppID just leave the credentials out, you are making your life harder that it is. When the credentials marked as not as required (with the red asterisk) then they aren't needed and therefore they broke the game download because you've specified them. Again, if the download fails or the container won't upgrade, simply: Stop the container Delete the steamapps folder Start the container again As for Valheim make also sure you are using at least a six character password and also make sure that the password only consist of alphanumeric characters and letters.

This is the only thing that is a real error. May I ask on what Unraid version are you? Please also try to restart your whole Unraid server. I'm not to sure what causes this line but something is definitely off, the other lines are fine.

Please don't, this is wrong advice and you basically created a new world. Also this is not an error message, this is just a warning that pops up too late, as you can see first it says that the Steam API was initialized successful and the last message is just a warning that it tried to initialize the Steam API before it even was initialized. This message is shown on almost every Steam Dedicated server in that order or vice versa. Please use the container variable WORLD_NAME, not SRV_NAME, my container doesn't support SRV_NAME. As I already said, a re-download is recommended by the game devs, see my post here:

What exact error, this isn't an error, have you yet tried to connect to the server? This is my server and it is working perfectly fine, three people are playing on it: ---Prepare Server--- ---Server ready--- ---Starting Backup daemon--- ---Update check deprecated!--- ---Start Server--- [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK. Setting breakpad minidump AppID = 892970 SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197960265728 [API loaded no] [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

About what container are we talking? What container? When we are talking about Valheim, this isn't an error, the server is running as it should, this is just a warning and the Steam API was initialized correctly.

If the Valheim container doesn't want to update when restarting it do the following: Stop the container Delete the steamapps folder in your Valheim directory Start the container again Please also do note that the developers recommended to start a new world since you could run into world generation issues. Edit: @thymon I've hidden your comment because this is completely overkill and not necessary.

Ups sorry, just saw it, yeah, had to change the .plg file twice and fort the second time to edit that in. Sorry about that and not answering your question appropriately.

For Valheim 1.0 I would recommend to deploy a new container or better speaking with a new path for the Game Files or delete the old ones (of course stop the container first) since the developers said that it could be possible if you've already visited a region that needs to be updated that this might fail, but this has nothing to do with the container and rather the world generation.

Already done: Please read the linked post. Deprecation and to make sure to not make it possible to install it to Unraid releases bigger than 7.3.2 Please do note that CA means Community Applications and therefore I don't think that Limetech has to be responsible for Containers/Plugins and so on, there is even a big disclaimer when you first visit CA about that. Please report that in the General Subforums since the Intel GPU Top plugin or any other plugin has nothing to do, except reporting data back, with drivers, the drivers are built into Unraid itself.