ich777

A bit more insight would be better. Can you post your Diagnostics after this happened? What have you done exactly, are you on the legacy 470.xx series driver? Did you wait for the Plugin Update Helper to finish before rebooting to the new version? I really can't tell anything without more information.

Why do you want to even do that? The 390.xx series drivers are not capable to be used in Docker containers.

Something is wrong with you .pak file, there are you get these messages over and over: which basically means that something is wrong. To what is your appdata share set in terms of Use Cache or what primary storage is set? I can not reproduce this, I've attached my log since I've now tried it, you can also see that bots are already playing on the server... q3.log

I don't have a PIA account and I can't help here but maybe someone else with PIA can help. But it seems that the communication with your VPN is established, how did you check if it is not working?

I don't share this opinion but of course that's my opinion. I think it's more overkill what you did above but don't get me wrong that's my opinion. It always depends on what you are trying to do and to accomplish. For me it's way enough to log in as root and do stuff as root and I never want to access this from outside and even if I want to do that I can create a tunnel and do that.

But the path in your screenshot from above and says something like "virtual_machines" are you sure that the path is correct? Also this was a really bad idea what you've did there, you should only changthe path to something like /mnt/virtual_machines/appdata/quake3 What you've done here is basically you've said the container that it should all files that belong in the folder quake3 now in a subfolder and you now even have a deeper path.

Did you restart the container after placing the file in the correct directory? Does the path in the template also point to the physical location on your machine?

What provider are you using? NordVPN is notorious for not working with my container. However someone got a answer from the support from NordVPN back and here is how you do it: Click

Simply restart the container and make sure that manual updates are disabled in the template.

I think this is maybe because the Target assumes that the Initiator with the IQN is still connected and doesn't allow a connection with the same IQN. May I ask if it wouldn't be better to sort out the root cause of the issue, the unstable network? I'm not too sure about that but I don't think that there is an easy solution to your specific issue because iSCSI usually requires a stable network connection.

This is nothing that I can integrate into my container since this needs to be applied on the host. My container uses the Windows client because there is no Linux server available. Only when the Host is restarted, so to speak Unraid. But that doesn't mean that will and I don't think that they will do that since they struggle even with the Windows version that much, look for example at The Forest or Sons of the Forest they have and probably will never have a native Linux server. I don't think I have time for that, in the little spare time that I have left over currently.

But the issue talks about the server crashing or am I wrong, this seems a bit different or am I wrong? I assume that my container is most certainly working differently then the "semi-official" container since I do many things differently than most other container maintainers. For now this is a workaround not a fix in my opinion, this needs to be fixed from the developers in the engine itself. I got so many requests about this game to create a container but in the early stages is was plagued by bugs and was really unstable, even for a proper connection you had to do a workaround. I'm not really willing to accept another workaround for a thing that needs to be fixed. It should not be necessary to increase that limit for a game server. Again, you have to do that on the host if you are really want to change that limit, execute this form a Unraid terminal (but please keep in mind that it will be reset on a restart from Unraid, because Unraid works differently): echo "262144" > /proc/sys/vm/max_map_count to check if it was applied successfully issue this command and it should give you 262144 back: cat /proc/sys/vm/max_map_count

This is something that needs to be done on the host and nothing that needs to be done in the container but that or at least how it's described there is not suitable for Unraid. I've never heard of that issue to date or better speaking no one reported that to me about my container, did you experienced this crash already? Is this discussion on Discord about my container or is it the "semi" official? I'm not a big fan of setting this value to something higher because this can also cause issues on the system itself. TBH I have played only a few hours on the server and it was rock solid.

I think this has to be done on the Windows side since you could technically connect two machines to one Target (but it is for obvious reasons not recommended). Have you yet tried to restart your Windows machine?

This seems correct to me IIRC. I don't think that you will get a answer back from most game servers over telnet... Most gameservers simply drop the connection if they get a request from something to them unknown.

How much CPU and RAM does the container consume? IIRC this line shows after the container is fully started and waiting for connections. EDIT: If you read one post above yours someone posted another Satisfactory related question so I assume the container is working, but I haven't tried it yet.

Please always pull Diagnostics from your system if you encounter an error before you reboot and always include them in the Diagnostics.

