action: finished

status: ok

summary:
---

## 🔧 Platform Health Council — Daily Check
**Saturday, February 21st, 2026 — 8:32 AM UTC**

### Overall Status: ⚠ **ATTENTION NEEDED**

---

### 🐳 Docker (64/238 running)

| Status | Count | Notes |
|--------|-------|-------|
| ✅ Healthy | 59 | Core services stable |
| ⚠ Unhealthy | 5 | See below |
| ❌ Exited | 7 | Non-critical stacks |

**Unhealthy Containers (5):**
- `ouro-qdrant-1` — 5 days unhealthy
- `memlayer-web-ui` — 5 days unhealthy
- `memlayer-service` — 5 days unhealthy
- `mcp-manager` — 5 days unhealthy
- `hr_roofing_qdrant` — 5 days unhealthy

**Exited Stacks:**
- Temporal (4 containers) — down 5 days
- `ouro-nemotron-worker-1` — exited 35h ago
- `open-webui`, `dockge` — down 5 days

---

### 🔄 PM2 (14 online / 4 stopped)

| App | Status | Restarts | Concern |
|-----|--------|----------|---------|
| `novel-os` | ❌ stopped | 943+ | **Critical** |
| `novel-os-dev` | ❌ stopped | 430+ | **Critical** |
| `omi-stt` | ❌ stopped | 1075+ | **Critical** |
| `omi-integration` | ❌ stopped | 7 | High |
| `accdrop` | ✅ online | 66 | Medium |

---

### 🖥 System Resources

| Metric | Value | Status |
|--------|-------|--------|
| **Memory** | 76/125 GB (61%) | ✅ OK |
| **Swap** | 8.0/8.0 GB (100%) | 🔴 **FULL** |
| **Load Avg** | 6.52, 6.99, 7.02 | ⚠ Elevated |
| **Root Disk** | 73% (238G free) | ✅ OK |
| **Storage** | 77% (433G free) | ⚠ Monitor |

---

### 🎮 GPU (2x RTX 3090)

| GPU | Memory | Temp | Util |
|-----|--------|------|------|
| GPU 0 | 19.7/24 GB | 48°C | 0% |
| GPU 1 | 19.6/24 GB | 34°C | 0% |

✅ GPUs healthy, memory allocated (likely cached models)

---

### 🚨 Critical Alerts

1. **Swap Exhaustion** — 100% swap used. This is causing `llamactl.service` to fail repeatedly with "Resource temporarily unavailable" (every 5 seconds in logs). System is under memory pressure.

2. **PM2 Crash Loops** — `novel-os`, `novel-os-dev`, and `omi-stt` have hundreds/thousands of restart attempts. These need investigation or should be disabled if not neede…

provider: zai


summary:
## 🔧 Fred Server Health Check
**Sunday, February 22nd, 2026 — 8:30 AM UTC**

---

### ✅ Overall Status: **OPERATIONAL** (with warnings)

---

### 🐳 Docker Containers
| Metric | Value |
|--------|-------|
| Running | 60 |
| Stopped/Exited | 7 |
| Unhealthy | 5 |

**Unhealthy Containers:**
- `ouro-qdrant-1` — Qdrant vector DB for Ouroboros
- `memlayer-web-ui` — Memory layer UI
- `memlayer-service` — Memory layer service
- `mcp-manager` — MCP manager
- `hr_roofing_qdrant` — HR Roofing vector DB

**Stopped Containers:**
- Temporal stack (4 containers) — workflow engine, intentionally stopped
- `ouro-nemotron-worker-1` — exited 2 days ago
- `open-webui`, `dockge-dockge-1` — intentionally stopped

---

### 📊 PM2 Processes
| Status | Count |
|--------|-------|
| Online | 14 |
| Stopped | 6 |

**Concerning Stopped Processes (high restart counts):**
- `omi-stt` — 1,075 restarts (Speech-to-Text)
- `tmux-web` — 501 restarts
- `novel-os` — 224 restarts
- `novel-os-dev` — 430 restarts

