ich777

Than it's probably a I2C issue where I usually can't do anything about it, please ask on the OpenRGB Forums/Issue Tracker. I don't see why this shouldn't work just because you are on Unraid. ;)

No patch needed anymore with recent Kernels.

It shouldn't give you issue, I just tried it over here and it works like it should. Please double check your port forwarding.

For now on the latest, we will see what the future or better speaking Nvidia is bringing to the table.

Okay, then I'll deprecate the container since I can't test it. Thanks for the report.

I meant the message in the game when you are trying to connect. However if you report the container as broken and not working, I'll pull it from CA.

Can you please try to not change anything and see if you can connect by your local IP? Do you try to connect to the dedicated server with your public IP or with your Server IP? What is the exact error message?

In addition to @alturismo‘s post:

The container by default does not limit the amount of RAM the application inside the container can use, so to speak the application inside the container can by default use all your available memory and even crash your server. This is something you have to ask the developers from the game since this is a application limitation that it doesn't use more RAM, not a container limitation as explained above.

I really can't tell because you posted so little information. Did you change any settings in the template, did you change any config files, do you have other services running which are reachable from the outside world, did you do a port forwarding in your router, do you have a static or dynamic public IP address?

Usually not, but without Diagnostics really hard to say. Since this is not related to a plugin, because Intel Driver support is built into Unraid itself, I would recommend that you create a post in the Gerneal Support subforums here on the Forum.

That's a setting in your BIOS usually but only available when you have a Motherboard that supports newer PCIe Generations than 3.0

Did you yet try to to lower the PCIe Gen to something like Gen3. Since you have a second gen Ryzen CPU please also disable C-States for your CPU entirely and see if that helps. However from looking through your syslog I see probably a few errors: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy This is an error that I never saw before to be completely honest. And then you get this error which I've seen a lot recently but in your case it's a bit different and it seems it's related to the CPU but I really can't tell, however what you can do is that you report that on the Nvidia Developer Linux Forums subforums: Aug 31 05:19:39 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363 Aug 31 05:19:40 Tower kernel: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy Aug 31 05:19:40 Tower kernel: eth0: renamed from veth6aa9d85 Aug 31 05:19:40 Tower kernel: br-6deb7f169b14: port 20(veth7d89dc4) entered blocking state Aug 31 05:19:40 Tower kernel: br-6deb7f169b14: port 20(veth7d89dc4) entered forwarding state Aug 31 05:19:41 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363 Aug 31 05:19:42 Tower kernel: NVRM: kbifInitLtr_GB202: LTR is disabled in the hierarchy Aug 31 05:19:42 Tower kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1363 Aug 31 05:19:42 Tower kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242 Aug 31 05:19:42 Tower kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed Aug 31 05:19:42 Tower kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed Aug 31 05:19:42 Tower kernel: NVRM: osInitNvMapping: *** Cannot attach gpu Aug 31 05:19:42 Tower kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter Aug 31 05:19:42 Tower kernel: NVRM: GPU 0000:09:00.0: RmInitAdapter failed! (0x22:0x51:763) Aug 31 05:19:42 Tower kernel: NVRM: GPU 0000:09:00.0: rm_init_adapter failed, device minor number 0 Aug 31 05:19:48 Tower kernel: NVRM: nvAssertFailedNoLog: Assertion failed: rmapiLockIsOwner() && rmGpuLockIsOwner() @ conf_compute_api.c:78 This is unrelated to the Nvidia Driver but you have lots of XFC Checksum errors: Aug 29 06:12:57 Tower kernel: XFS (md1p1): Metadata CRC error detected at xfs_dir3_data_read_verify+0x7e/0x100, xfs_dir3_data block 0xbdd8fbe8 Aug 29 06:12:57 Tower kernel: XFS (md1p1): Unmount and run xfs_repair Aug 29 06:12:57 Tower kernel: XFS (md1p1): First 128 bytes of corrupted metadata buffer: Aug 29 06:12:57 Tower kernel: 00000000: 58 44 44 33 fa 13 dc ae 00 00 00 00 bd d8 fb e8 XDD3............ Aug 29 06:12:57 Tower kernel: 00000010: 00 00 00 01 00 04 b3 99 d7 b2 3a 12 2b 94 46 cb ..........:.+.F. Aug 29 06:12:57 Tower kernel: 00000020: a0 27 c6 a5 40 66 31 b1 00 00 00 00 cf 30 95 6e .'[email protected] Aug 29 06:12:57 Tower kernel: 00000030: 07 80 08 80 00 00 00 00 00 00 00 00 ff 7f 00 00 ................ Aug 29 06:12:57 Tower kernel: 00000040: 00 00 00 00 cf 30 96 15 16 53 6c 75 6d 20 4c 6f .....0...Slum Lo Aug 29 06:12:57 Tower kernel: 00000050: 72 64 20 28 48 75 6d 61 6e 29 2e 63 68 75 6d 01 rd (Human).chum. Aug 29 06:12:57 Tower kernel: 00000060: 00 00 00 00 00 00 00 40 00 00 00 00 cf 30 96 16 [email protected].. Aug 29 06:12:57 Tower kernel: 00000070: 14 53 6c 75 6d 20 4c 6f 72 64 20 28 4f 72 6b 29 .Slum Lord (Ork) I would recommend that you report that alongside with your Diagnostics in the General Support subforums here on the Forum.

