Dbochman/openclaw-ssrf-localhost-plugins
.claude/skills/openclaw-ssrf-localhost-plugins/SKILL.md
Fix OpenClaw SSRF guard blocking channel plugins (BlueBubbles, etc.) from reaching localhost or private/LAN IP servers. Use when: (1) gateway.err.log shows "blocked URL fetch (bluebubbles-api) reason=Blocked hostname or private/internal/special-use IP address", (2) `openclaw health` reports BlueBubbles as "failed (unknown)", (3) after upgrading OpenClaw to 2026.3.28+ or 2026.4.x. The SSRF guard doesn't distinguish between agent-initiated web_fetch and plugin internal HTTP calls.
$ install --global
skillsauthnpx skillsauth add Dbochman/dotfiles openclaw-ssrf-localhost-pluginsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 1:49 AM4.8s1 file scanned
SKILL.md
- name:
- openclaw-ssrf-localhost-plugins
- description:
- |
- localhost or private/LAN IP servers. Use when:
- (1) gateway.err.log shows "blocked URL
- author:
- Claude Code
- version:
- 1.0.0
- date:
- 2026-04-05
OpenClaw SSRF Guard Blocks Localhost Channel Plugins
Problem
OpenClaw 2026.3.28 introduced SSRF protection that blocks all HTTP requests to localhost, 127.0.0.1, private IPs (10.x, 172.16-31.x, 192.168.x), and other special-use addresses. This affects channel plugin internal API calls (BlueBubbles, Home Assistant, local LLM servers, etc.) even though those URLs are admin-configured in openclaw.json, not user-controllable.
Context / Trigger Conditions
- Upgraded OpenClaw to 2026.3.28 or later
- Channel plugin (e.g., BlueBubbles) uses a localhost or LAN server URL
gateway.err.logshows:[security] blocked URL fetch (bluebubbles-api) target=http://localhost:1234/api/v1/ping reason=Blocked hostname or private/internal/special-use IP addressopenclaw healthreports the channel as failed- Actual messaging may still partially work (webhooks inbound work, but outbound pings/health checks and some API calls are blocked)
Solution
Add "allowPrivateNetwork": true to the channel config in openclaw.json:
{
"channels": {
"bluebubbles": {
"enabled": true,
"serverUrl": "http://localhost:1234",
"allowPrivateNetwork": true,
...
}
}
}
This is a per-channel setting that exempts that channel's internal HTTP client from
the SSRF guard. It does NOT affect agent-initiated web_fetch or browser tool calls.
Verification
- Restart gateway:
launchctl kickstart -k gui/$(id -u)/ai.openclaw.gateway - Check
gateway.log— should showBlueBubbles server macOS X.XandBlueBubbles Private API enabled(successful connection) - Check
gateway.err.log— no more "blocked URL fetch" lines after restart - Run
openclaw health— should showBlueBubbles: ok
Notes
- This affects ANY self-hosted integration on localhost/LAN, not just BlueBubbles
- The config key is
allowPrivateNetwork(camelCase), validated in the channel schema - See openclaw/openclaw#57181 and openclaw/openclaw#60715 for upstream discussion
- A broader fix (exempting all plugin internal HTTP from SSRF) is tracked upstream but not yet shipped as of 2026.4.2
References
- openclaw/openclaw#57181 — SSRF guard blocks BlueBubbles plugin internal API calls
- openclaw/openclaw#60715 — BlueBubbles health check fails on LAN/private serverUrl
Related Skills
Dbochman/reolink-camera
tools
VerifiedTrustedCommunity
Use exact configured Reolink cameras through the local Home Hub for availability and power status, fresh stills, visual commentary, protected Dylan/Julia/household sharing, and reversible spotlight control. Supports trusted owner tasks and explicitly scoped proactive automations; not for Nest or Ring cameras, arbitrary recipients, recordings, account changes, or raw camera APIs.
2SKILL.mdUpdated Jul 28, 2026
Dbochman/plant-tracker
data-ai
VerifiedTrustedCommunity
Privately manage Dylan and Julia's household plant inventory and care history by physical location, bed, and exact Flower Cam view. Use for confirmed plant onboarding from camera conversations, camera- or bed-filtered inventory, record corrections, individual or whole-bed care, and private filtered exports. Pair with reolink-camera when an owner asks about plants visible in Flower Cam images.
2SKILL.mdUpdated Jul 28, 2026
Dbochman/reachy-control
testing
VerifiedTrustedCommunity
Inspect and control the physically secured Reachy Mini at Crosstown through ClawBody. Use for requests to check Reachy, look around, express an emotion, play any official emotion or dance preset, speak proactively, mute or unmute its microphone, stop movement, or describe what its camera sees.
2SKILL.mdUpdated Jul 16, 2026
Dbochman/reachy-continuity
tools
VerifiedTrustedCommunity
Handle Reachy/iMessage handoffs, selective durable memory, forgetting, and diagnostics; automatic context comes from the gateway plugin.
2SKILL.mdUpdated Jul 16, 2026