---

### 💾 System Resources
| Resource | Used | Total | Status |
|----------|------|-------|--------|
| Root Disk | 646G | 915G | 74% ✓ |
| /mnt/storage | 1.5T | 1.9T | 78% ✓ |
| RAM | 64Gi | 125Gi | 51% ✓ |
| **Swap** | **8.0Gi** | **8.0Gi** | **100% ⚠** |

**⚠ Warning:** Swap is fully exhausted. System is under memory pressure.

---

### 🎮 GPU Status
| GPU | VRAM Used | VRAM Total | Utilization |
|-----|-----------|------------|-------------|
| RTX 3090 #1 | 21.2 GiB | 24.6 GiB | 0% (idle) |
| RTX 3090 #2 | 19.6 GiB | 24.6 GiB | 0% (idle) |

Both GPUs have models loaded in VRAM but are currently idle.

---

### ⏱ System Uptime
**6 days, 14 hours** | Load Average: 6.30 (moderate)

---

### 🚨 Action Items
1. **Investigate swap exhaustion** — Consider adding more swap or identifying memory-hungry processes
2. **Review unhealthy Qdrant instances** — 3 Qdrant containers showing unhealthy status
3. **Fix omi-stt restart loop** — 1,075 restarts indicates a configuration issue
4. **Check memlay…


summary:
---

## 🔧 Platform Health Council — Daily Check
**Monday, February 23rd, 2026 — 8:30 AM UTC**

### System Overview
| Metric | Status | Details |
|--------|--------|---------|
| **Uptime** | ✅ 7d 14h | Load: 10.73 (72 cores, ~15% load) |
| **Memory** | ⚠ | 56/125GB used (68GB available), Swap 100% used |
| **Root Disk** | ✅ | 77% used (202GB free) |
| **Storage** | ✅ | 78% used (414GB free) |

### GPU Status (2x RTX 3090)
| GPU | Utilization | VRAM | Temp |
|-----|-------------|------|------|
| GPU 0 | 0% | 23.3/24GB (95%) | 49°C |
| GPU 1 | 0% | 23.5/24GB (96%) | 34°C |

*VRAM nearly fully allocated (likely Ollama models loaded)*

---

### Docker Containers: 62 Running
**⚠ 5 Unhealthy Containers:**
| Container | Issue |
|-----------|-------|
| `ouro-qdrant-1` | Health check failing (service running fine) |
| `memlayer-web-ui` | Health check failing |
| `memlayer-service` | 404 on `/` endpoint (wrong health path?) |
| `mcp-manager` | Health check failing |
| `hr_roofing_qdrant` | Health check failing (service running fine) |

*Note: Qdrant containers appear functional — likely misconfigured health checks*

---

### PM2 Processes: 19 Online / 5 Stopped
**Stopped (expected):**
- `cfr-command-center` (cluster mode, dev version running)
- `novel-os`, `novel-os-dev`
- `omi-integration`, `omi-stt`
- `tmux-web`

---

### Recommendations
1. **Swap at 100%** — Consider adding swap or monitoring memory pressure
2. **Health checks** — Review health endpoints for memlayer, mcp-manager, and qdrant containers
3. **GPU VRAM** — Near capacity; monitor if new model loads needed

---

**Overall: 🟢 HEALTHY** — No critical issues. Minor health check misconfigurations on 5 containers.


summary:
**Platform Health Council — Daily Check**
**Tuesday, February 24, 2026 — 8:30 AM UTC**

---

## 🟢 System Status: OPERATIONAL

**Uptime:** 8 days, 14 hours
**Load Average:** 7.48 / 6.87 / 6.98 (36 cores available)

---

## 📊 Core Resources

**Disk Usage:**
- **/** → 79% used (189GB free) ✅ OK
- **/mnt/storage** → 78% used (414GB free) ✅ OK

