ich777

Yes, everything correct, I did not push an update because there was no need to do so. The key won't change as long as it can find the physical path to the files since the key is stored on disk. If you have no cache then please check if the path in the template is set to /mnt/user/appdata/... instead of /mnt/cache/appdata/...

The variable --key _ forces the server and the relay to use the key otherwise everyone would be able to connect through an to your machines without a key, so to speak the server and relay do strict key checks if they are matching, otherwise the connection is rejected.

Can you please go a bit more in detail what you mean with "last update"? The last update was pushed 5 months ago since this was the time where RustDesk Server 1.1.14 was released. Are you sure that your Docker template is configured correctly, so to speak please check the paths in the template. If you are using for exmple /mnt/cache/appdata/... then you have to ensure that the Mover takes no action for the appdata share and that the data stays on the cache and is not moved to another disk.

I think this is your issue: Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU at PCI:0000:02:00: GPU-257c8daf-576b-fa9e-c3c1-94f40e3e4347 Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU Board Serial Number: 1422019097083 Jul 1 13:18:36 OrbitalHub kernel: NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus. Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU 0000:02:00.0: GPU has fallen off the bus. Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU 0000:02:00.0: GPU serial number is 1422019097083. Jul 1 13:18:36 OrbitalHub kernel: NVRM: A GPU crash dump has been created. If possible, please run Jul 1 13:18:36 OrbitalHub kernel: NVRM: nvidia-bug-report.sh as root to collect this data before Jul 1 13:18:36 OrbitalHub kernel: NVRM: the NVIDIA kernel module is unloaded. Jul 1 13:18:36 OrbitalHub kernel: NVRM: Xid (PCI:0000:02:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required) However as you can see you even got a Xid error which you can learn more about here: https://docs.nvidia.com/deploy/xid-errors/index.html#xid-error-listing (in your Case you got Error 79) Does this happen often for you or did this just happen for the first time? If this happened for the first time was this possibly during the Parity check or on the beginning from the Parity check? If this happened during the Parity check for the first time make sure that your Power Supply is up to the task since such errors can happen at peaks where the Power Supply delivers power a bit too late or even to less which is required by the GPU. Don't forget that power supplies also degrade over time. Just because I saw it, please remove the file /boot/config/modprobe.d/nvidia.conf <- this isn't needed anymore, you also don't have the correct driver installed anyways. You can also remove it by issuing this command from a Unraid Terminal: rm -f /boot/config/modprobe.d/nvidia.conf

Sorry but not many people having issues, if you read through the posts these are mostly compatibility issues and possibly dying cards or other issues which of most are probably solved by now, I admit not all but most of them. Usually people come here to report issues and not to say that everything is working fine. 🙂 Please keep in mind that about 16k people have installed the driver plugin and I would not say that many poeple have issues otherwise this thread would be full of support requests lately. Can you possibly post your Diagnostics after the error occurs so that we can diagnose the issue further otherwise troubleshoting the issue is really hard and I even can‘t see which system you are having or what possibly could be the cause of the issue.

Can you possibly try to not stop the containers that use the Nvidia GPU when running appdata backup, I would also report that in the CA Backup/Restore thread since this not seems like a driver issue to me, a running VM usually don't takes over a GPU. BTW, did you know that I and @Joly0 have a LXC container for AMP ready? You can also try to uninstall GPU Statistics since it seems to cause issues for a few users lately and see if that fixes the issue.

In no offence but nothing has changed in terms of the container. The only things that could have changed are the game itself, since it will get updates sooner or later, or the mod got update or it got not updated and therefore it might be incompatible. So to speak nothing changed in terms of the container and even if I push container updates these are usually only contain security updates.

Are you sure that this isn't possibly a problem that a container causes? I had many issues back in the days with Tdarr crashing servers for example.

Diagnostics would help a lot to troubleshoot your issue.

To me this seems like a firmware issue, however have you yet tried to limit the PCIe Generation to something like Gen4 or even lower to Gen3 to see if that fixes the issue. About the performance I'm on the same page as @alturismo because for transcoding it doesn't matter much however for AI related stuff you would need as much bandwidth as possible but I'm not sure if dropping down the PCIe Generation would have such a significant impact (at least not to Gen4) in a real world scenario.

Usually it is enough to just connect with: mydomain.com (as long as it points to your public IP address). Exactly. Please make sure that Hair Pin NAT is working properly, this could be also be a reason why it‘s not working.

Sorry, I don‘t create new containers any more.

Windows only, maybe possible through WINE, don't know since I don't create new containers anymore. I don't think so. That won't help at all since this is for the Steam Client and not SteamCMD and in addition to that for Windows. ...these are my thoughts.

Sorry but I can't support modding since this would be too much for me and, it was at least in the past, sometimes the case that broken/incompatible mods prevented the server start. Maybe @Mainfrezzer can help.

Sorry, I've deprecated the container, please use a image from another author.

No difference, just two different container registries.

Please take a look here: https://github.com/ich777/unraid_kernel However I don't think you can build modules for custom Kernels but this would definitely give you some clues and possibly the maintainer from your Kernel could implement your driver that you need.

Sorry, that's not possible with my containers.

Do you have Diagnostics?

Please look at this thread, it looks like more of a miss-configuration from the paths to the game files: https://forums.unraid.net/topic/79530-support-ich777-gameserver-dockers/page/451/#findComment-1478062 Can you please describe a bit more in detail what commands that you want to pass over?

Sorry, but this is the wrong thread to request a game server Docker. I don't create game server containers any more.

Just deploy the container and it should work OOB without needing you to do anything special.

Go to your appdata directory and there you will find the files that you need to edit, please always stop the container in the first place, then edit the files, then save the changes you've made and start the container again.

Please update the container ("force update" on the Docker page), everything is fixed now.

Please post your Diagnostics.