ich777

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.

The saves directory. However you vould also stop the container, delete all files and start the container again, this will take a bit longer since it has to download the game files again but they are not too big.

Yes, will be still maintained. Yes.

Hi everyone, as many of you might have noticed, I haven't been around much lately, so I wanted to let you know that I've moved on and am no longer actively maintaining my plugins and drivers for Unraid. The driver compilation will remain in place as long as the drivers compile and no major issues come up, though testing has gotten a lot harder for me these days. If one of my plugins stops working for you, feel free to fork it and republish it on the CA App, I'd be happy about that! I'll still stop by from time to time and fix whatever I can. I don't think this will have a big impact anyway, since Unraid is switching to a new base distribution in the near future, which would have meant redoing the plugin compilation and everything around it anyway. It was a lot of fun. I learned a lot and had many great conversations with the people here on the Forums and Discord, and also with the whole Unraid Team. Thanks for everything, guys! Take care, everyone!

It's already finished and you see the server running and that the server saves player/world data in intervals which is normal.

Man, how I hate those AI reports... xD Sorry guys, I don't run Unraid anymore and I also don't have a Ugreen Box to test, I'll now fully deprecated the plugin. Feel free to fork the plugin and update it.

Your GPU fell from the BUS, could be caused by anything: Sep 4 15:21:17 DellBox kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 237 Sep 4 15:21:17 DellBox kernel: Sep 4 15:21:17 DellBox kernel: nvidia 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible Sep 4 15:21:17 DellBox kernel: NVRM: The NVIDIA GPU 0000:04:00.0 Sep 4 15:21:17 DellBox kernel: NVRM: (PCI ID: 10de:1eb8) installed in this system has Sep 4 15:21:17 DellBox kernel: NVRM: fallen off the bus and is not responding to commands.Please make sure that you update your BIOS, enable Resizable BAR support and Above 4G decoding. Make also sure that you've booting into UEFI Mode. You could also try another PCIe slot if you have on available but I'm not super sure if that's a Dell artificial limitation, you'll never know with Dell hardware.

Can you please go a bit more in detail what causes boot issues? I just put the Deprecation flag there because I don't develop it any further, the driver itself should still work as it should.

Sorry can't help with that, nothing changed from my side.

No holiday at all... However I'm not much around these days.

The PR was merged last week, you have to wait until a new Unraid version drops. The plugin is still working.

In the folder for Palworld in your appdata directory in: Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

In my opinion a few things need to be managed by the user and this is a thing the user needs to make sure that this path actually exists on his server, since cache is usually the default location for appdata sure, you don't need to have it but if you don't have it at least check the paths from the containers that you are deploying.

Are you on @Spectral Force Discord server, he has a tutorial there I think. https://discord.gg/VwwYA5h

Please look in the template, you can specify the version there.

Sorry about that, forgot that some users need console access, however the newly introduced WebUI now features also a Console tab, please update the container itself: Hope that helps (it looks even half decent on mobile :D ).

Just a heads up for Unraid 7.2.8 and SR-IOV users. SRIOV currently doesn't compile against Kernel 6.12.98 which Unraid 7.2.8 is based on, so to speak, don't upgrade if you need SRIOV support. An issue was already opened in their GitHub but I think they are a bit exhausted supporting that many Kernel versions and it will take time to be updated so that it works again.