**Memory:**
- **RAM:** 73GB / 125GB used (52GB available) ✅ OK
- **Swap:** 8GB / 8GB used (100% full) ⚠ **WARNING**

**GPUs:**
- **RTX 3090 #0:** 23.6GB / 24.6GB vRAM, 0% utilization (Idle)
- **RTX 3090 #1:** 23.7GB / 24.6GB vRAM, 0% utilization (Idle)

---

## ⚙ Service Health

**OpenClaw Gateway:** ✅ RUNNING (PID 3564248)
**Docker Containers:** 67 active
**PM2 Processes:** 24 tracked

---

## 🔴 Issues Detected

### Critical
**1. Swap Memory Exhausted (100%)**
- All 8GB swap consumed
- May cause performance degradation under load
- **Action:** Monitor memory-intensive processes

**2. Unhealthy Docker Containers (5)**
- ouro-qdrant-1
- memlayer-web-ui
- memlayer-service
- mcp-manager
- hr_roofing_qdrant

### High Priority
**3. PM2 Restart Loops (7 services stopped due to excessive restarts)**
- `pasturelog-api` → 167,620 restarts
- `cfr-command-center` → 46,672 restarts
- `tmux-web` → 50,153 restarts
- `novel-os-dev` → 43,063 restarts
- `novel-os` → 22,401 restarts
- `omi-stt` → 1,075 restarts
- `omi-integration` → 7 restarts

**Recommendation:** Remove or permanently disable these failed services to reduce PM2 overhead.

---

## 📈 Trends Since Last Check (2026-02-21)

- **Disk /:** 73% → 79% (+6% in 3 days)
- **Memory:** 76GB → 73GB (improved)
- **Swap:** Still at 100% (unchanged — ongoing issue)
- **PM2 crashes:** Novel-os/tmux-web restart counts continue climbing

---

## ✅ Action Items

1. **Immediate:** Investigate swap exhaustion root cause
2. **This week:** Restart or troubleshoot 5 unhealthy Docker containers
3. **Cleanup:** Remove 7 failed PM2 services permanently

---

**Overall Assessment:** Platform i…

provider: anthropic


summary:
## 🔧 Platform Health Council — Daily Check
**Wednesday, February 25th, 2026 — 8:30 AM UTC**

---

### ✅ Overall Status: **OPERATIONAL** (with warnings)

---

### 🖥 System Overview

| Metric | Value | Status |
|--------|-------|--------|
| **Uptime** | 9 days, 14 hours | ✅ Stable |
| **Load Average** | 6.06 (36 cores) | ✅ Normal (~17% utilization) |
| **Root Disk** | 79% used (187GB free) | ⚠ Monitor |
| **Storage (/mnt)** | 78% used (414GB free) | ✅ OK |

---

### 💾 Memory Status

| Type | Used | Available | Status |
|------|------|-----------|--------|
| **RAM** | 75GB / 125GB | 50GB free | ✅ OK |
| **Swap** | 8.0GB / 8.0GB | 100KB free | 🔴 **EXHAUSTED** |

**⚠ Critical:** Swap has been at 100% for 5+ consecutive days. System is under sustained memory pressure.

---

### 🎮 GPU Status (2x RTX 3090)

| GPU | VRAM Used | VRAM Total | Temp | Utilization |
|-----|-----------|------------|------|-------------|
| GPU 0 | 22.1 GB | 24 GB | 47°C | 0% (idle) |
| GPU 1 | 17.8 GB | 24 GB | 33°C | 0% (idle) |

✅ GPUs healthy with models loaded in VRAM

---

### 🐳 Docker Containers

| Status | Count |
|--------|-------|
| Running (healthy) | 60+ |
| Up 2+ days | Most core services |
| Unhealthy | 5 (ongoing issue) |

**Healthy Core Services:** ollama, qdrant, searxng, postgres, redis, filebrowser, adguardhome, postiz

---

### 📡 OpenClaw Platform

