Mrtj18

Wow, after giving this a break for a while, from being frustrated, because i was obviously something I was doing wrong. I did what you suggested, by updating both openclaw and using the command you just provided of "npm i [email protected]" within the Openclaw console, then asking the basic question of " what unraid tools do I have available?". Then boom, I finally got responses from my server. Thank you so much fort your patience!

Mmmm.... Maybe there's something I don't understand here, if I typed into openclaw, " what's my Unraid drive health" it should be about to see my unraid drives and provide feedback correct? Because when I do that, the following results is what I get , in my previous posts. But thanks for the assistance!

That's odd, I don't have any websites I'm attempting to visit. Plus when I type in any command listed from your GitHub page ( like unraid_list_disk) I receive unraid not connected responses from openclaw. I also receive the same error others have from your GitHub page when I click on the link that the logs provide when attempting to connect to your plug-in. Attached in the screenshot. Your instructions from the GitHub page says just to double check the openclaw.json file and restart the service along with creating a new key. But I still receive the same error.

Im back, lol... I made some progress that openclaw can now see the plugin, and the plugin is communicating back with me, but I am now getting a 401 error. Im sure this has something to do with api. But I have attempted to re-create the unraid and openclaw api multiple times. Can anyone point me in the right direction? log edit: I think this could be a new bug not dealing with unraidclaw https://github.com/openclaw/openclaw/issues/77800

https://www.phoronix.com/news/AMDGPU-Pipe-Reset-Support I really hope this finally contains the driver level support we will finally needed to get rid of the awful AMD reset bug for once and for all.

Thank you for taking a look at the .json file for me. seems like after making the correction you suggested, I still get the "Invalid openclaw.json unriadclaw api key error". Which will refuse to let openclaw start. I will continue to read around and build up my knowledge. Thanks for your help

upon inspection I have found that my openclaw.json was missing the required lines mentioned in the install instructions. ( I dont know how, I had them inserted correctly before) and now when I attempt to insert them it is giving me syntax error or unrecognized key error when inserting the required config lines or api key. Do you have any tips to clean this up? Openai was still giving me bad config lines and commas to insert. I took out my identifying info and api's the best I could. openclaw.json

Hello I know this should be a stright forward plugin, but running the latest stable unraid and latest unraidclaw, I cant get unraidclaw and openclaw to speak to each other. I have attempted the following: Uninstalled and reinstalled the plugin. Checked the node --version and /etc/rc.d/rc.unraidclaw status to make sure those are good. And they are Double checked my openclaw.json file to make sure "tlsSkipVerify: true" and it is. I have Created multiple keys and double checked my openclaw.json file try different api keys. To no success But no matter what I try, openclaw and unraidclaw just do not speak to each other. Any time I type something that the unraidclaw should understand I get a wall of text, that pops up in the logs, which is attached below, and I continue to get api resonses or calls. Any assistance would be great! 2026-05-12T171544.731-0500 [reload].txt

First make sure you have the correct parameters and the nvidia driver installed from this link. Next make sure you can get the docker container to constantly run. Mine was attempting to open and kept force closing. Due to the same error everone was reporting here. ( I had to uninstall and reinstall the container) Then I opened the console and did sudo apt remove sunshine. To remove sunshine, so the error would stop in the logs. (make sure you can enter the container from the webUI at this point) Lastly I opened up the software option within the container (Applications-System-Software) and installed the Flathub User option to reinstall sunshine. Then the container started working correctly for me. I still get the xorg11 errors, but the container starts correctly, and I can connect to the docker container from my steam deck and phone like usuall. Hope this helps

You need the --runtime=nvidia in extra parameters. Also make sure you have the nvidia visible devices, and nvidia driver capabilities parameters. I personally had to uninstall sunshine via the command line, and reinstall it via the software center from within the docker container.

I had the same issue, when attempting to downgrade my GPU drivers, my GPU was no longer detected. After a few reboots and going back to the latest driver, I was about to get the desktop to the steam headless container. And then I noticed sunshine was not starting. I had to install the "user" version of sunshine and Firefox, for sunshine to work on restart again. From the software center.

