OpenClaw for Unraid

A containerized deployment of OpenClaw (formerly Moltbot/Clawdbot) designed specifically for Unraid.

🚀 Quick Start

1. Install: Add the container using the Unraid Community App.
2. Start: Start the OpenClaw app.
3. Get Token: Check the App logs. Look for the OpenClaw Startup banner to find your Gateway Token.
   • Tip: You can copy this token into the "Gateway Token" field in the Unraid template to make it permanent.
4. Access: Open the WebUI.
   • Required: See below to enable HTTPS.

---

HTTPS & Remote Access

OpenClaw uses the WebCrypto API to secure your chat. Modern browsers BLOCK this API on insecure HTTP connections (unless you are using localhost).

If you access the bot via IP (e.g., http://192.168.0.1:18789), the page may load but immediately disconnect with Error 1008.

Option 1: Tailscale (Recommended)

The easiest way to get valid HTTPS on Unraid is using Tailscale Serve.

1. Install Tailscale on Unraid.
2. Open Unraid Terminal (>_).
3. Run the serve command (using port 8443 as an example):

   tailscale serve --bg --https=8443 http://localhost:18789

4. Update Unraid Template:
   • Edit the Public URL variable in the OpenClaw container settings.
   • Set it to your full HTTPS URL: https://your-machine.tailnet.ts.net:8443 (No trailing slash).
5. Access the bot at that HTTPS URL.

Note: While --bg attempts to save the config, Unraid's ephemeral nature means settings can be lost on reboot. For maximum reliability, use the Unraid User Scripts plugin to run the command above "At Startup of Array".

Option 2: Nginx Proxy Manager

If using a reverse proxy (like Nginx Proxy Manager or Swag), you must enable:

• Websockets Support
• SSL (HTTPS)

---

Device Pairing

For security, OpenClaw requires manual approval for any device connecting from a non-local IP (including Tailscale).

1. Connect via your browser. You will see "Disconnected (1008): Pairing Required".
2. Leave the tab open.
3. Open the Unraid Docker Console for OpenClaw.
4. Run this command to see the Request ID:

   # We pass the token explicitly since the console session is new
   OPENCLAW_GATEWAY_TOKEN=$(cat /home/node/.openclaw/.generated_token) node dist/index.js devices list

5. Approve the request (e.g., replace abcd-1234-efgh-5678 with your ID):

   OPENCLAW_GATEWAY_TOKEN=$(cat /home/node/.openclaw/.generated_token) node dist/index.js devices approve abcd-1234-efgh-5678

6. Your browser will instantly connect.

---

Running Multiple Instances (Multi-User)

OpenClaw is a "Single-Player" AI with one memory and one chat history. To support multiple users (e.g., you and a partner), you must run separate Docker containers.

Step 1: Add a Second Container

1. Go to the Docker tab in Unraid.
2. Click Add Container at the bottom.
3. In the Template dropdown, select OpenClaw (it may appear under "User Templates" if you have installed it previously, or simply search for it again in Community Apps and install a second copy).

Alternative Method: You can also simply install the app again from the Apps tab. Unraid will detect the existing install and ask if you want to reinstall or install a second instance (depending on version), or you can manually change the name during the installation screen.

Step 2: Customize Configuration

You must change these 3 settings to prevent conflicts with the first bot:

1. Name: Change to something unique (e.g., OpenClaw - User2).
2. WebUI Port:
   • Change the Host Port to 18790 (or any free port).
   • Leave the Container Port as 18789.
3. Appdata Path:
   • Change the Host Path to /mnt/user/appdata/openclaw-user2.
   • If you skip this, both bots will corrupt the same database.

Step 3: HTTPS for the Second Bot

Since the new bot is on a new port (18790), you need a separate secure tunnel.

1. Open Unraid Terminal.
2. Run a second serve command using a different HTTPS port (e.g., 8444):

   # Serve the second bot (Host Port 18790) on HTTPS port 8444
   tailscale serve --bg --https=8444 http://localhost:18790

3. Update the Variable:
   • In the OpenClaw - User2 settings, set Public URL to: https://your-machine.tailnet.ts.net:8444

Result:

• User 1: Access via https://...:8443
• User 2: Access via https://...:8444

---

🛠 Troubleshooting

"Mixed Content" / Blank Page

• Cause: You are accessing via HTTPS, but the app thinks it is HTTP.
• Fix: Set the Public URL variable in the Unraid template to your exact HTTPS address.

"Gateway Closed (1008)"

• Cause: Browser security blocking WebSockets.
• Fix: Use HTTPS. If testing locally on HTTP, try appending ?token=YOUR_TOKEN to the URL for the initial connection.