May I ask why you want to do that? This is a really bad idea, if you do that the server will ultimately crash if it wants to assign more RAM than you allow it to.

The driver sees 3 GPUs: Attached GPUs : 3 ... GPU 00000000:08:00.0 Product Name : NVIDIA GeForce RTX 2070 SUPER ... GPU 00000000:09:00.0 Product Name : NVIDIA GeForce GT 1030 ... GPU 00000000:44:00.0 Product Name : NVIDIA GeForce GT 1030 Is one GPU passed through to the VM or are more GPUs passed through to VMs? Please don't forget that if you pass a GPU through to the VM and the VM is running that it doesn't show on the plugin page... However I see this in your lspci: 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) Subsystem: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia 08:00.1 Audio device [0403]: NVIDIA Corporation TU104 HD Audio Controller [10de:10f8] (rev a1) Subsystem: NVIDIA Corporation TU104 HD Audio Controller [10de:1e84] 08:00.2 USB controller [0c03]: NVIDIA Corporation TU104 USB 3.1 Host Controller [10de:1ad8] (rev a1) Subsystem: NVIDIA Corporation TU104 USB 3.1 Host Controller [10de:1e84] Kernel driver in use: xhci_hcd 08:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller [10de:1ad9] (rev a1) Subsystem: NVIDIA Corporation TU104 USB Type-C UCSI Controller [10de:1e84] 09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) Subsystem: ASUSTeK Computer Inc. GP108 [GeForce GT 1030] [1043:85f4] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia 09:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1) Subsystem: ASUSTeK Computer Inc. GP108 High Definition Audio Controller [1043:85f4] ... 43:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1) Subsystem: Gigabyte Technology Co., Ltd GA106 [GeForce RTX 3060 Lite Hash Rate] [1458:4096] Kernel driver in use: vfio-pci Kernel modules: nvidia_drm, nvidia 43:00.1 Audio device [0403]: NVIDIA Corporation GA106 High Definition Audio Controller [10de:228e] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device [1458:4096] Kernel driver in use: vfio-pci 44:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP108 [GeForce GT 1030] [1462:8c98] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia 44:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP108 High Definition Audio Controller [1462:8c98] Nvidia RTX2070 Super: nvidia driver loaded Nvidia GT1030: nvidia driver loaded Nvidia RTX3060: bound to VFIO Nvidia GT1030: nvidia driver loaded So to speak, everything seems completely fine and the Nvidia Driver plugin lists the cards correctly. In this Diagnostics I see that you have bound the RTX3060 to VFIO so to speak the Nvidia Driver plugin can't see it. I don't know how you've bound it to VFIO because I don't see any indication why it should be bound to VFIO in your Diagnostics but the syslog shows that it was bound to VFIO on boot: Aug 10 12:19:48 Server kernel: vfio-pci 0000:43:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=io+mem:owns=none Again, please note that you're RTX 2070 Super won't show up if you've use it in a running VM, that is the default behaviour.

Maybe someday it will be included in the base OS.

Please update the plugin and visit the plugin page, you will then see a new tab where it is described what to do to make the changes persistent (the first example on this page is exactly what you need or better speaking what you've changed).

Please update the container you are now able to specify if you want to download "latest" or "beta". The container will now (as of time of writing) pull the latest version 115.1.0 I won't recommend switching between "beta" and "latest" since it is also not recommended by Mozilla itself, it should work however but there are some implications about compatibility in the profiles folder and from my testing you have to create a new profile if you switch from beta back to latest. EDIT: I've now took a quick look at KasmVNC and see no real benefit switching over at least not at a first glance. From my testing it behaves pretty much the same in terms of speed/quality and the downside at least from my perspective is that you can't connect with a VNC client to it.

I mean you could always advice users to create an Issue on GitHub or you can even create an Issue yourself if you want to keep track of that. The Forums in my opinion are only for support requests if something is unclear but users will of course report issues too. But that seems also tedious, especially because this a forum.

Could this be the issue: The name doesn't match.

What settings did you change? I think there are options for the syslinux.conf so that you can make these changes persistent. @CyrIng can you maybe help here? What do you think about the idea if I add a help page for the config parameters so that users can easily append them to the syslinux.conf or the modprobe.d file?