Your issue is right there: Aug 30 14:54:21 JunkyardGarage kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 238 Aug 30 14:54:21 JunkyardGarage kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid: Aug 30 14:54:21 JunkyardGarage kernel: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:01:00.0) Aug 30 14:54:21 JunkyardGarage kernel: nvidia 0000:01:00.0: probe with driver nvidia failed with error -1 Aug 30 14:54:21 JunkyardGarage kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Aug 30 14:54:21 JunkyardGarage kernel: NVRM: None of the NVIDIA devices were initialized. Aug 30 14:54:21 JunkyardGarage kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 238 This usually means that you don't have Resizable BAR Support and/or Above 4G Decoding enabled in your BIOS. I would however firstly recommend to update your BIOS. You should definitely be using the OpenSource Driver for your card. You see that Unraid loads the nouveau driver correct? Please disable the nouveau driver by doing that from a terminal and reboot: mkdir -p /boot/config/modprobe.d echo "blacklist nouveau" > /boot/config/modprobe.d/nouveau.conf That wouldn't do much because you would need to run the installer every time you boot Unraid or create a package that you install somehow on boot, I wouldn't recommend going down that route since this is really complicated and the plugin is there for. What is that script in your go file: # Custom: NVIDIA Datacenter Driver Install sh /boot/config/custom/scripts/install_nvidia.sh

Sorry, I never seen that error, it would be best to create an Issue here since the plugin is based off from that repository: GitHubmiskcoo/ugreen_leds_controllerAn LED Controller for UGREEN's DX/DXP NAS Series. Contribute to miskcoo/ugreen_leds_controller development by creating an account on GitHub.

Most likely yes. I know Fritzboxes but I don‘t have one here in Austria, howerver you can try to use something like DuckDNS and see if that is working better, I assume that the server list caches the IP and when your IP changes the IP isn‘t correct anymore but this is just a guess.

Not really, never heard of such a behavior. My server also looks sometimes like that but that doesn‘t mean that the server isn‘t reachable, that‘s still an issue since the very beginning from the game. Do you have a static or a dynamic public IP address? Do you and your friends connect with the IP or with the hostname in game? BTW BepInEx should work again.

Did you reboot after installing the plugin? Please post your Diagnostics if the issue persists.

I create a second tag for the container shortly with dotNet 7.0 is that okay for you, so to speak you would have only to change the repository in the template. Please edit your container and at Repository make sure to add :dotnet7 at the end, so to speak that your repository look like either: ghcr.io/ich777/vintagestory:dotnet7 or ghcr.io/ich777/vintagestory:dotnet7 depending which container registry you are using. If you should ever upgrade to the latest version you just have to remove :dotnet7 Hope that helps.

I‘m not too sure if the admin panel was a thing back then. However it is like it is in my container.

The container is now updated, please update the container itself and everything will work again.

No worries, then you'll have to wait for the next release from Unriad but I already have two confirmations that on the new beta everything is working as expected.

Can you please try to upgrade to the latest Unraid beta version and see if the issue persits?

I didn‘t know that you could do that directly from the game. Usually you have to edit the config files but this was actually done on purpose to make it easier for users to set it up through the template. :)

I have to do that, please give me a few days.