ich777

What ports are mapped in your BeamMP template? You usually should have a port mapping with container: 8080 and host: 9045 if not simply add that to your template and then connect to the webconsole in your browser with: http://UNRAIDIP:9045 Newer templates should have that mapping already in place, older ones not.

Just because the GitHub Repository wasn't updated it doesn't mean that the container is out of date. The container contains the latest version from RustDesk Server. However I'll push a updated version from the container later this year since Debian Trixie came out and I'll usually push containers once or twice a year for my containers since most of them are self maintaining (where RustDesk is a exception).

Is your path set correctly in the template, by default all my templates are using /mnt/cache/appdata/... which is bad when you've set the Mover to move the files from your appdata to a different Pool which sounds like you've did when the container doesn't save the data. You have two options here: Set appdata to stay on the cache and that the Mover takes no action (which I would strongly recommend) Set the path in the template to /mnt/user/appdata/...

Sorry, I'm not much on Discord... :D Yes, because that's the console from the Docker Container and not the Console from the Dedicated Server, that is however a common misconception. To open the console from the Dedicated Server you have to click on WebUI.

Do you need this: vfio_iommu_type1.allow_unsafe_interrupts=1 I really can't help anymore since this seems like some kind of Hardware incompatibility issue. You can try to create a post on the Nvidia Developer forums and see if someone can help there, or if you are willing to upgrade, you can try the newest public Beta from Unraid, this should be also stable and you usually don't have to worry about your date and even if you are not satisfied, it should be easy for you to downgrade to the latest Stable version from Unraid.

Please look at this post, my containers are self maintaining and that means they update them self on restart if that is not working you can do that (of course it's another game but the same applies for your container) :

Stop the container Delete the steamapps folder from the avorion directory Start the container Open the container logs and see if it pulls the update

Nvidia will move on with the Open Source driver and deprecate the Closed Source over time, like they do it always, however this will take a few years.

Yes, the plugin is downloading a driver: GitHubGitHub - frankcrawford/it87Contribute to frankcrawford/it87 development by creating an account on GitHub. lm-sensors is part from Unraid, if this is a lm-sensors issue I would recommend that you report that on the General subforums.

Can you please go more in detail what you mean exactly? Is your chip probably supported in the Kernel but it is just missing?

That's the issue. Yes, but please stop the container first and make sure to make backups of all data you currently have. Please also check the container paths too since you have to ensure that the path to the game files matches to a Cache that is persistent and not moved from there, at least that is what I would recommend to do, you can also use /mnt/user/appdata/... but that it a thing that I wouldn't recommend.

Nope it is not, usually it should be disabled by default. Please read: Version 7.1.0 2025-05-05 | Unraid DocsDieses Release fügt drahtloses Networking, die Möglichkeit, TrueNAS und andere Fremdpools zu importieren, mehrere Verbesserungen an VMs, erste Schritte hin zu einem responsiven WebGUI und mehr hinzu. Just do: mkdir -p /boot/config/modprobe.d echo "blacklist nouveau" > /boot/config/modprobe.d/nouveau.conf One from the terminal and that's enough.

Please check the paths in your template, do the game files point to /mnt/cache/appdata/... if yes make sure that your appdata share stays on the cache in the Share settings and the Mover takes no action. Reason behind this is if the Mover moves your data to another Pool then this would basically mean that container searches in /mnt/cache/appdata/... for the save files but mover has already moved it to /mnt/OTHERPOOL/appdata/... and your save file, is at least for the container, not there any more where it should be. You have two options: Set the appdata share to stay on the cache and Mover takes no action Set the GameData Path to /mnt/user/appdata/... However I would always recommend that you choose option 1 since your Containers should have always access to the data quick and you ensure it with that with the benefit that your Array can go to sleep. There is also another option, that you even don't have /mnt/cache/appdata/... and that would mean your save file is gone because it was stored in RAM.

Oh, Icarus is working for you on LAN? I wasn't able to find it on my machine, I had a similar issue here which was very strange since I couldn't find it on LAN but I could connect through it via my Favorites (however that means that you would have need to connected once successfully) : https://forums.unraid.net/topic/79530-support-ich777-gameserver-dockers/page/488/#findComment-1580541 I'm not 100% sure if there is an in game console where you could type in a command to connect to the server manually via your TailscaleIP:PORT, that would maybe work.

I'm not 100% sure, you can try to remove the plugin, reboot, install it again and reboot again to see if anything changes.

If your chip isn't supported by the ITE plugin then it won't work, exactly.

I have to look into that but last time I checked IntelGPUTop wasn't compatible with the xe driver but from what I know they plan to support it in the future.

Depends about which plugin are we talking about. If you are talking about RadeonTOP or IntelGPUTop then maybe not but only if you don't need GPU Statistics.

I think it should be pretty obvious why it's not working, another driver is used. You have to blacklist the nouveau driver. @SimonF shouldn't the nouveau driver be blacklisted by default, I have seen now many reports with that issue.

Can you please go a bit more in detail? However all the drivers are closed source ones except for the option where it says Open Source. For 5000 Series cards, yes. 5000 Series only supports Open Srouce 2000 Series up to 4000 Series support both Closed and Open Source (including the 1600 series cards) Everything below 2000 supports Closed Source only

My containers are self maintaining, so to speak they update themself on restart, but the devs probably changed something and the update logic is broken, I will look into that and report back. I should learn to read, if create a veriable with the Key: PRERELEASE and Value: true then the container will download the prerelease, if you ever want to go back to stable or better speaking latest, simply set the Value to false.

Again, this depends completely on the distribution. This was just an example for Debian Bookworm/Trixie

You have to search how to change the IP for the distributions. For example for Debian you have to do something like that in the container itself: Edit/Create /etc/systemd/network/eth0.network And fill it with something like that: [Match] Name=eth0 [Network] Address=10.0.0.99/24 Gateway=10.0.0.5 DNS=10.0.0.5 #IPv6AcceptRA = false After that you have to restart the container and the new IP will be applied. Again, you have to see it more like a VM instead of a Dicker container.

Since you've did this, you'll have to start over. Please don't use Steam credentials to log in my containers where it isn't strictly marked as required with the red asterisk. Can you please describe what this means in detail or post a link to where I can find out more about that? I don't play Abiotic Factor anymore.

Sure, inside the container, please keep in mind that this is basically a VM, or better speaking a full distribution in a container.