got the same problems

So close. I tried with Tailscale and it failed.

However, if I leave that out it installs and starts. I can reach it here - http://YOUR-UNRAID-IP:18789/?token=YOUR_GATEWAY_TOKEN

But It is stuck asking for https or running on local host, which I can't do on this box. Ideas?

doesnt work anymore since latest update, same error as the others here.

There was a bug that was just corrected that had to do with preloading some node packages. If you try loading

https://github.com/ghcr.io/openclaw/openclaw:2026.5.2-slim  vs :latest

in your template you may make out ok...

41 minutes ago, FlynDice said:

There was a bug that was just corrected that had to do with preloading some node packages. If you try loading

https://github.com/ghcr.io/openclaw/openclaw:2026.5.2-slim  vs :latest

in your template you may make out ok...

I don't understand what you mean, is this version you sent working?
openclaw:2026.5.2-slim

Edited May 3May 3 by Braulio Dias Ribeiro

10 hours ago, Aedankerr said:

got the same problems

This should still work https://forums.unraid.net/topic/196865-support-openclaw-ai-personal-assistant/page/6/#findComment-1614922

4 hours ago, kteach said:

So close. I tried with Tailscale and it failed.

However, if I leave that out it installs and starts. I can reach it here - http://YOUR-UNRAID-IP:18789/?token=YOUR_GATEWAY_TOKEN

But It is stuck asking for https or running on local host, which I can't do on this box. Ideas?

OpenClaw docker doesn't like trying to use tailscale the way unraid doesnt its container setup. Run tailscale directly on unraid.

ghcr.io/openclaw/openclaw:latest works fine for me now. it is co-tagged with 2026.5.2-slim right now.

see: OpenClaw tags

Edited May 3May 3 by FlynDice
link...

I know this take will probably be unpopular with community here but most will be better off running OpenClaw or Hermes on a Raspberry Pi 5 or Budget VPS with Hetzner/Contabo/OVHCloud. Downside to VPS is local llm usage but you can get around that with wireguard/tailscale.

1 hour ago, PikkonMG said:

I know this take will probably be unpopular with community here but most will be better off running OpenClaw or Hermes on a Raspberry Pi 5 or Budget VPS with Hetzner/Contabo/OVHCloud. Downside to VPS is local llm usage but you can get around that with wireguard/tailscale.

This unfortunately doesn’t work,

As after I have made the changes to the config file, and restart the docker app it reverts all changes I made.

In addition, while the app is running I loose access to the folder in windows.

(New issue for me)

Has anyone else had or has this problem and managed to resolve it?

I didn't want to create a VPS just for this...I wanted to centralize everything on unraid

12 hours ago, Aedankerr said:

This unfortunately doesn’t work,

As after I have made the changes to the config file, and restart the docker app it reverts all changes I made.

In addition, while the app is running I loose access to the folder in windows.

(New issue for me)

Just did another test install on unraid and it installed just fine. Only difference from post on page 6 is you now get your device pairing required requestId via the browser and don't have to run openclaw devices list.

Take the requestId via the browser and pair it openclaw devices approve xxxxxxxx-xxxxxx-xxxxxx-4443434cac61 --token "$OPENCLAW_GATEWAY_TOKEN"

if openclaw.json is being edited while the container is running openclaw might overwrite or revert those changes. Stop the container first, edit the file, save, then restart. Also confirm /root/.openclaw is properly bind-mounted to persistent Unraid storage (/mnt/user/appdata/openclaw) or changes may be lost during container recreation.

6 minutes ago, Braulio Dias Ribeiro said:

Has anyone else had or has this problem and managed to resolve it?

I didn't want to create a VPS just for this...I wanted to centralize everything on unraid

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

In your config dont use wildcard like * edit it to use the ip address of your unraid server

And you have to pair you device this has been posted on a few times here now you get pairing request via the browser just take that requestid and run it with openclaw devices approve xxxxxxxx-xxxxxx-xxxxxx-4443434cac61 --token "$OPENCLAW_GATEWAY_TOKEN" inside the container.

7 hours ago, PikkonMG said:

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

In your config dont use wildcard like * edit it to use the ip address of your unraid server

And you have to pair you device this has been posted on a few times here now you get pairing request via the browser just take that requestid and run it with openclaw devices approve xxxxxxxx-xxxxxx-xxxxxx-4443434cac61 --token "$OPENCLAW_GATEWAY_TOKEN" inside the container.

I did it but it didn't work....if you have one, I'll leave the prints.
I did this too:
openclaw devices approve xxxxxxxx-xxxxxx-xxxxxx-4443434cac61 --token "$OPENCLAW_GATEWAY_TOKEN"

Edited May 4May 4 by Braulio Dias Ribeiro

8 minutes ago, Braulio Dias Ribeiro said:

