Closed emarref closed 4 years ago
Can confirm, we have the same issue. Caddyfile:
our.domain:80 {
}
our.domain:443 {
tls self_signed
proxy /api http://server:5000 {
transparent
}
}
internal.net:443 {
tls server.crt server.key
proxy /api http://server:5000 {
transparent
}
}
Looking into it. Kindly stick to 1.0.1 for now.
Looks related to this https://github.com/caddyserver/caddy/issues/2706
This change in the config files fixes the issue with 1.0.2 https://github.com/caddyserver/caddy/issues/2706#issuecomment-521232621
A release with a fix is imminent https://github.com/caddyserver/caddy/issues/2706#issuecomment-521324042.
Awesome thanks very much
Fixed upstream. Docker hub should have 1.0.3 in few hours when the builds are done.
We are running caddy in a Kubernetes environment. The latest docker hub caddy update (1.0.2) has caused a panic, and our deployment never finishes. Caddy version 1.0.1 does not have this issue. This issue affects
abiosoft/caddy
from Docker Hub.The error message we get is:
With the following Caddyfile: