Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] OpenClaw — AI Personal Assistant

Featured Replies

8 hours ago, unraid-user said:

I have mine connected to OpenAI API. I stuck $20 on it and have used about $2 over 2 days of queries here and there.

My issues with running OpenClaw in a container is I get timeouts from requests that take longer than a minute. Trying to work out where in the pipeline that's happening. Also because OpenClaw is running in a unraid container it doesn't have access to a few system calls so I feel I'm not letting OpenClaw do all it can do. I've considered sticking it into a linux VM instead just to check out if there's a significant different in usability.

Right now I am slowly using a couple of features and not rushing into getting lots of skills working. Brave API search is working. GitHub integration is working. It's checked out a project for me and added files to dockerise it and checked them in. Simple stuff, but I prefer getting stuff working before moving onto other skills. So it's limited use right now but mostly because I want to go at a slower pace.

If you do the linux VM idea let me know how that goes, i am curious on this myself since it wouldn't need a lot of cores, storage or ram to be usage.

  • Replies 201
  • Views 91.6k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Sharing my local ollama settings. "models": { "providers": { "ollama": { "baseUrl": "http://xxx.xxx.xxx.xxx:11434/v1", "apiKey": "ollama", "api": "openai-responses

  • PikkonMG
    PikkonMG

    If your on chrome or like me edge then edge://flags/#unsafely-treat-insecure-origin-as-secure Enable Insecure origins treated as secure and add your local ip on unraid server running openclaw I.E http

  • Can't seem to find the template on community apps. Was this published yet?

Posted Images

Hi Team,

Have you guys been having problems with the more recent versions of Openclaw i ran into token issues on .15(resolved by matching the systemd config to the openclaw.json) .17 had an issue with telegramand .19 had an issue with telegram and not being able to connect to the tui. Think i will wait a while on .15 before trying to upgrade again.

All good seems a few changes and conflicts as below, in case anyone else seeing issues with bind to lan

  • Telegramstreaming: true config fix

  • IPv6/Nodeipv4-force.js preload script

  • WebchatdangerouslyDisableDeviceAuth: true + allowInsecureAuth: true

Edited by Draco

On 2/4/2026 at 8:18 AM, Timminater said:

U can use
node dist/index.js
instead of the openclaw command for everything.

So dont use
openclaw onboard
in the console, but use:
node dist/index.js onboard

Looks like all commands work this way.

Couple of questions.

You can do an alias so that the openclaw commands will still work. Can that be done?

alias openclaw="node dist/index.js"

Can some options for local models and sources be added?

On 2/4/2026 at 8:18 AM, Timminater said:

U can use
node dist/index.js
instead of the openclaw command for everything.

So dont use
openclaw onboard
in the console, but use:
node dist/index.js onboard

Looks like all commands work this way.

Few things.

Can an alias be added to so openclaw commands will work?

Also can options for local models and sources be added?

I just wanted to put down the steps I had to take to save anyone else some time.

  1. Install via Community Apps.

  2. Generate and enter gateway token

  3. Add Discord Bot Token (or other channel)

  4. Add Gemini API Key (or other).

  5. Apply.

  6. Command from container console: NONINTERACTIVE=1 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

  7. Command from container console: node dist/index.js onboard

  8. Go through quickstart wizard. Finish.

  9. Open http://YOUR-IP:18789/?token=YOUR-GATEWAY-TOKEN

  10. If you are getting gateway errors go to appdata/openclaw/config/ and download openclaw.json and open in text. Check the gateway token! Mine was changed for some reason. If different take the token from the json and change the variable in the container, then go back to http://YOUR-IP:18789/?token=YOUR-NEW-GATEWAY-TOKEN.

Has anyone got browser automation working? I am running chrome on another machine on my LAN. I modified the chrome extension to connect to my local "unraid" ip. The plugin says it can properly authenticate after i paste the token, but when i am on the page i want to control i receive a message that the relay is not reachable.

will node.js persist through updates if it was installed after homebrew was installed?

Here's a tip, don't use 'hybrid' or 'restart' options here: https://docs.openclaw.ai/gateway/configuration#reload-modes

Spent $15 on Opus figuring out why my plugin install won't work in docker. 😅

'openclaw plugins install' writes to openclaw.json which triggers the

gateway config watcher. Changes to 'plugins.*' have kind="restart" in

reload rules. Gateway is PID 1 in Docker, so restart = container death

mid-install. npm install never finishes, node_modules missing on reboot.

On 2/23/2026 at 3:37 AM, burgess22 said:

will node.js persist through updates if it was installed after homebrew was installed?

No. I had to rerun the commands and reinstall everything the second time I ran setup.

Hey, I updated OpenClaw Docker from the CA Store and now the container won't start. The log says:

"2026-02-27T09:42:25.247+01:00 Gateway failed to start: Error: non-loopback Control UI requires gateway.controlUi.allowedOrigins (set explicit origins), or set gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true to use Host-header origin fallback mode"

Has anyone else had this problem? Or how can I solve it?

Edit

Go to Shares / appdata / openclaw / config / openclaw.json and set this:
"gateway": {

"mode": "local",

"bind": "lan",

"controlUi": {

"allowInsecureAuth": true,

"dangerouslyAllowHostHeaderOriginFallback": true

},

Now OpenClaw is back :-)

Edited by Trustwbc

On 2/27/2026 at 12:03 PM, Trustwbc said:

Hey, I updated OpenClaw Docker from the CA Store and now the container won't start. The log says:

"2026-02-27T09:42:25.247+01:00 Gateway failed to start: Error: non-loopback Control UI requires gateway.controlUi.allowedOrigins (set explicit origins), or set gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true to use Host-header origin fallback mode"

Has anyone else had this problem? Or how can I solve it?

Edit

Go to Shares / appdata / openclaw / config / openclaw.json and set this:
"gateway": {

"mode": "local",

"bind": "lan",

"controlUi": {

"allowInsecureAuth": true,

"dangerouslyAllowHostHeaderOriginFallback": true

},

Now OpenClaw is back :-)

Thank you! It worked

Hi there,

Firstly I'm a beginner and I looked online but couldn't find the answer.
I can't seem to activate the gateway. ) Could you please help me?

Thanks.

Screenshot 2026-03-01 at 10.08.59.png

Screenshot 2026-03-01 at 11.09.50.png

On 2/2/2026 at 3:54 AM, jdhill777 said:
node $(find /app/node_modules/.pnpm -path "*/playwright-core@*/cli.js" | head -1) install chromium

That did the trick for me but i also had to install deps using the same principle to fix this error:

error while loading shared libraries: libnspr4.so: cannot open shared object file: No such file or directory

Fix:
node $(find /app/node_modules/.pnpm -path "*/playwright-core@*/cli.js" | head -1) install-deps

On 2/6/2026 at 5:45 PM, dub19 said:

I had this issue when i first spun it up as well. To get the openclaw commands to register, you need to add the npm link command to the post args in a very specific place...

<PostArgs>
sh -c "mkdir -p /root/.openclaw /home/linuxbrew /var/run/tailscale; [ -s /root/.openclaw/openclaw.json ] || echo '{\"gateway\":{\"mode\":\"local\",\"bind\":\"loopback\",\"controlUi\":{\"allowInsecureAuth\":true},\"auth\":{\"allowTailscale\":true},\"tailscale\":{\"mode\":\"serve\"}}}' > /root/.openclaw/openclaw.json; curl -fsSL https://pkgs.tailscale.com/stable/tailscale_latest_amd64.tgz | tar -xzf - -C /tmp && cp /tmp/tailscale_*_amd64/tailscale* /usr/local/bin/; tailscaled --tun=userspace-networking --state=/var/lib/tailscale/tailscaled.state --socket=/var/run/tailscale/tailscaled.sock & sleep 5; tailscale up --authkey=${TAILSCALE_AUTHKEY} --hostname=openclaw --accept-routes=false; cd /app & npm link & exec node dist/index.js gateway --bind loopback "

Explanation from Perplexity...
What npm link Does in This Context

In this Docker entrypoint script, npm link is being used to create a global symlink for the Node.js package located in /app. This makes the package and any CLI tools defined in its package.json available globally within the container.

How it works

When npm link is executed in a directory containing a package.json, it:

  1. Creates a symbolic link in the global node_modules folder pointing to /app

  2. Links any bin executables defined in the package to the global npm binary directory (e.g., {prefix}/bin/{name})

Why it's used here

In the OpenClaw container startup:

cd /app & npm link & exec node dist/index.js gateway --bind loopback

The npm link serves to globally expose the OpenClaw CLI tools. This enables:

  • Running openclaw commands from anywhere in the container without specifying the full path

  • Access to the package's binaries as system commands

  • Development-style convenience where the package behaves like a globally installed npm package

The Full Sequence

Step

Command

Purpose

1

cd /app

Navigate to application directory

2

npm link

Create global symlink for the package and its CLI binaries

3

exec node dist/index.js

Start the gateway service

The & operators run these commands in parallel, allowing the main application to start while npm link completes its filesystem operations in the background.


Not the intended use perhaps, but this post helped me set up tailscale!

Hi, I can't make it work.

At first, I had this message:

origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)

So, I added my unRaid IP to the allowedOrigins in the openclaw.json.

But now, when I go the the URL http://[unRaid IP]:18789/?token=[token], it redirects me to http://[unRaid IP]:18789/chat?session=main with this error:

control ui requires device identity (use HTTPS or localhost secure context)

What can I do ?

I’ve downloaded the latest update and it’s no longer working. It won’t connect to http://url/#token either.

Edit: I reverted to the previous version.(2026.3.11) Thankfully, it worked.

Screenshot 2026-03-13 at 17.25.45.png

Edited by Lethe

13 hours ago, Benji7790 said:

Hi, I can't make it work.

At first, I had this message:

origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)

So, I added my unRaid IP to the allowedOrigins in the openclaw.json.

But now, when I go the the URL http://[unRaid IP]:18789/?token=[token], it redirects me to http://[unRaid IP]:18789/chat?session=main with this error:

control ui requires device identity (use HTTPS or localhost secure context)

What can I do ?

I'm also gettting this error

For people with origin not allowed follow these steps to create an ssl connection

  1. For openclaw docker network set to custom br0 in order for you openclaw to have a differing ip then your unraid server.

  2. Download and install nginx proxy manager from unraid apps. Proxy will also have its own ip.

  3. Create a proxy and self signed cert and point to the openclaw ip and default port.

  4. Try and create a DNS entry eg openclaw.home pointing to you nginx proxy which in turn will forward to you openclaw instance,

Hope this helps

Edited by dvkwong

On 3/13/2026 at 10:31 PM, Lethe said:

I’ve downloaded the latest update and it’s no longer working. It won’t connect to http://url/#token either.

Edit: I reverted to the previous version.(2026.3.11) Thankfully, it worked.

Screenshot 2026-03-13 at 17.25.45.png

Ended up doing the same back down to 2026.3.11.

3 hours ago, TomasJAnderson said:

Ended up doing the same back down to 2026.3.11.

I haven’t tried '3.13', but 'v2026.3.13-beta.1' works for me

I I have ollama container for Intel GPU can I use UT with this? ollama container for Intel GPU can I use UT with this?

Clearly I am doing something wrong but I can't for the life of me getting this thing to run.. I tried reverting back to a prior version (2026.3.11) and got further that time then ever but it still complains about needing https or using local host, I even tried an ssh tunnel to the server but still a no go.. Hopefully whatever has changed gets correct soon and I'll revisit...

same for me, tried few times for couple of hours without any luck. It worked once a month ago, but not anymore.

I will wait for smart people of the internet to make this easier, and I revisit.

Hello, after I intalled the openclaw on my unraid, It show me 'origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)'

I try to search on google, but no working. anbody know how to fix?

Thanks

Edited by expensive-vat8747

On 3/21/2026 at 11:01 PM, expensive-vat8747 said:

Hello, after I intalled the openclaw on my unraid, It show me 'origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)'

I try to search on google, but no working. anbody know how to fix?

Thanks

If your on chrome or like me edge then edge://flags/#unsafely-treat-insecure-origin-as-secure
Enable Insecure origins treated as secure and add your local ip on unraid server running openclaw I.E http://192.168.1.100:18789
Edit your openclaw.json in appdata->openclaw->config you will see section like this
"allowedOrigins": [
"http://localhost:18789",
"http://127.0.0.1:18789"
],
Edit it to include your Unraid Servers IP
"allowedOrigins": [
"http://localhost:18789",
"http://192.168.1.100:18789",
"http://host-name-or-whatever:18789",
"http://127.0.0.1:18789"
],
Start OpenClaw Docker and open the webui. then just close it.
Open console terminal for OpenClaw docker and run
printenv OPENCLAW_GATEWAY_TOKEN

openclaw devices list --token "$OPENCLAW_GATEWAY_TOKEN"

It will spit out some stuff like
🦞 OpenClaw 2026.3.24 (unknown) — Say "stop" and I'll stop—say "ship" and we'll both learn a lesson. │ penclaw devices approve --latest --token "$OPENCLAW_GATEWAY_TOKEN"◇ Pending (1)


under that you will see your Pending (1) client and you will see a key something like xxxxxxx-xxxx-xxxx-xxxx-xxxxxx3971

copy that key and run
openclaw devices approve xxxxxxx-xxxx-xxxx-xxxx-xxxxxx3971 --token "$OPENCLAW_GATEWAY_TOKEN"

After that try opening webui should work.

If you use a reverse proxy you could set it up at OpnClaw and probaly skip the "Enable Insecure origins treated as secure"

Edited by PikkonMG

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.