LaunchKit · 2026
Back to Skills

caddy-reverse-proxy

Add, manage, and troubleshoot Caddy reverse proxy routes for local apps via wildcard subdomains.

0
0 downloads
by @brennerspear

Setup & Installation

openclaw skills install @brennerspear/caddy-reverse-proxy

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install caddy-reverse-proxy

What This Skill Does

Routes *.YOUR_DOMAIN wildcard subdomains to local services via Caddy reverse proxy with automatic Let's Encrypt HTTPS certificates. Access is limited to Tailscale, keeping services off the public internet. Supports macOS (LaunchDaemon) and Linux (systemd).

Manages wildcard TLS certs and subdomain routing in a single Caddyfile without exposing services publicly.

When to use it

  • Serving a local web app at a named HTTPS subdomain
  • Adding a new self-hosted tool to a private Tailscale network
  • Reloading Caddy routing config without a full service restart
  • Diagnosing cert failures after a Vercel API token expires
  • Spinning up a dev server with automatic subdomain and TLS

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Add a reverse proxy for my local app running on port 3100

AGENT
  1. 1Creates a background service definition (LaunchAgent or systemd unit) for the app
  2. 2Adds a Caddyfile block for appname.YOUR_DOMAIN pointing to localhost:3100
  3. 3Appends a dashboard HTML entry for the new subdomain
  4. 4Reloads Caddy config via the admin API
  5. 5Confirms TLS cert provisioned after the 30-60 second DNS-01 challenge
OUTPUT

App is accessible at https://appname.YOUR_DOMAIN over Tailscale with a valid TLS certificate

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

Caddy installed with the caddy-dns/vercel pluginTailscale account with Tailscale running on the hostVercel account with a domain managed by Vercel DNSVercel API token with DNS edit permissions