ich777

I don't think you have to do that or am I wrong? The Containers will fail to start if I'm not wrong? What happened after the upgrade after you first built it on the lower version?

Can't image that this is the case with my Plugins since I use it on my Development machine like this. Are you sure we are talking about the DVB-Driver and Nvidia-Driver Plugins that were introduced with Unraid 6.9.0beta35 There are two answers to this question: No, simply install both Plugins and you should be good to go. Yes, if you like it to have everything included into one build then you can use the Unraid-Kernel-Helper.

Have you already tried to clear the Cache of your browsers? Also no problem here.

Please try the same as in this post and the followed up post: Don't know why it isn't working for some users on the first star/install but this solves the problem in 100% of the cases.

But the second run includes that you are on the preferred Unraid version or am I wrong? I strongly recommend always upgrading first and then run the Kernel-Helper with all your features included. You can at least try to create a variable in the template if you are on a lower Unraid version with the Key: 'UNRAID_V' and as the Value the Unraid version you want to build for, not exactly sure if this will work because I always upgrade first and then build. Hope that helps.

Darf ich mal generell fragen warum du ZFS brauchst auf Unraid? Momentan wird es noch nicht offiziell unterstützt...

Which IP adress and which port are you using? Have you clicked refresh after adding the server? You have to use YOURIP:PORT+1 (eg: 192.168.1.1:2467) That is only a warning and nothing to worry about. Your startup log looks just fine. Please read the second recommended post on the top of this thread.

But Fox Server is 42 MB and FoxServer is 2MB...

Nein, das macht Unraid. Bei ZFS gibt es eigentlich keinen Spin down soweit ich weiß und hat auch @steini84 hier geschrieben:

Don't know if that looks right to you (on the right side is water and on the left it goes up I think a mountain... , doesn't reset in my case):

Can you try to stop the container delete the valheim directory that is located in your appdata, then also delete the container and after that try to redownload it from the CA App and see if it works with the default settings?

Have you set the password to at least 5 characters?

Sent you a PM. Anyways try to restart the server and see if it actually uninstalls.

You have to ask on the Valheim Discord/Forums/Steam Community Hub if this is a known problem... Have you checked the Docker template if everything matches your save game? I don't think it's a problem with the container since I run it also and have no problems so far.

That's why it isn't working, you have to set it to 'Only' or 'Prefered' since the container has to be on the Cache drive (otherwise it won't run properly) every time the Mover moves the files from the Cache drive to the Array the game won't work properly since it moves the game files and Backups to the Array and the game executable searches for the files on the Cache drive. Hope that makes sense to you...

Please close the window with the red X, see if it installed anything to your server and remove the Plugin if it installed it. After that reboot the server and try to install the Plugin again. Are you sure that your Server has exclusive access to the internet and can connect to Github?

Please check how your appdata share is configured in terms of using the cache? Is it set to use the cache "Only", "Prefered", "Yes" or "No"? Is this the first time happening or is this always the case? How long did you run the server now?

Try to disable to Stop the Container when the Backup is executed, go into the Plugin and at the bottom click on: then click on the little slider icon at Valheim so that it says don't stop: Try to restore it form your PC to your Container and see if that works. In the template the world name and everything is the same as before or appropriate to fit the save?

Can it be that you have CA Backup running and that's why it skipped? Something must have happened between 2021-03-08_06.25.11 and 2021-03-09_04.12.34 but I can't tell you what seems like the container wasn't running or something eslse happened. Can you try to restore the world on your local computer and see if it loads? Eventually try to also completely delete the old world files and not just replace it, have you stopped the container in the first place, please also look into the template if anything has changed and if the world name is correct.

There was no update of Valheim or the Container... Did the Container update? Have you enabled the Backup function of the container and have you tried to restore the backup from there?

Yes and no, if the plugin doesn't finds the version that you manually selected then it falls automatically back to latest, so there is no reason to worry about the version.

You can now safely upgrade to 6.9.1 and the plugin will download the new driver on boot (keep in mind that the boot time could take a little longer than normal since it's downloading the driver).

@vinid223 Please don't forget to close the bug report if it is working.

Already thought of that... But then I thought it would be enough if you see it on the left side of the Plugin but that shows only the current version... Would it be better to select the radio button what is actually installed or a little textbox with what version is currently selected? I'm open to suggestions on that... It would also be a idea to display a textbox or something similar if you choose another version than the current version that says something like: "Nvidia Driver vWHATEVER will be installed on the next boot" Error? This should be a "red" notification but not an Error, I made it red so that the user actually can't miss it what to do next...

I'm running a ConnectX2 in my DevServer and a ConnectX3 on my Main server and have no problem whatsoever. The Plugin shows also information about the card itself so the modules should be loaded and I think nothing is preventing it from running. Eventually try to reset the Network settings and start over again only with the 10Gbit/s card.