caddy

Configure Caddy as an HTTPS reverse proxy with DNS-01 wildcard certificates.

1|Updated Apr 15, 2026

Search Tags:#tls #https #reverse-proxy #web-server #caddy #dns-01

Ready to run

npx skills add https://github.com/MysticRyuujin/spirens --skill caddy-mysticryuujin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: caddy
Source: https://github.com/MysticRyuujin/spirens/tree/main/caddy
Command: npx skills add https://github.com/MysticRyuujin/spirens --skill caddy-mysticryuujin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying web services with automatic HTTPS can be complex and error-prone; Caddy provides a straightforward, secure reverse-proxy solution that auto-manages TLS and supports wildcard certificates via DNS-01.

Core Features & Use Cases

Automatic TLS management for HTTP services with simple Caddyfile configuration.
DNS-01 wildcard support enabling multi-host deployments behind a single domain.
Matcher-based routing and simple reverse_proxy patterns for flexible service composition.

Quick Start

Launch a basic Caddy-based gateway by writing a Caddyfile and starting the Caddy server to serve your first site.

Frequently Asked Questions about caddy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up an automatic HTTPS reverse proxy?▼

To set up an automatic HTTPS reverse proxy, configure Caddy using a Caddyfile. Caddy automatically manages TLS certificates and routes traffic to backend services with simple reverse_proxy directives.

How does Caddy handle wildcard certificates?▼

Caddy handles wildcard certificates using the DNS-01 challenge. This mechanism allows multi-host deployments behind a single domain to be secured automatically without requiring individual certificate requests for each subdomain.

Can I implement flexible routing patterns with a reverse proxy?▼

Yes, you can implement flexible routing patterns with a reverse proxy by using matchers in your Caddyfile. Matchers allow you to define specific conditions and route requests to different backend services based on those patterns.

What are the risks of on-demand TLS in a web server?▼

The risk of on-demand TLS in a web server is potential abuse if not properly secured. On-demand TLS allows the server to obtain certificates automatically for arbitrary hostnames on-the-fly, which requires strict configuration to prevent unauthorized certificate issuance.

Do I need a specific DNS provider to use DNS-01 for automatic HTTPS?▼

To use DNS-01 for automatic HTTPS with wildcard certificates, you need a supported DNS provider. Caddy requires configuring the appropriate DNS challenge plugin so it can programmatically create the TXT records needed to validate domain ownership.

What is the best way to manage TLS for multi-host deployments?▼

The best way to manage TLS for multi-host deployments is using a reverse proxy that supports automatic DNS-01 wildcard certificates. This approach secures all subdomains behind a single certificate managed automatically via a Caddyfile.