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.

Rev0991

Members
  • Joined

  • Last visited

  1. Yup, same operator read error over here. Tried to work with another AI to fix the errors shown in the logs, didn't have any success. Seems this issue came with the latest update as my docker container updated last night.
  2. I finally got it working with Kimi! I'm not the most tech savvy person, so it took me a lot longer than I anticipated. I'll edit my previous comment to provide the changes I had made so that if other users want to go this route, they'll know how to do it. On a side note jdhill777, I asked my OpenClaw bot if there were any potential security issues and what it's able to view on my server. Take it with a grain of salt, as again, I'm not as tech savvy as you. My bot stated: If I escalated: • Escape the container and access the host filesystem (your Unraid system) • See/modify files outside /root/.openclaw/workspace • Potentially access other containers • Run commands on the host as whatever user the container runtime uses How to lock it down so only you control the system: 1. NoNewPrivs — zero downside, blocks all privilege escalation attempts 2. Drop capabilities — removes ~30 unnecessary kernel permissions 3. Read-only root — trickier; I'd need to test if OpenClaw writes to /tmp, /var, etc. Key points to include: • Current template runs as root with no privilege restrictions • Suggest adding --security-opt no-new-privileges:true --cap-drop ALL to ExtraParams • These are zero-breaking-change security improvements • Cite Docker security best practices
  3. Is it possible to add Kimi? EDIT: After a few hours of testing, I was able to successfully get my bot up and running with Kimi 2.5. Step 1: https://platform.moonshot.ai/console You have to get the API key from here, not Kimi Code. Recharge the account and get your API key Step 2: Replace your OpenClaw JSON file with the code below Note: I had Telegram setup on my bot, so it has the parameters already included below if you want to add your own Telegram bot. Change 'UPDATE' listed under botToken for your bot token, then replace 'UPDATE' under allowFrom with your Telegram user ID. Step 3: Edit your OpenClaw container and add variable Name: MOONSHOT API KEY Key: MOONSHOT_API_KEY Value: Your API Key Done. { "meta": { "lastTouchedVersion": "2026.1.30", "lastTouchedAt": "2026-02-01T01:13:25.232Z" }, "models": { "mode": "merge", "providers": { "moonshot": { "baseUrl": "https://api.moonshot.ai/v1", "apiKey": "${MOONSHOT_API_KEY}", "api": "openai-completions", "models": [ { "id": "kimi-k2.5", "name": "Kimi K2.5", "reasoning": false, "input": ["text"], "cost": { "input": 0, "output": 0, "cacheRead": 0, "cacheWrite": 0 }, "contextWindow": 256000, "maxTokens": 8192 } ] } } }, "agents": { "defaults": { "model": { "primary": "moonshot/kimi-k2.5" }, "models": { "moonshot/kimi-k2.5": { "alias": "Kimi K2.5" } }, "maxConcurrent": 4, "subagents": { "maxConcurrent": 8 } } }, "messages": { "ackReactionScope": "group-mentions" }, "commands": { "native": "auto", "nativeSkills": "auto" }, "channels": { "telegram": { "dmPolicy": "pairing", "botToken": "UPDATE", "allowFrom": [ "UPDATE", "UPDATE" ], "groupPolicy": "allowlist", "streamMode": "partial", "actions": { "reactions": true, "sendMessage": true } } }, "gateway": { "mode": "local", "bind": "lan", "controlUi": { "enabled": true, "allowInsecureAuth": true }, "auth": { "mode": "token" } }, "plugins": { "entries": { "telegram": { "enabled": true } } } }

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.