| Component | Status |
|-----------|--------|
| **Gateway** | ✅ Running (port 18789) |
| **Config** | ✅ Valid (v2026.2.17) |
| **Cron Jobs** | ✅ 70 scheduled |
| **Active Sessions** | 2 |
| **Paired Nodes** | 2 (Desktop2025, ESP32 — both offline) |
| **Telegram** | ✅ Connected (11 accounts) |
| **Memory Backend** | ✅ QMD operational |

---

### 📊 5-Day Trend Analysis

| Metric | Feb 21 | Feb 25 | Change |
|--------|--------|--------|--------|
| Disk / | 73% | 79% | +6% ⚠ |
| Swap | 100% | 100% | No change 🔴 |
| RAM | 76GB | 75GB | -1GB ✅ |
| Uptime | 6d | 9d | +3 days ✅ |

---

### 🚨 Action Items

**Critical:**
1. **Swap …


summary:
**📊 Platform Health Council — Daily Check**
*Thursday, February 26th, 2026 — 8:30 AM UTC*

---

**🟢 SYSTEM STATUS**
- **Uptime:** 10 days, 14 hours
- **Load Average:** 9.18 (HIGH ⚠)
- **Memory:** 79GB/125GB used (63%) — 46GB available ✓
- **Swap:** 8GB/8GB used (100% ⚠ CRITICAL)
- **Disk:** 749GB/915GB used (86%) — 128GB free ⚠

---

**🔴 FAILED SERVICES (16)**
Notable failures requiring attention:
- `systemd-resolved` — DNS resolution (may cause network issues)
- `redis-server.service` — System Redis (Docker redis OK)
- `caddy.service` — Web server/proxy
- `nvidia-persistenced` — GPU persistence
- `chatterbox-gpu0/gpu1` — TTS services
- `vllm-manager` — vLLM management
- `pm2-crogers2287` — PM2 process manager

---

**🟢 DOCKER CONTAINERS (20 running)**
All containers healthy:
- inboxagent stack (4 containers) ✓
- scrypted, pgvector, pentagi ✓
- ollama, spacebot, FileBrowser ✓
- zeroclaw-hub, adguardhome ✓
- postiz stack, canna ✓

---

**🟢 SESSIONS**
2 active sessions in last 30 minutes

---

**⚠ ACTION ITEMS**
1. **Swap exhaustion** — Investigate memory hogs; consider OOM killer
2. **Disk at 86%** — Schedule cleanup (logs, old docker images)
3. **High load (9+)** — Check for runaway processes
4. **systemd-resolved failed** — Verify DNS still functional; restart if needed

---

*Summary complete. No external delivery needed.*


summary:
**Platform Health Check — Feb 27, 2026 08:30 UTC**

**Overall Status: ⚠ NEEDS ATTENTION**

---

**OpenClaw Version:**
- Current: 2026.2.17 (stable channel)
- Update available: 2026.2.26
- Recommend: `openclaw update` at your convenience

---

**Security Audit Summary:**
- 6 CRITICAL issues
- 7 WARNINGS
- 2 INFO items

**Critical Issues Requiring Action:**

1. **Host-header origin fallback enabled** — Weakens DNS rebinding protections
   - Fix: Disable `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback`

2. **Open groupPolicy with elevated tools** — 10 Telegram accounts allow open groups with elevated tools
   - Fix: Set `groupPolicy="allowlist"` for all accounts

3. **Credentials directory permissions** — `/home/crogers2287/.openclaw/credentials` is mode 775
   - Fix: `chmod 700 /home/crogers2287/.openclaw/credentials`

4. **Plugin safety concerns:**
   - `foundry-openclaw` plugin has dangerous code patterns (exec, dynamic code, crypto-mining refs)
   - `reddit-poster` skill has credential harvesting patterns
   - Fix: Review or remove these extensions

---

**Gateway Status:**
- Running: ✅ (pid 143546, systemd active)
- Dashboard: http://192.168.1.195:18789/
- 12 agents, 268 sessions
- Memory: 473 files indexed

