Invert OpenClaw port 18789 check: green when blocked, red when accessible

[Copilot]

Upptime has no native support for inverted TCP checks — it marks a port as "up" (green) when reachable and "down" (red) when not. For port 18789, the desired logic is the opposite: blocked = good (green), accessible = security breach (red).

Keeping the entry in .upptimerc.yml with tcp:// would permanently show red (firewall correctly blocks it) and generate misleading GitHub Issues.

Changes

• .upptimerc.yml — Remove OpenClaw firewall (port 18789) entry to prevent Upptime's uptime workflow from interfering with the inverted check.

• .github/workflows/openclaw-firewall-port-18789.yml (new, not Upptime-managed) — Custom daily workflow at 00:15 UTC applying inverted logic via nc:

  • Port blocked → writes status: up (green) + closes any open security issue
  • Port accessible → writes status: down (red) + opens a GitHub Issue: "🚨 OpenClaw port 18789 is accessible — firewall may be down"

• history/open-claw-firewall-port-18789.yml — Set to status: up to reflect the correct current state (port is blocked = firewall working).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• upptime.js.org
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.