ich777

Please post your Diagnostics, without them I can't say much.

Do you have a log from the container or anything? It is most likely that your configuration is not compatible with the new OpenVPN version (this was the reason I updated). If you have a crl-verify block in your config please remove that (you usually have two crl-verify lines in the config from PIA, remove the two lines and everything in between) and restart the container.

Clear your browser cache.

So wait, the default braunch works fine but the experimental not? Could it be that the experimental branch has additional, new, dependencies or tht it is just broken or does it work if you install it on Linux box/vm?

Okidoki, then I will look into that, could anyone give me the exact error message? When you stop the container you can actually look at the log and copy the message when the container is looping.

I don't know if that will definitely help but a few users reported that this helped, however that looks okay. Sorry, you have to ask that on the container side of things however it looks like you don't do transcoding if you are currently playing a file. Please also note, if audio transcoding is needed, this is done on the CPU not on the GPU.

Yeah, that should work. Sorry, but most of the times it has to do with hardware incompatibility, the GTX16 series was always a bit of hit and miss, maybe look out for something like a Nvidia T400 4GB (even the 2GB version should work fine) and try if this card works.

Pairing old hardware (you System) with relatively new Hardware GTX16 series or RTX series is most of the times a bad idea and will lead to potential issues like you are experiencing.

Unraid should have a file explorer where you can edit files directly in the WebUI.

Okay, seems pretty old but you might be out of luck with the BIOS updates, seems this machine is deprecated from the manufacturer. Seems your machine doesn't support either of these options. Not exactly but it is enough if you issue it once after a reboot. May I ask if this is a new issue or a new installation or even a new GPU or a new installation from Unraid? Most of the times it's a hardware incompatibility issue or a wrong set setting in the BIOS, but I don't think it's the latter in your case.

You have to go into the BIOS for that and check the settings. For the BIOS update you have to check your Motherboards/Systems manufacturers website. Just put the line: nvidia-persistenced at the end of the file /boot/config/go and reboot afterwards. The video is a good source of information. Seems to be a PCI related issue, I would strongly recommend that you do the above steps.

If possible, please also pull diagnostics when the error occurs. From the Diagnostics I don't see anything wrong. You can try to add nvidia-persistenced to your go file, make sure that you are on the latest BIOS version, make sure that Above 4G Decoding and Resizable BAR Support is enabled.

Please update the container and try again, I might downgrade to Debian Bookworm again if you report more issues.

Please update the container. For the text editor type in gedit in the popup box and it should open just fine.

I assume this is the issue: Using NAT to change the ports for game servers is not recommended and will fail in most cases because the client usually the game server on which port he listens and the server with responds "I'm listening on port 27015 UDP" and you've NATed that to 27016 that won't work, a game server is not a Webservice where this usually would work. However also only use the ports and protocols which are specified in the template because some game servers went a step further and check if the game server port with a protocol is forwarded that is not needed and simply refuse to work.

And does it reboot or what is the exact issue?

Have to look into that, did just an upgrade to Debian Trixie.

I don't use Arch for my containers so pacman won't work. I'll look into this, please give me at least one or two days.

If you have selected "latest" on the plugins settings page, then yes, you will be on the beta driver because latest means always the latest available driver version, which not always must mean that you are on a Beta driver, but currently Beta is the latest available driver. You know that the plugin has a settings page right? Nope, I don't accept any PMs, there is usually nothing you have to hide in that file. Please drag the Diagnostics file into the textbox here on the forums.

As said that has nothing to do with System Memory, that refers to Kernel Memory, so to speak reserved memory for the Kernel in System Memory and the message is actually produced by the Nvidia Driver, so nothing that I could do about. Try it. As another test, please post nvidia-persistenced in your go file and execute it once (so that you don't have to reboot).

This refers to Kernel Memory not strictly speaking RAM. Please make sure that you've enabled Above 4G Decoding and Resizable BAR Support in your BIOS. Please also make sure that you are on the latest BIOS version available, most of the times this points to firmware related issue. Not much that I can do about, you'll find plenty of these errors on the Nvidia Developer forums and most of the times this happens to users on AMD platforms, please maybe report that on the Nvidia Developer forums since this is directly related to the driver. I could, but usually I compile the drivers once when a Unraid version is released, are there any new features that you need or why do you need the newer driver?

This. All GTX 10 und 9 series are now legacy. All Turing based cards, including GTX16 series should work just fine bisides the point that the driver seems pretty unstable with the newer driver releases.

Please post your diagnostics.

This is a thing you have to figure out since this is a game server issue not a container issue. The container is just the same as if you install it directly on to a dedicated Linux machine but with the installation/updates automated. Nothing the container can fix if the value isn't read properly.

Sadly no, at least not how it's currently implemented. I could add --delete to the rsync command but that would affect all users.