Caddy is behind sslh on IPv4, but I now have dual-stack IPv6 at home. I was hoping to make Caddy bind to specific addresses for both v4 and v6 but the last bind statement appears to win - i.e. Caddy no longer listens on IPv4 if I have the v6 bind last
https://my.site:443 {
bind 127.0.0.3 #yes, this is to allow sslh to work
bind v6.my.site #resolves to a specific v6 address
root /var/www/sites/my.site
log / /var/log/caddy/access.my.site "{combined}"
tls {
dns gandiv5
}
}
a. System environment:
OS, relevant versions, systemd? docker? etc.
Ubuntu 19.04, systemd 240
It looks like this would add multiple binds to Caddy 1.0 - however it doesn’t appear to be merged in.
@matt’s last comment also seems relevant if you were thinking about testing out Caddy 2 beta:
FYI, the equivalent capability (binding to multiple interfaces) is already working natively in Caddy 2, and the v2 Caddyfile supports multiple bind addresses, so this PR would only affect Caddy 1. It’s up to you whether to continue with this. Thank you for working on it!