You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that the Caddyfile adapter would need to recognize that both of those bind addresses will exist on other servers that exclusively listen to that address, then copy the routes for your 3 domain to both of those. It's not currently smart enough to do that.
Run caddy adapt -p on your Caddyfile to see what I mean, Caddy produces servers with listen addresses, and the servers must not overlap otherwise they will try to bind to the same address.
Oh... yeah, edge case. That is just a little more complicated than I wanted to do at the time. So if we're going to fix that we'll need to decide if it's worth the added complexity.
when using the default_bind and a custom or multiple custom binds on the same address ar used caddy tries to bind 2 two or more times to the address.
using caddy v2.7.6 h1:w0NymbG2m9PcvKWsrXO6EEkY9Ru4FJK8uQbYcev1p3A=
setup:
i have 3 services which need an upgrade from http to https, each listen on a local port
now i specify with caddy 3 sections
so this does not work, even if i remove the bind of the last block.
The text was updated successfully, but these errors were encountered: