部署Caddy进行反向代理
1. 背景
我一直使用Nginx来进行APP的反向代理。所有的APP都是容器。我部署了不到10个APP,也不经常更换。但是我使用的是掩码证书,没有官方的acme.sh的DNSPod插件。有社区版的插件,但是我折腾了一下,并没有成功。所以我一直是使用DNS-01的方式来更新证书,每次都需要到DNS的后台更新TXT的Record。最后我决定使用Caddy为每一个APP申请一个证书,这样就可以使用HTTP-01的方式来验证了,只需要80和443端口可达。
2. Caddy部署的文件结构和内容
2.1 文件结构
1-rw-r--r-- 1 root root 3276 Sep 22 15:27 Caddyfile2drwxr-xr-x 2 root root 4096 Sep 22 15:26 conf.d/3drwx------ 3 root root 4096 Sep 22 14:29 config/4drwx------ 3 root root 4096 Sep 22 14:29 data/5-rw-rw-r-- 1 root root 755 Sep 22 11:01 docker-compose.yml6drwxr-x--- 2 root root 4096 Sep 22 15:28 logs/%%{init: {
'theme': 'base',
'themeVariables': {
'fontFamily': 'Arial, sans-serif',
'fontSize': '13px',
'primaryTextColor': '#2C3E50',
'edgeLabelBackground': '#EEEEEE'
},
'flowchart': {
'htmlLabels': true,
'curve': 'basis',
'nodeSpacing': 50,
'rankSpacing': 60
}
}}%%
flowchart TB
%% Top Container Subgraph
subgraph Container ["Docker Container"]
CADDY["<b>Caddy Server Process</b>"]
end
%% Host Filesystem Subgraph
subgraph Host ["Host Filesystem"]
subgraph ConfigInputs ["Configuration (User Managed)"]
CF["<b>Caddyfile</b><br/>(Main Config)"]
CONFD["<b>conf.d/</b><br/>(Modular Site Configs)"]
end
subgraph RuntimeOutputs ["Runtime Data & Storage (Caddy Managed)"]
DATA["<b>data/</b><br/>(SSL/TLS Certs & Keys)"]
CONFIG["<b>config/</b><br/>(Autosaved Active State)"]
LOGS["<b>logs/</b><br/>(Access & Error Logs)"]
end
DC["<b>docker-compose.yml</b><br/>(Defines Service & Mounts)"]
end
%% Internal Subgraph Connections
CF -->|Imports rules from| CONFD
%% Orchestration & Mount Connections
DC -->|Deploys & Configures| CADDY
CF -.->|Mount: /etc/caddy/Caddyfile| CADDY
CONFD -.->|Mount: /etc/caddy/conf.d/| CADDY
%% Output & Storage Connections
CADDY -->|Writes Certs & Keys to /data| DATA
CADDY -->|Saves Active Config to /config| CONFIG
CADDY -->|Outputs Logs to /var/log/caddy| LOGS
%% ==========================================
%% Styling & Color Palettes
%% ==========================================
classDef default fill:#FFFFFF,stroke:#2C3E50,stroke-width:1.5px,color:#2C3E50;
style Container fill:#E1F5FE,stroke:#4FC3F7,stroke-width:2px,color:#0288D1
style Host fill:#FAF4FB,stroke:#CE93D8,stroke-width:2px,color:#6A1B9A
style ConfigInputs fill:#E8F5E9,stroke:#81C784,stroke-width:2px,color:#2E7D32
style RuntimeOutputs fill:#FFF3E0,stroke:#FFB74D,stroke-width:2px,color:#EF6C002.2 Docker Compose文件
1services:2 caddy:3 image: caddy:2.10-alpine4 container_name: caddy5 restart: unless-stopped6 7 ports:8 - "80:80"9 - "443:443"10 - "443:443/udp"11 12 environment:13 TZ: Asia/Shanghai14 ACME_EMAIL: brain_07@163.com15 16 volumes:17 - ./Caddyfile:/etc/caddy/Caddyfile:ro18 - ./conf.d:/etc/caddy/conf.d:ro19 - ./data:/data20 - ./config:/config21 - ./logs:/var/log/caddy22 23 networks:24 - proxynet25 26 healthcheck:27 test: ["CMD", "caddy", "version"]28 interval: 30s29 timeout: 5s30 retries: 331 32 logging:33 driver: json-file34 options:35 max-size: "10m"36 max-file: "3"37 38 security_opt:39 - no-new-privileges:true40 41networks:42 proxynet:43 external: true2.3 Caddyfile文件
Caddyfile是主的配置文件,它也会引入所conf.d/*.caddy 。
1{2 # ── ACME / certificates ───────────────────────────────────────────────3 email {$ACME_EMAIL}4 5 # Uncomment ONLY while testing. Staging certs are untrusted by browsers6 # but have far higher rate limits. Switch back by re-commenting and7 # deleting /srv/caddy/data/caddy/certificates/acme-staging-*8 # acme_ca https://acme-staging-v02.api.letsencrypt.org/directory9 10 # ── Server behaviour ──────────────────────────────────────────────────11 grace_period 10s # drain in-flight requests on reload/stop12 13 # Leave the admin API at its default (127.0.0.1:2019, container-internal).14 # `caddy reload` depends on it. Do NOT add `admin off`.15 16 # ── Only if something sits IN FRONT of Caddy ──────────────────────────17 # Cloudflare proxy, an L4 load balancer, another reverse proxy, etc.18 # If Caddy is the internet-facing edge (your case), leave this commented:19 # an attacker could otherwise spoof client IPs via X-Forwarded-For.20 # servers {21 # trusted_proxies static private_ranges22 # }23}24 25# ═══════════════════════════════════════════════════════════════════════════26# SNIPPETS — must be defined before the import that uses them27# ═══════════════════════════════════════════════════════════════════════════28 29# Per-app access log. Usage: import logs app130(logs) {31 log {32 output file /var/log/caddy/{args[0]}.access.log {33 roll_size 10MiB34 roll_keep 535 roll_keep_for 720h36 }37 format json38 level INFO39 }40}41 42# Baseline response headers. Usage: import hardening43(hardening) {44 header {45 Strict-Transport-Security "max-age=31536000; includeSubDomains"46 X-Content-Type-Options "nosniff"47 X-Frame-Options "SAMEORIGIN"48 Referrer-Policy "strict-origin-when-cross-origin"49 -Server50 }51}52 53# Headers passed UPSTREAM to the app. Usage inside reverse_proxy:54# import proxy_headers55(proxy_headers) {56 header_up Host {host}57 header_up X-Real-IP {remote_host}58 header_up X-Forwarded-For {remote_host}59 header_up X-Forwarded-Proto {scheme}60 header_up X-Forwarded-Host {host}61}62 63# Compression. Usage: import compress64(compress) {65 encode zstd gzip66}67 68# ═══════════════════════════════════════════════════════════════════════════69# SITES — one file per app in conf.d/70# Each site block = one hostname = one independent certificate.71# ═══════════════════════════════════════════════════════════════════════════72 73import /etc/caddy/conf.d/*.caddy2.4 子配置文件
具体的配置文件在conf.d文件夹下,后缀.caddy 。因为一部分配置在主配置文件里已经定义了,子配置文件只需要引入相应的配置块就可以了。
1panda.zenseek.site {2 import logs pandablog3 import hardening4 import compress5 6 reverse_proxy pandablog-app:3000 {7 transport http {8 read_timeout 86400s9 }10 }11}2.5 其他文件
data文件夹存储TLS证书和acme验证相关的文件。config文件夹存储自动保存的配置,更改的API状态以及一些内部的运行时设置。
3. Caddy部署
3.1 Staging阶段
Let's Encrypt有额度的限制。所以在部署的时候,为了防止重复申请证书,可以更改Caddyfile里的内容。去# acme_ca https://acme-staging-v02.api.letsencrypt.org/directory 的注释,再启动容器。这时申请的就是Staging的证书,它的额度很高。
1ubuntu@VM-0-6-ubuntu:~/container/caddy$ echo | openssl s_client -connect link.zenseek.site:443 -servername link.zenseek.site 2>/dev/null | openssl x509 -noout -subject -issuer -dates2 3subject=CN = link.zenseek.site4issuer=C = US, O = Let's Encrypt, CN = (STAGING) Baloney Bulgur YE25notBefore=Sep 22 05:31:11 2026 GMT6notAfter=Dec 21 05:31:10 2026 GMT当确认容器里没有额外的报错,证书也可以正常显示。可以将Caddyfile再改回# acme_ca https://acme-staging-v02.api.letsencrypt.org/directory 。因为更改了配置文件,所以需要重新验证一下配置文件的有效性。输出是一堆的log,注意里面有Valid configuration的字样就可以了。然后再重新加载配置。
1sudo docker exec -w /etc/caddy caddy caddy validate --config /etc/caddy/Caddyfile2......3Valid configuration4......5 6sudo docker exec -w /etc/caddy caddy caddy reload --config /etc/caddy/Caddyfile但是我这么做了之后,重新拿到的配置文件依然是Staging的证书,或许是之前Staging的证书没有被替换。我在docker compose down再up之后,才收到了新的证书。
3.2 生产环境
首先确认容器是UP并且状态是healthy。
查看证书是有效的。
Curl查看Header状态。
1ubuntu@VM-0-6-ubuntu:~/container/caddy$ docker compose up -d2[+] up 7/73 ✔ Image caddy:2.10-alpine Pulled 4.1s4 ✔ Container caddy Started5 6ubuntu@VM-0-6-ubuntu:~/container/caddy$ docker ps | grep caddy7ce34210a4a41 caddy:2.10-alpine "caddy run --config …" 38 seconds ago Up 37 seconds (healthy) 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp, 0.0.0.0:443->443/udp, [::]:443->443/udp, 2019/tcp caddy8 9ubuntu@VM-0-6-ubuntu:~/container/caddy$ 10echo | openssl s_client -connect link.zenseek.site:443 -servername link.zenseek.site 2>/dev/null | openssl x509 -noout -subject -issuer -dates11 12subject=CN = link.zenseek.site13issuer=C = US, O = Let's Encrypt, CN = YE214notBefore=Sep 22 06:33:56 2026 GMT15notAfter=Dec 21 06:33:55 2026 GMT1617ubuntu@VM-0-6-ubuntu:~/container/caddy$ curl -sSI https://link.zenseek.site | head -n 818HTTP/2 302 19alt-svc: h3=":443"; ma=259200020content-language: en21content-type: text/html; charset=utf-822cross-origin-opener-policy: same-origin23location: /login/24referrer-policy: strict-origin-when-cross-origin25strict-transport-security: max-age=31536000; includeSubDomains