ich777

Then make sure that nothing on the host (Docker) is using the card and start the VM. Even if you are uninstalling the plugin you have to reboot too to fully remove the plugin/driver.

The driver is reporting this: May 24 12:40:27 Tower kernel: NVRM: GPU 0000:83:00.0: GPU does not have the necessary power cables connected. May 24 12:40:27 Tower kernel: NVRM: GPU 0000:83:00.0: RmInitAdapter failed! (0x24:0x1c:1428) May 24 12:40:27 Tower kernel: NVRM: GPU 0000:83:00.0: rm_init_adapter failed, device minor number 0 Are you sure that you've connect everything properly? Please use the Nvidia support thread if you experience further issues.

On what Unraid version are you? Did you change something in the template? Have you yet tried to stop the container and then open the Logs? Please post a screenshot from your Docker template. EDIT: I've now set up a new instance on my test server and it is working as intended, I've attached the log here: rustdeskserver-aio.log EDIT2: I've got now confirmation that it works on other machines than on mine on Unraid 6.11.5 and also on 6.12.0-rc6

No, in my templates are always the ports listed which are needed. Not more or less (usually). I will report back ASAP, got a cold yesterday and not feeling very well...

What do you mean with that? You only have to forward the two Ports listed in the template (UDP). I will try that later today, edit this post with my result and if experience the same error. As said multiple times, this is not necessary! The server will always look at the config in save-data first. You can leave this field empty since it will do nothing because the Server Name in the Docker template will override this line.

This seems perfectly fine and also looks like this on my server. No, if you enter Steam credentials you will break it and it won't work. If you want to play on LAN or better speaking if you want LAN only you have to append "-lan" to the GAME_PARAMS and also on your client on you local PC, I've made a post about this here: Did you click Refresh a few times, V-Rising is a bit special when it comes to the Steam Server Browser. What error did you get when trying to connect to the server, please keep in mind that you have to forward the ports in your Router even if you are trying to connect with your local IP if you didn't append -lan to GAME_PARAMS, otherwise it won't work. Please also double check your port forwarding and also check if you forwarded the correct protocol.

I have now tried it but I can't get it to work, the container and also the dedicated server is running but I don't know what's missing or not working and since there is not much documentation on this (or at least most of it is in French) and I don't speak french I really can't help. Sorry...

You only have to edit the settings file in this location: .../vrising/save-data/Settings (all other setting files will be ignored, the path is also mentioned in the description from the container) The server name is set in the template no matter what you set in the config file. Are you sure that you've forwarded the correct protocol too (in this case only UDP <- TCP is not needed!!!) Would be the same if you set it to "please do not enable bepinex" or "i dont want bepiniex", just leave it empty. I set up a new instance on my server and I can see it fine in the Steam Server Browser: If I forward the ports I can see it here too (and of course can connect to it, otherwise you won't see the indication that I have played on it like in the screenshot below): I don't know playit.gg but the timeout usually means that somwthing with the port forwarding is wrong, if I close the ports then I get also a timeout error.

Yes: Source: https://www.ginx.tv/en/v-rising/v-rising-lan-mode-guide-enable-settings

This is probably why it won't work for you. I've update the template about 7 months ago because they changed how the ports work. In the past every player needs it's own unique TCP port where now you only need to forward two ports 16261 & 16262 UDP: (you will only see that when you pull a fresh template from the CA App) But thanks for pointing that out, I forgot to delete the TCP port entry which I've did now.

Not yet, it‘s still on my to do list.

Wenn du es nicht meldest wird es nicht besser, so viel kann ich dazu sagen und es wird nicht besser werden. Überleg doch mal, du bist jetzt mehr oder weniger gezwungen auf 6.11.x zu bleiben. Du bist auch sicher nicht der einzige der dann davon betroffen ist. Nochmal, melde das. Ich meine, mir persönlich ist es in diesem Fall egal wenn ich ehrlich bin weil ich keine Fritzbox habe und bei mir alles funktioniert aber du bist nicht alleine und um so mehr es melden um so schneller kann es behoben werden aber wenn es keiner magt dann wird vermutlich auch nix behoben. 😉 Just my two Euro cents…

Yes you could but I don‘t see any benefit because this is a file manager and I don‘t think that it features any new major changes with a minor release. Anyways Debian Bookworm should be released in July and I will update my containers after a waiting period after the release of about a month (the release of Bullseye was a bit rough in my opinion).

Don't know how you are doing it. Since I'm using Debian Bullseye in the container the latest available version is 2.7.2-2 (see here), of course you could do it manually but on a container update that will be wiped again. May I ask why do you want to update it anyways? Is something not working for you?

Please read this post: No, because even if it does now that doesn't mean that Nvidia will break it in the future, this was the case for many card over time.

You know that this comes with the downside of lower image quality (more blockyness) because the low poer mode was created for video calls, so to speak web cam encoding and decoding. Please read this: https://wiki.archlinux.org/title/intel_graphics#Enable_GuC_/_HuC_firmware_loading No, not necessary, please read this: https://wiki.archlinux.org/title/intel_graphics#Framebuffer_compression_(enable_fbc)

This should be no issue for this chip at all.

I thin you‘ve followed the video by spx correct? Of so you have to place the files in /luckybackup/… not in /root/… because if you put the files in /root/… everytime a container update is done the files will be wiped. Please read this comment and the following ones:

Hast du denn eine bug report gemacht? Wenn nein, warum nicht? Es wird sich nichts ändern wenn du nichts sagst und es greift dich auch sicher keiner an weil du evtl was falsch eingestellt hast aber es wäre doch super gewesen wenn du es gemeldet hättest denn überleg mal, wie soll sich was ändern oder das Problem gefixt werden wenn es keiner meldet…

Warum machst du es nicht einfach, dir ist doch keiner böse wenn du es dort postest. Wenn du auf 6.11.5 keine Probleme hattest und seit dem Upgrade Probleme hast dann bitte erstell doch einen Bug report, ich verstehe deine Bedenken hier nicht ganz.

Aber trotzdem solltest du einen Bug report auf machen, im Deutschen bereich lesen die Entwickler nicht mit, wie auch... Vergiss nicht, überall wo du hier postest verlässt du dich auf die Community, die Bug Reports werden aktiv von den Entwicklern gelesen.

Wäre es dann nicht besser wenn du einen Bug report erstellst hier mit deinen Diagnostics damit sich das Problem jemand ansehen kann: https://forums.unraid.net/bug-reports/prereleases/

Which game?

From what I know it is and back when I created the container it was working fine, it is also in the description from the container: Yes, because the name in the Docker template overrides the config file.