---

**Recommended Actions:**

1. Run `openclaw update` to get latest version
2. Fix credentials permissions: `chmod 700 ~/.openclaw/credentials`
3. Review `foundry-openclaw` plugin and `reddit-poster` skill
4. Consider setting `groupPolicy="allowlist"` for Telegram accounts
5. Review and disable `dangerouslyAllowHostHeaderOriginFallback`

---

For interactive hardening, run: `openclaw security audit --fix` (OpenClaw-level fixes only) or call the healthcheck skill for guided remediation.

deliveryStatus: delivered


summary:
**Platform Health Check — Feb 28, 2026 08:39 UTC**

---

**System Status:** ✅ Healthy
- Gateway: Running (systemd, pid 3551919)
- Sessions: 325 active across 12 agents
- Memory: 481 files indexed, vector search ready
- Dashboard: http://192.168.1.195:18789/

---

**Update Status:** ⚠ Behind by 2 days
- Installed: 2026.2.17 (stable)
- Latest: 2026.2.26
- Action: `openclaw update` when ready

---

**Security Audit:** 🔴 8 Critical | 7 Warning | 2 Info

**Critical Issues Requiring Attention:**

1. **File Permissions** — Fix immediately
   - `chmod 600 ~/.openclaw/openclaw.json` (currently 664)
   - `chmod 700 ~/.openclaw/credentials` (currently 775)

2. **Host-Header Origin Fallback** — Weakens DNS rebinding protection
   - Disable `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback`
   - Configure explicit `gateway.controlUi.allowedOrigins`

3. **Open Group Policy + Elevated Tools** — All 10 Telegram accounts use `groupPolicy="open"` with elevated tools enabled, creating prompt injection risk
   - Recommend: Set `groupPolicy="allowlist"` for sensitive rooms

4. **Small Model Without Sandbox** — `mark-twain` uses qwen3.5-35b-a3b with web tools enabled but no sandbox
   - Either enable sandboxing or disable web tools for small models

5. **Suspicious Code Patterns Detected:**
   - Plugin `foundry-openclaw`: 3 critical issues (exec, dynamic code, crypto reference)
   - Skill `reddit-poster` in cannadeals-marketing: 2 env-harvesting patterns
   - Action: Review code before trusting, or remove if unused

**Warnings:**
- No auth rate limiting configured (brute-force risk)
- Gateway password stored in config (prefer env var)
- Plugin installs unpinned and missing integrity hashes

---