I can confirm after re-reading your posts and checking the docker container setup I had for ollama. I had the --gpus=all flag in the extra parameters section. Thus causing ollama not to start. As soon as I placed what you mentioned in the 2nd post of this thread. the --runtime=nvidia flag there, the docker started. I also removed all --gpus=all flags from other containers I have. As well as placed the actual GPU-ID in the nvidia visable devices section as well. I had All listed there. My steam-headless issue is an issue with the container itself. It does not like to play well with the latest nvidia drivers for some reason. I see other reports of users downgrading to 580.142 driver. I will just possibly wait on a new update to the container. Or try and find the previous docker image release name, because I didnt have the issue before upgrading. So sorry, user error once again. lol

I would like to confirm I am having the same issues as others expressed in the thread, some of my docker containers still work with the latest Nvidia open source drives like emby. But steam-headless and ollama refuse to start, stating the exact same logs like previously mentioned. I will attempt to downgrade my driver's. Because this happened for me once I updated both steam-headless and ollama to their latest docker image. Emby has not had a recent update and I assume that's why it's still working. And unfortunately I don't have a current backup of my docker images. 😞

I think some of these dummy HDMI adapters are not so good.... Mine are supposed to do 4k 120hrz. Even though I can set it in the panel, in game never gets over 1080p. I think I just have to hook up a real monitor. For it to work correctly.

Sorry to resurrect an old thread, but your suggestion to change bios helped me as well. I have a x870e MSI tomohawk motherboard. And after updating my bios unraid would refuse to start. Didn't matter what USB drive I tried, what port I used (3.0 or 2.0) it just refused to start. It wasn't until I read this post that I started downloading all the bios'ies i could find on my motherboards official site, to find one that worked. And I found one eventually, it even fixed my issue that I was having that my server would not boot unless I moved my USB to a different port. If I didn't do that my server would just boot again, to a solid black screen.

So for me to fix the permission issues. I had to uninstall the docker container. ( Don't delete any appdata data). And reinstalled it from the previous docker apps section from apps on unraid. After that all the weird permission errors are gone, and I have no issue opening anything

Yep just noticed it today, I'm getting access denied errors. Seems if we are not logged in as root. I'm going to download debain trexie version of Firefox and attempt to install it via command line when logged in as root to see if that fixes the issue

I have a steam deck as well, I saw this, but was not 100% sure of the benefits of running this. Have you gotten it too work? If so, what's the benefits?

I personally wouldn't recommend it, but the only way I was able to fix my error was to uninstall sunshine via command line, and reinstall it via the software manager. Now I have to figure out how to get sunshine to auto start with the container lol.

Has anyone encountered an error like this..... My sunshine icon constantly blinks, and it was working fine just the other day. I can no longer connect via moonlight because sunshine is constantly starting and stopping repeatedly and filling my logs. I even installed a new separate container was running into the same error.

I ran across this on GitHub, maybe this can help us nextcloud users get appAPI up and running on our nextcloud setups that don't use the all in one? https://github.com/nextcloud/docker-socket-proxy/issues/39

I have seen this issue as well on my end, and I cannot get nextcloud to connect to my open-ai docker instance. Every time I attempt to open the assistant settings page, I get the internal error screen. I figured it was due to the appAPI not being setup, but I'm not sure. So I'm waiting to find a tutorial, on this as well. Maybe it can fix the only two issues I have with my nextcloud setup.

Thanks for the great advice, I was able to use my IGPU for the ryzen 9 9950x using a windows 11 VM. Now, following the same steps I am unable to create a Linux VM using my AMD IGPU, anyone have any advice because the same steps wont work for me? I constatnly get the black blank VM screen.

I can confirm the updated version of nextcloud, you only have to update it, from the community apps section like all other apps. No more going into the container itself to update. I personally don't have a off site backup of nextcloud, just a backup of it's appdata and network shared folder files on a separate USB drive.

Yeah I do co-sign the above.... Don't be lazy and screw up your working install like I did lol