I did it but it didn't work....if you have one, I'll leave the prints.
I did this too:
openclaw devices approve xxxxxxxx-xxxxxx-xxxxxx-4443434cac61 --token "$OPENCLAW_GATEWAY_TOKEN"

{

"gateway": {

"mode": "local",

"bind": "lan",

"controlUi": {

"allowInsecureAuth": true,

"allowedOrigins": [

"http://localhost:18789",

"http://127.0.0.1:18789",

"http://192.168.50.250:18789"

]

},

Your request id will show up from you browser like in your post on page before. Please make sure once

you figure this out and get it running that you delete and reinstall it dont give out your requestid stuff like that. You can also unauthrize that id and get a new one using commandline inside the container if you wiosh to do that.

2 hours ago, PikkonMG said:

{

"portal": {

"modo": "local",

"ligar": "lan",

"controlUi": {

"allowInsecureAuth": true,

"OrigensPermitidas": [

" http://localhost:18789 ",

" http://127.0.0.1:18789 ",

" http://192.168.50.250:18789 "

]

},

O ID da sua solicitação será exibido no seu navegador, assim como na sua postagem anterior. Certifique-se de verificar isso antes de prosseguir.

Depois de resolver isso e conseguir fazer funcionar, você pode desinstalar e reinstalar o programa sem divulgar informações como o seu requestid. Você também pode revogar a autorização desse ID e obter um novo usando a linha de comando dentro do contêiner, se desejar.

2 hours ago, PikkonMG said:

{

"gateway": {

"mode": "local",

"bind": "lan",

"controlUi": {

"allowInsecureAuth": true,

"allowedOrigins": [

"http://localhost:18789",

"http://127.0.0.1:18789",

"http://192.168.50.250:18789"

]

},

Your request id will show up from you browser like in your post on page before. Please make sure once

you figure this out and get it running that you delete and reinstall it dont give out your requestid stuff like that. You can also unauthrize that id and get a new one using commandline inside the container if you wiosh to do that.

I deleted docker and deleted the folder in appdata. I reinstalled everything from scratch.

I added "http://192.168.50.250:18789" in the json file.

I ran the command in the docker console but I still couldn't. Did I do it right?

openclaw devices approve xxxxxxxxxxxxxxxc9d9 --token "$OPENCLAW_GATEWAY_TOKEN"




ta

Edited May 4May 4 by Braulio Dias Ribeiro

I never had to approve a browser device... telegram had to be approved but no the browser. I've been using this line under advanced in the docker template:

WebUI: http://[IP]:[PORT:18789]/#token=MyReDaCtEdGaTeWaYtOkEn

link works perfectly. I notice in a lot of screenshots i see [?token=] vs [#token=]

I posted the gateway config I have been using a few days ago.

i got around it by enabling ssh on unraid and Running the below

ssh -N -L 18789:127.0.0.1:18789 user@<UNRAID-IP>

(example... ssh -N -L 18789:127.0.0.1:18789 [email protected])

sign in, leave that window open and open 127.0.0.1:18789 in your browser

Edited May 5May 5 by Aedankerr

3 hours ago, Aedankerr said:

i got around it by enabling ssh on unraid and Running the below

ssh -N -L 18789:127.0.0.1:18789 user@<UNRAID-IP>

(example... ssh -N -L 18789:127.0.0.1:18789 [email protected])

sign in, leave that window open and open 127.0.0.1:18789 in your browser

ANOTHER Temp fix

Add the below to the config to temporarily disable the https requirement.

gateway.controlUi.dangerouslyDisableDeviceAuth = true

that works here also. Had to add it to "allowedOrigins" also...

      "allowedOrigins": [
        "http://<UNRAID-IP>:18789",
        "http://127.0.0.1:18789"
      ],

I managed to make it work.....I'll leave what I did to help others.

In docker console:

openclaw devices approve ENTER-YOUR-ID-DEVICE-HERE --token "$OPENCLAW_GATEWAY_TOKEN"

Did anyone find a WORKING solution/process to the "all tools get wiped on image update" problem?
E.g. installing clawhub binaries each time after an update gets annoying...

1 hour ago, ADvorsky said:

Did anyone find a WORKING solution/process to the "all tools get wiped on image update" problem?
E.g. installing clawhub binaries each time after an update gets annoying...

Do you have a Homebrew Path (mount for persistence) set under additional settings?

And then you have to actually install Homebrew (linuxbrew)with :

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

16 hours ago, FlynDice said:

Do you have a Homebrew Path (mount for persistence) set under additional settings?

And then you have to actually install Homebrew (linuxbrew)with :

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

not yet. investigating this... Thanks!

On 5/7/2026 at 8:16 AM, ADvorsky said:

Did anyone find a WORKING solution/process to the "all tools get wiped on image update" problem?
E.g. installing clawhub binaries each time after an update gets annoying...

Did you try asking open claw after updating?