The instance's internal Caddy is only for Stoat itself, so the panel no longer goes through it: the bot ships its own compose project, publishes 3005 on loopback, and the host's external Caddy gives it a domain. extra_hosts pins the instance domain to host-gateway, so the bot reaches the API, gateway and LiveKit through the external proxy with a valid certificate instead of depending on router NAT loopback. The old in-project layout stays available as a fallback example, together with a step-by-step guide for when voice fails to connect. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
9 lines
446 B
Caddyfile
9 lines
446 B
Caddyfile
# Внешний Caddy на хосте: /etc/caddy/Caddyfile
|
|
# Добавьте блок рядом с остальными вашими сайтами.
|
|
music.example.com {
|
|
reverse_proxy 127.0.0.1:3005
|
|
}
|
|
|
|
# Внутренний Caddy инстанса трогать не нужно: панель к нему не относится.
|
|
# WebSocket (/ws) Caddy апгрейдит сам, отдельных директив не требуется.
|