ich777

No, should I? The description is good and all but it seems like that this script just installs the default hbbs and hbbr part from RustDesk and the API server on top. What is the main benefit? Is something wrong with RustDesk itself?

Thanks for the report. Please update the container itself and it will work again.

Then it's most likely a issue with the port forwarding, please double check the forwarded ports and also if the correct protocol is set. I would also recommend that you try it with the default settings and see if that is working properly (I would recommend if you try it with the default configuration that you at least change the server name). This is not an issue and nothing to worry about.

@Amane please create a bug report here: https://forums.unraid.net/bug-reports/stable-releases/ This is not the right place to report a bug.

Are you talking about ARK:Survival Evolved or ARK:Survival Ascended? Please note these are two different games and basically using a different Engine.

Just mark it as solved.

I had multiple people in this thread which had the same issue: Here is one who was able to solve it by upgrading the PSU: Here is one who never responded again but is seems to be fixed now (because I found a follow up Diagnostics from him and the card is properly recognized) : The next one is this here which I'm also not sure if it's fixed: However please keep in mind that Linux is a lot more sensitive to thermal issues or power delivery issues for example. I remember one user who had the GPU fall from the bus because of a thermal issue.

@KingHawk this is now solved in this post correct:

Can you please clarify that a bit more? According to the documentation (which is not very clear) you have to user ?Port=7779

Maybe they changed it again, I have already changed the description from the container so that it says to put the server token in the config.txt If you don't need VAC then don't enable it.

Die größte muss immer die Partiy sein. Ich vermute wir reden hier über das XFS Array, das kommt immer drauf an wie sie kaputt geht: Wenn sie ganz aus dem System fällt: Ja Wenn sie einen SMART fehler hat: Ja Wenn sie defekte Sektoren hat: Nur bei einem Parity Check Wenn sie Bitrot hat: Nein BTW, bitte keine Doppelposts!

Ich würde dir eher zu einem USB Stick raten. Such mal auf Amazon nach einem Transcend USB 2.0 zB. den hier. Bei einem SD Karten Reader läufst du immer gefahr das der keine gültig UUID hat und vergiss nicht die können auch kaputt gehen. BTW Bitte keine Doppelposts!

Sorry, I can't help here since the documentation here also says that you can enable VAC with: enableVAC on I think you have to set those values now in the config.txt (please be sure to do that also in the config file). EDIT: I just tried it on a fresh installation and it is working perfectly fine: Make sure to change these two lines: The file is located: .../theforest/config/config.txt <- please make sure to stop the container first and then edit the file.

Thanks. The first thing that I noticed is that your BIOS is out of date, make sure to update your BIOS. Please make also sure to disable C-States in the BIOS since these cause (at least on Linux) issues with Nvidia cards. I deleted the Diagnostics from above because there was something in the go file that didn't need to be public. BTW, I think that your Motherboard supports Resizable BAR support maybe it is named differently.

Sorry, I completely overlooked your post. Can you please post a screenshot from your template (maybe blur the token). May I ask for what Game ID did you create the token?

I need the Diagnostics not the Nvidia bugreport.

Are you really sure that your RAM is okay? As said my best guess is that there is something wrong with the RAM and the files not installing correctly. Are you on the latest BIOS version? There must be something else going on since I also tested this exact driver package and it is working fine over here.

Please make also sure that the files stay on this Pool and are not moved to the Array in the Share settings because otherwise you will run into problems again.

Have you yet tried to reboot? BTW, this is the wrong location the file is located in /usr/lib64 you are actually looking at the 32bit libraries in the screenshot above. Have you any special scripts in place that maybe modify the PATH variable on your system or something similar? I can't see anything obvious from your Diagnostics at a first glance. The only thing that is a bit strange that the driver got not installed early in the boot process since it should be installed and pick up the card early. You could of course try to: Remove the plugin Reboot Install the plugin Reboot May I ask why did you had to remove the docker.img? Hardware fault? My best guess else is that something is going on with the RAM but that is just a vague guess since the driver get's also installed into the rootfs which on Unraid is the system memory.

Please post your Diagnostics.

Why did you enable validation? Please disable it. On what system do you try to run the container? Did you change already some config files? Please note that I always recommend to use the real file path (this applies to the game files only) not the FUSE file path to the files. /mnt/user/... in this case is the FUSE file path and some games will segfault and refuse to start.

The path in the container to the gamefiles is always: /serverdata/serverfiles/ Sorry but I really don't know how to mod a ARK server.

Did you change something in the template? It seems the container can't find the files or is not able to start V-Rising. Are you sure that the path for the Gamefiles is correct? May I ask why did you enable verification from the game files? On what system are you trying to run the container?

Please always include Diagnostics. Anyways, you got a XID 79 error which you can read more about here. On what BIOS version are you? In which slot on your Motherboard is the card? Is Above 4G Decoding and Resizable BAR support enabled in the BIOS?

I would recommend that you create an issue over here on GitHub in the repository form @Frank Crawford since he is the maintainer for the driver and I only made a plugin that his driver is available for Unraid.