How do I install the Cf Tunnel Deploy skill?

Run npx skillmds@latest add tangchunwu/cf-tunnel-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cf Tunnel Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cf Tunnel Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cf Tunnel Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cf Tunnel Deploy?

tangchunwu (@tangchunwu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cf Tunnel Deploy by tangchunwu — Agent Skill

Name: Cf Tunnel Deploy
Rating: 4.2 (5 reviews)
Author: tangchunwu

Cf Tunnel Deploy

Deploy local services to public internet via Cloudflare Tunnel with custom domain. Use when user wants to expose local Docker service to public, set up Cloudflare tunnel, configure cloudflared, or make local service accessible via custom domain. Handles DNS pollution issues, SSL configuration, and Docker Compose integration.

tangchunwu Updated Aug 19, 2026 1 repo stars

File contents

Cloudflare Tunnel Deploy

Deploy local services to public internet using Cloudflare Tunnel with custom domain.

Prerequisites

Cloudflare account with a domain
Docker installed
cloudflared CLI installed locally

Quick Start Workflow

1. Login to Cloudflare (one-time)

cloudflared tunnel login

This creates ~/.cloudflared/cert.pem.

2. Create Named Tunnel

cloudflared tunnel create <tunnel-name>

This creates credentials file: ~/.cloudflared/<tunnel-id>.json

3. Create Tunnel Config

Create ~/.cloudflared/config-<service>.yml:

tunnel: <tunnel-id>
credentials-file: /etc/cloudflared/<tunnel-id>.json
protocol: http2

ingress:
  - hostname: <subdomain>.<domain>
    service: http://host.docker.internal:<port>
    originRequest:
      connectTimeout: 180s
      noTLSVerify: true
  - service: http_status:404

4. Add DNS Route

cloudflared tunnel route dns -f <tunnel-id> <subdomain>.<domain>

5. Configure Cloudflare SSL (CRITICAL)

In Cloudflare Dashboard: SSL/TLS -> Overview -> Set to Flexible (not Full).

6. Add to Docker Compose

See references/docker-compose.md for template.

Common Issues & Solutions

See references/troubleshooting.md for:

DNS pollution (198.18.x.x fake IPs)
TLS handshake errors
404 from Cloudflare
host.docker.internal not accessible

Verification

# Check tunnel status
cloudflared tunnel list
cloudflared tunnel info <tunnel-name>

# Test via proxy (if DNS polluted locally)
curl -x http://127.0.0.1:<proxy-port> https://<subdomain>.<domain>/health

---name: cf-tunnel-deploydescription: Deploy local services to public internet via Cloudflare Tunnel with custom domain. Use when user wants to expose local Docker service to public, set up Cloudflare tunnel, configure cloudflared, or make local service accessible via custom domain. Handles DNS pollution issues, SSL configuration, and Docker Compose integration.---# Cloudflare Tunnel DeployDeploy local services to public internet using Cloudflare Tunnel with custom domain.## Prerequisites- Cloudflare account with a domain- Docker installed- `cloudflared` CLI installed locally## Quick Start Workflow### 1. Login to Cloudflare (one-time)```bashcloudflared tunnel login```This creates `~/.cloudflared/cert.pem`.### 2. Create Named Tunnel```bashcloudflared tunnel create <tunnel-name>```This creates credentials file: `~/.cloudflared/<tunnel-id>.json`### 3. Create Tunnel ConfigCreate `~/.cloudflared/config-<service>.yml`:```yamltunnel: <tunnel-id>credentials-file: /etc/cloudflared/<tunnel-id>.jsonprotocol: http2ingress: - hostname: <subdomain>.<domain> service: http://host.docker.internal:<port> originRequest: connectTimeout: 180s noTLSVerify: true - service: http_status:404```### 4. Add DNS Route```bashcloudflared tunnel route dns -f <tunnel-id> <subdomain>.<domain>```### 5. Configure Cloudflare SSL (CRITICAL)In Cloudflare Dashboard: `SSL/TLS` -> `Overview` -> Set to **Flexible** (not Full).### 6. Add to Docker ComposeSee [references/docker-compose.md](references/docker-compose.md) for template.## Common Issues & SolutionsSee [references/troubleshooting.md](references/troubleshooting.md) for:- DNS pollution (198.18.x.x fake IPs)- TLS handshake errors- 404 from Cloudflare- host.docker.internal not accessible## Verification```bash# Check tunnel statuscloudflared tunnel listcloudflared tunnel info <tunnel-name># Test via proxy (if DNS polluted locally)curl -x http://127.0.0.1:<proxy-port> https://<subdomain>.<domain>/health```

Frequently asked questions