ich777

I can only give support for license owners. @SpencerJ

Then roll back to an even older version, the drivers won't change and the package is always the same since they are precompiled. If it was working before something in terms of hardware or BIOS must have been changed since otherwise the older driver will work as expected, I think you get the point what I'm trying to say. Maybe the power supply is dying or something similar, if you haven't changed anything and you've rolled back the driver and you have the exact same issue with the previous driver there must be something different now... Can you please describe what you are doing? Do you update the BIOS on Unraid itself? No, the plugin won't reinitialize the driver, I would recommend that you close all browser windows when doing that because it is possible if something calls nvidia-smi, like for example the GPU Statistics plugin is calling nvidia-smi frequently, that the card gets reinitialize, or if you visit the plugin page, because if you are visiting the plugin page nvidia-smi get also called one time.

No issue over here: Here is the log from a fresh installed container: edge.log Do you have any AdBlocking software on your network or a UniFi Firewall that maybe blocks the download? Please do the following: Delete the container Delete the edge folder which lives in your appdata directory Pull a fresh copy from the CA App and leave everything as it is and try if it works <- this is what I've did

Thank you for the report. They changed the name from the binary that's why it was looping, please fore update the container and then start it again.

As said above I think you have to add some parameters in ESXi so that newer cards are working, this is not the first time I see that. Also please remove these two files from your modprobe.d folder: blacklist-nouveau.conf and nvidia.conf (why did you even do that?) This is the part why it doesn't work: 0b:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) DeviceName: pciPassthru0 Subsystem: Shenzhen Colorful Yugong Technology and Development Co. TU116 [GeForce GTX 1660 SUPER] [7377:0000] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia ESXi does something to the device names and I think that was the issue the last time too. The last user who reported that switched from ESXi to a native installation and it worked after that. Please also keep in mind that some hardware combinations and the 1660s series are complicated... at least on Linux. Please look into the Visualizing Unraid subforums, there you should find the answer what you have to add to the ESXi host that the card will work without a Kernel Panic. EDIT: I found that: But there is nothing I can do about that since you are visualizing Unraid and this could cause issues, I also really can't help since I'm not familiar with ESXi (just search for ESXi in this thread and you will find a few posts, some even stating that drivers >=460 not working with ESXi).

Have you yet tried to install the lagacy driver as mentioned above?

Have you yet tried to install the legacy driver version 470.xx, reboot and see if that version is working for you? Can you please post the full Diagnostics? When virtualizing via ESXi I think you have to add a parameter if I'm not mistaken so that newer cards will work.

What do you mean exactly, do you mean the driver itself or the plugin? Have you yet tried to roll back to the previous driver that was working? Have you changed something in terms of hardware or did you maybe update your BIOS or change some settings in the BIOS? Have you yet tried to disable C-States in the BIOS? Please don't do this manually until advised since the plugin does this on it's own.

This can be caused by various things, you can try to disable the built in AST adapter (this is done usually by a physical jumper on the motherboard). You can also try to use a different dummy adapter, reason behind this is that some dummy adapters don't provide a valid EDID. The last thing that we can try is to hide this message altogether from the log when the functionality from your iGPU isn't affected.

Also noticed that and I thought that I'm going crazy... Glad that someone else noticed that too...

I don't know, if I change it over here, it asks for the new password.

So the default password "Docker" is working correct? EDIT: I just tested it and if I change the password in the config to something else from "Docker" it is asking for the new password.

Have you yet tried to add the -password <YOURPASSWORD> parameter to the GAME_PARAMS like: The container always asks me for the password, which is initially "Docker" You have to rename it in multiple locations:

What have you done exactly? Did you stop the server in the first place and then set the password in the config? I have no issue setting the password over here.

@Spectral Force do you maybe have a idea? If you are doing it that way you also set Validate to "true" (without double quotes), but please set it to nothing or false after the check went through because this will force a validation from the game files on each container start and leads to way longer loading times.

I‘m not entirely sure but if TDARR changes a environment variable on container start to use all GPUs that could be the reason why, but this is only a guess and I don‘t know if that‘s the case here but it would be possible that something like this is causing the issue here.

Since when does this happen? Have you yet tried to assign the other UUID, but this shouldn't make a difference since the UUIDs are correct from what I see from the Diagnostics). I would also recommend that you check your VFIO bindings since it tries to bind 04:00 (which is your GTX1050 but it fails since the HW/VENDOR ID doesn't match - /boot/config/vfio-pci.cfg): Processing 0000:04:00.0 1002:67df Error: Vendor:Device 1002:67df not found at 0000:04:00.0, unable to bind device --- Processing 0000:04:00.1 1002:aaf0 Error: Vendor:Device 1002:aaf0 not found at 0000:04:00.1, unable to bind device --- Can you please also post the docker run command? I would strongly recommend that you disable Privileged mode? Why did you even enable this? This is a huge security risk and can maybe cause this issue.

And please post your Diagnostics there.

I would rather recommend SWAG because it has built in Fail2Ban support and also many template proxy configurations but no WebUI, but configuration is pretty straight forward.

Where did you read that? Running it as root isn't the same as running it as privileged. If you are just running it in your home network and no one else can access it, not really. You can mount the source directory as read only then it can't change anything if you are concerned about luckyBackup deleting anything in the source.

Do you run luckyBackup as root? Try to delete the file on the backup share and do the sync again.

Is the disk Backup mounted? From the screenshot from above I see that you point the data directory (this would be usually the path to your appdata directory which defaults to: /mnt/cache/appdata/luckybackup) to a Unassigned Devices disk. Are you sure that this is correct?

What kind of firewall/router are you using, do you run anything like PiHole or AdGuard for AdBlocking on your network? But you can't do that at the same time. Please note, a newer driver won't do anything in terms of transcoding speed... Please post your Diagnostics and don't delete anything from the plugin directory so that I can see what's going on.

Are you really sure that you didn't do anything manually to the permissions, that's the only reason I can think of why it is now not working. Please delete the container, then delete the folder for luckybackup which is located in the appdata directory and then reinstall the container from the CA App.

Did you do a reset permissions from the tools menu on the Docker directory? Are you using a Docker directory or a image? If you did a reset permissions, you have to set up Docker again. Reset permissions is only meant for user shares…