ich777

Have you created the Port from the container that you route through the OpenVPN-Client container in the OpenVPN-Client template too? If you are using @binhex containers you have to create custom rules in your container like mentioned here:

I can only point you to the Guide that @Cyd created: Modding the servers is always up to the user, I can only support this only to a certain degree because I only create the base container for the game itself and sadly enough haven't got the time to play most of the games anymore don't even speak of modding... Here is also a post from Reddit:

Depends on what do you want to compile and package up. Should this be a „AiO Package“ manager or what do you want to do exactly? The NerdTools only provides packages from the official available Slackware packages from what I know. Oh and do this apps need to be compiled for each new Unraid version because of dependent Kernel modules?

Thank you for the report, already updated the container. Please force an update from the container itself in Unraid and then try it again.

This is the most definite solution to your issue, create a variable with the Key: FORCE_X86 and the Value: true like: For this game from what I know you need to provide a valid Steam account with the game in the library. On what machine (CPU) do you try to run ARMA3? I think that ARMA3 released a update in the last year so that a specific type of instruction is needed, so if you are trying to run this on something like an AMD Phenom it won't work, but I'm actually not quite sure about that...

Plugin is basically done, have to check a few things with @capt.asic before I release it.

In general I don't think that's possible because a BMC is generally speaking it's own dedicated System and only interfaces with the rest of the System. This patch basically hooks into the PCI device reset function for the specific these AMD devices and watch if it is necessary to reset the them (for example when a VM is shutdown), this is a very oversimplified explanation. I can't imagine that this will cause any issues with you BMC since it watches only for these AMD devices which are supported by the vendor reset (Graphics devices - Polaris 10, Polaris 11, Polaris 12, Vega 10, Vega 20, Navi 10, Navi 12, Navi 14) and perform a simple device reset if needed (like if you reboot a computer so that the card initializes again). However I would recommend that you create an issue on GitHub if you think that the vendor reset is causing this issue but as said above I really can't think of how it would manage to do that and I know a few people out there with Supermicro Boards that has also BMC chips on them and have zero issues in combination with the vendor reset. Here is the Issue tracker from the vendor reset: Click All good... What kind of devices have you connected to the BMC? LAN, VGA, COM? Maybe also check the other HW/Cables connected to the BMC if the fault is maybe located there. Have you also contacted Supermicro for Firmware updates or if this is a commen issue like suggested on Reddit from another user?

Simply set it to "1690800 -beta experimental" like so: and set the variable "Validate Installation" to "true" (without double quotes).

When it arrives and you are testing it please let me know if it's the same as for @always67, we already have a workaround for this on 6.10.0-rc5

This is a known issue but nothing you or I can do about that because basically Nvidia breaks some readings for cards in each new version from the driver and so to speak nvidia-smi. Even if the card can report it it won't show up because it is broken in nvidia-smi and it will get worse over time with each new driver revision released because if they fix it for one card it breaks for another one. My Nvidia T400 also doesn't report the currently drawn power and this is a "new" card. As @trurl pointed out this is the correct thread for this question:

I will look into this but currently I'm really busy and this will take at least a week.

I don‘t own FS22. BTW are you sure that everything is working there? I had it running once but gave up after a bit since some elements from the game did not run properly. You can easily create your own template, here is a quick tutorial that I‘ve found:

That isn‘t possible from what I know, thats the case for some games, like for Space Enineers too, these games where designed without Linux in mind and will only work on Windows. No, you have to look also what architecture and OS these containers are for… For farming simulator there are only Windows containers out there and this is also a game that won‘t work on Windows.

From what I know it is not possible to run those servers on Linux without violating the EULA. You can only run it from within a Windows VM.

This is a common issue with this cards on newer Kernel versions. Yes, the Kernel, but you know as time goes on newer and newer Kernel versions are integrated and there is nothing I can do about that „old“ version cards… You can however contact the DigitalDevices support and send them the error message, the Kernel version and your exact cards.

Maybe create a post in the Nerd Pack support thread if it can be added.

But that doesn't always works perfectly fine as you already pointed out and this is not the only issue... This was also the way on how it worked on Unraid, but that also introduces other issues. I don't think that your idea is disagreeable, as @Squid pointed out this is more kind of a experiment and if it doesn't work out it will be changed back how it was and maybe with some additions like a global option to turn updates on/off <- at least this would be my suggestion...

I can add you to the conversation if you want to...

You have to install ValheimPlus or BepInEx to your local game too to work properly.

Some special characters are not supportet that's true but that's also true for some sites where you can't just simply use for example : $, \,... Sorry about that I've worte that when I was on the go... I really hope you don't exposed the WebGUI from AdGuard to the web? If so why? It's common to use strong passwords for services that you can reach from the Internet but for services on your local network it won't be that big of a deal except you have hackers in your local network but then I think a password would be your lowest priority problem...

Warum ist das zu unsicher, bei einem upgrade passiert genau das gleiche, nur automatisiert. Wichtig ist nur die bz* und die changes.txt zu ersetzen. Downloads der zip Dateien findest du hier (ganz unten bei Manuelle Installation): Klick

Maybe on monday, I usually don't give direct support because this would consume my whole free time...

Thaha I‘m the complete opposite of that and when the maintainers from Gitea introduce a new variable or something that‘s not well documented so that my instance (where everything is hosted I do) won‘t work anymore I start raging at their Discord. 😂

Think about it, most won‘t read it and click OK or Change or whatever button is in place anyways…. Do you change your templates that often or what is the exact issue in your containers? I barely change my templates and if I do so they won‘t break the container because I also integrate a new variable or whatever into the Dockerfile itself that it is by default there and won't break functionality… If you really want auto updates or whatever I think the easiest solution would be to create a option to enable or disable auto updates in general (also respect templates that have it turned off) somewhere in the GUI so that users can decide… but by default I would let that global option turned off.

Please post your Diagnostics, which adapters are you running? Why not? Better to fix it now than later… This is a common thing with DVB cards, if this happens again please make sure to shutdown the server, unplug the power cable from the wall, press teh power and reset button a few times (to empty the caps), wait about 1 minute, plug the power cable back into the wall and start your server again. Your cards should now be back in a working state. EDIT: Now that I thought about it are your cards pre V6.5? If so please stick to the LibreELEC drivers for your cards.