**Recommendations:**
1. Fix file permissions immediately (2 commands)
2. Review and update openclaw (2-day security patches likely)
3. Review plugin/skill code or remove if untrusted
4. Consider tightening groupPolicy for production agents
5. Add auth rate limiting: `gateway.auth.rate…


status: error

error: Connection error.

summary: Connection error.

deliveryStatus: not-delivered

deliveryError: Connection error.


summary:
---

## Platform Health Check — March 2, 2026 08:30 UTC

### ✅ OpenClaw Gateway
- **Status**: Running (pid 640166, systemd enabled)
- **Version**: 2026.2.17 → **Update available: 2026.3.1**
- **Agents**: 12 active (grant, maya, magoo, clinker, ash, cardone, selena, carl, mark-twain, ghc-marketing, cannadeals-marketing, ceo)
- **Sessions**: 391 active
- **Memory**: 521 files, vector backend ready
- **Channels**: Telegram (9 bots configured, all probing OK), Email (configured)

---

### ⚠ Security Audit (7 CRITICAL, 7 WARN)

| Priority | Issue | Fix |
|----------|-------|-----|
| CRITICAL | Host-header origin fallback enabled | Disable `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback` |
| CRITICAL | Small model (qwen3.5-35b) with web tools, no sandbox | Enable sandboxing or disable web tools for mark-twain |
| CRITICAL | Open groupPolicy on all Telegram accounts | Set `groupPolicy="allowlist"` for production |
| CRITICAL | Credentials dir writable by others | `chmod 700 ~/.openclaw/credentials` |
| CRITICAL | Plugin "foundry-openclaw" dangerous code patterns | Review source before trusting |
| CRITICAL | Skill "reddit-poster" env-harvesting patterns | Review source before trusting |
| WARN | No auth rate limiting | Configure `gateway.auth.rateLimit` |
| WARN | Gateway password in config file | Use `OPENCLAW_GATEWAY_PASSWORD` env var |

---

### 📊 System Resources

| Metric | Value | Status |
|--------|-------|--------|
| Disk | 767G / 915G (88%) | ⚠ 110G free |
| RAM | 28Gi / 125Gi | ✅ 96Gi available |
| Swap | 7.4Gi / 8Gi | 🔴 **93% used** |
| Load | 9.24 | ⚠ Elevated (18-core system) |
| Uptime | 15h 28m | ✅ |

---

### 🐳 Docker Services

**Running Healthy**: ollama, pgvector, scrypted, uvin-server, companycam_*, spacebot, FileBrowser, zeroclaw-hub

**Unhealthy**: `uvin-asterisk` — investigate

---

### 📋 Recommended Actions

1. **Update OpenClaw**: `openclaw update` (2026.3.1 available)
2. **Fix permissions**: `chmod 700 ~/.openclaw/credentials`
3.…


summary:
## Platform Health Check — March 3, 2026 (08:30 UTC)

**Host:** fred (Ubuntu 24.04.2 LTS, kernel 6.8.0-101-generic)

---

### OpenClaw Security Status

| Severity | Count |
|----------|-------|
| CRITICAL | 7 |
| WARN | 7 |
| INFO | 2 |

**Critical Issues:**
1. **Host-header origin fallback enabled** — DNS rebinding protections weakened
2. **Small model (qwen3.5-35b) with web tools + no sandbox** — `mark-twain` agent exposed to untrusted inputs
3. **Open groupPolicy + elevated tools** — 10 Telegram accounts allow prompt injection → high-impact commands
4. **Open groupPolicy + runtime/filesystem tools** — All agents have unsandboxed exec/read/write
5. **Credentials dir world-writable** — `/home/crogers2287/.openclaw/credentials` mode 775
6. **Plugin "foundry-openclaw"** — Dangerous code patterns (exec, crypto-mining refs)
7. **Skill "reddit-poster"** — Env-harvesting patterns detected

---

### OpenClaw Version

- Channel: **stable**
- Status: **Update available** (2026.3.2)
- Fix: `openclaw update`

---

### Network Exposure

- **Firewall:** None detected (no ufw/firewalld active)
- **Notable open ports:**
  - 80 (HTTP), 443 (HTTPS) — bound to tailscale IP
  - 445/139 (SMB) — file sharing exposed
  - 25 (SMTP) — mail server
  - 2222 (SSH alt)
  - 18789 (OpenClaw gateway) — public listener
  - Multiple Node/Python apps on high ports

---

### Recommendations

1. **Immediate:** `chmod 700 ~/.openclaw/credentials`
2. **Immediate:** Review `foundry-openclaw` plugin and `reddit-poster` skill for trust
3. **High:** Set `groupPolicy="allowlist"` for Telegram accounts handling untrusted input
4. **High:** Enable sandboxing (`agents.defaults.sandbox.mode="all"`) or disable web tools for small models
5. **High:** Disable `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback`
6. **Medium:** Enable UFW with deny-inbound default
7. **Medium:** Run `openclaw update` to apply 2026.3.2

---

**Trust Model:** Personal assistant (single trusted operator) — but current config ex…


summary:
**Platform Health Council — Daily Check**
*Wednesday, March 4, 2026 — 8:32 AM UTC*

---

**GATEWAY STATUS:** ✅ Running (pid 3234, systemd enabled)
- Dashboard: http://192.168.1.195:18789/
- 12 agents active, 507 sessions, memory system operational
- Last default grant: 12 minutes ago

**UPDATE AVAILABLE:** OpenClaw 2026.3.2 (current: 2026.2.17)

---

**SECURITY AUDIT: 5 CRITICAL | 7 WARNINGS**

🔴 **CRITICAL ISSUES:**

1. **Host-header origin fallback enabled** — Weakens DNS rebinding protections
   - Fix: Disable `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback`

2. **Small model with web tools exposed** (mark-twain uses qwen3.5-35b)
   - Sandbox=off with web_search, web_fetch, browser enabled
   - Fix: Enable sandboxing or disable web tools for small models

3. **Open groupPolicy with elevated tools** (10 Telegram accounts)
   - Prompt injection in open groups could trigger high-impact actions
   - Fix: Set `groupPolicy="allowlist"`

4. **Open groupPolicy with runtime/filesystem tools**
   - Same exposure — exec/process/read/write/edit available in open groups
   - Fix: Restrict tools or sandbox

5. **Credentials dir writable by others**
   - `/home/crogers2287/.openclaw/credentials` mode 775
   - Fix: `chmod 700 ~/.openclaw/credentials`

⚠ **WARNINGS:**
- Auth rate limiting not configured
- Gateway password in config file (prefer env var)
- Plugin unpinned (foundry-openclaw)
- Plugin missing integrity hash

---

**RECOMMENDED ACTIONS:**

1. **Immediate:** `chmod 700 ~/.openclaw/credentials`
2. **High:** Disable `dangerouslyAllowHostHeaderOriginFallback`
3. **High:** Set Telegram accounts to `groupPolicy="allowlist"` or sandbox agents
4. **Routine:** `openclaw update` to install 2026.3.2

---

**CHANNELS:** Telegram (WARN - open groups), Email (OK)
**SESSIONS:** 507 active, default model glm-5

Run `openclaw security audit --fix` to apply safe defaults, or consult the healthcheck skill for guided hardening.


summary:
## Platform Health Check — 08:30 UTC (March 5, 2026)

### Overall Status: ⚠ ATTENTION REQUIRED

**OpenClaw Version:** 2026.2.17 → **2026.3.2 available** (`openclaw update`)

---

### Security Audit: 7 Critical · 7 Warnings

| Priority | Issue | Fix |
|----------|-------|-----|
| 🔴 | Credentials dir world-writable | `chmod 700 ~/.openclaw/credentials` |
| 🔴 | Host-header origin fallback enabled | Disable `dangerouslyAllowHostHeaderOriginFallback` |
| 🔴 | Open groupPolicy with elevated tools | Set `groupPolicy="allowlist"` on Telegram accounts |
| 🔴 | Plugin "foundry-openclaw" — dangerous patterns | Review source or remove |
| 🔴 | Skill "reddit-poster" — credential harvesting risk | Review source or remove |
| 🟡 | No auth rate limiting | Configure `gateway.auth.rateLimit` |
| 🟡 | Gateway password in config file | Use `OPENCLAW_GATEWAY_PASSWORD` env var |

---

### Host Posture
- **Firewall (UFW):** Active ✓
- **Gateway:** Running (pid 1979488, loopback) ✓
- **Sessions:** 528 active across 12 agents
- **Tailscale:** OFF
- **Dashboard:** LAN-accessible at 192.168.1.195:18789

---

### Immediate Actions
1. Fix credentials permissions: `chmod 700 ~/.openclaw/credentials`
2. Update: `openclaw update`
3. Review flagged plugin/skill before next use
4. Consider sandboxing for agents with small models + web tools

---

Logged to `memory/2026-03-05.md`


summary:
## Platform Health Check - March 6, 2026 8:30 AM UTC

### System Overview
**Host:** fred (Linux 6.8.0-101-generic, Ubuntu x64)
**OpenClaw:** v2026.2.17, update available (2026.3.2)
**Gateway:** Running on 0.0.0.0:18789 (also LAN 192.168.1.195)
**Agents:** 12 active (549 sessions total)

---

### 🔴 Critical Security Issues (8)

1. **Host-Header Origin Fallback Enabled**
   Weakens DNS rebinding protections. Disable and configure explicit allowed origins.

2. **Small Model (qwen3.5-35b) Without Restrictions**
   Running without sandbox or web tool restrictions. Risk: unsafe for untrusted inputs.

3. **Open Telegram Groups with Elevated Tools**
   All 9 agents configured with `groupPolicy="open"` + runtime/filesystem tools exposed.
   Risk: prompt injection → command execution / file access.

4. **Credentials Directory World-Writable**
   `/home/crogers2287/.openclaw/credentials` mode 775. Fix: `chmod 700`

5. **Dangerous Plugins Detected**
   - `foundry-openclaw`: dynamic code execution, crypto-mining patterns
   - `openclaw-better-gateway`: env harvesting, dynamic code execution

6. **Dangerous Skill: reddit-poster**
   Environment variable access + network send patterns in cannadeals-marketing agent.

---

### ⚠ Warnings (7)

- Auth rate limiting not configured (brute-force vulnerable)
- Gateway password stored in config (prefer env var)
- Multi-user heuristic triggered (multiple open groups + runtime tools)
- Plugin tools reachable under permissive policy
- Unpinned plugin installs
- Missing plugin integrity metadata

---

### 🌐 Network Exposure

- **Firewall:** No active firewall (iptables default ACCEPT, no filtering rules)
- **Listening Ports:** 80+ services exposed, including:
  - OpenClaw gateway: 18789 (all interfaces)
  - SSH alternate: 2222
  - SMB: 445, 139
  - Multiple web services: 80, 3001, 3004, 3333, 3434, 5173, 5174, 8080, etc.
  - Development servers, databases, and admin interfaces

---

### ✅ Positive Findings

- Unatten…


summary:
## Platform Health Check — March 7, 2026 (08:30 UTC)

**Host:** fred (Ubuntu 24.04.2 LTS, Kernel 6.8.0-101-generic)
**OpenClaw Channel:** stable
**Update Available:** Yes — npm 2026.3.2

---

### Security Audit Summary

| Severity | Count |
|----------|-------|
| Critical | 8 |
| Warning | 7 |
| Info | 2 |

---

### Critical Issues

1. **Host-header origin fallback enabled** — `gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true` weakens DNS rebinding protection. Fix: Disable and configure explicit `allowedOrigins`.

2. **Small model with web tools unsandboxed** — `local/qwen3.5-35b-a3b` has `web_search`, `web_fetch`, `browser` enabled without sandbox. Fix: Enable sandboxing and restrict web tools.

3. **Open group policy with elevated tools** — 10 Telegram accounts use `groupPolicy="open"` with elevated tools enabled. Risk: prompt injection → high-impact actions. Fix: Set `groupPolicy="allowlist"`.

4. **Open group policy with runtime/fs tools** — Same 10 accounts expose `exec`, `process`, `read`, `write`, `edit` without sandbox. Fix: Restrict tools or enable sandboxing.

5. **Credentials dir writable by others** — `/home/crogers2287/.openclaw/credentials` mode 775. Fix: `chmod 700`.

6. **Plugin "foundry-openclaw" dangerous patterns** — Shell exec, dynamic code exec, possible crypto-mining reference detected. Review before use.

7. **Plugin "openclaw-better-gateway" dangerous patterns** — Dynamic code exec, possible env harvesting. Review before use.

8. **Skill "reddit-poster" dangerous patterns** — Env harvesting detected. Review before use.

---

### Warnings

- Insecure config flag: `dangerouslyAllowHostHeaderOriginFallback=true`
- No auth rate limiting configured (brute-force not mitigated)
- Gateway password stored in config, not env var
- Multi-user heuristic detected with runtime tools exposed
- Plugin tools reachable under permissive policy
- Unpinned npm specs for `foundry-openclaw`
- Plugin installs missing integrity hashes

---

### Network…