{
}
:80
# Compress responses according to Accept-Encoding headers
encode gzip zstd
tracing {
span caddy_span
}
reverse_proxy {
to 10.43.181.223:8888
lb_policy least_conn
header_down -x-powered-by
}
3. The problem I’m having:
No spans are visible in the Jaeger UI. Tested multiple configs but couldn’t find a working one. Jaeger is deployed on a VPS using the all-in-one docker image, using the example command:
gRPC protocol config yields this error, hinting that the INSECURE parameter is ignored
root-caddy-1 | 2022/08/04 08:08:53 max retry time elapsed: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake"
HTTP protocol config (using both json and protobuf) yields this error:
root-caddy-1 | 2022/08/04 08:10:05 max retry time elapsed: rpc error: code = Unavailable desc = connection closed before server preface received
tried this (along with the other INSECURE variables), same outcome. I also tried setting the endpoint to a non-existing domain and then I got a DNS resolver error message, so I know that the environmental variables set in docker-compose.yml indeed are visible by Caddy.
My plan is to add a reverse proxy in front of Jaeger for SSL termination and then it should all work. But if the insecure option can be enabled, that’d definitely be easier
It seems like the difference was 4318 (what you used) and 4317. You did try that port, but it looks like you used https:// there which might’ve been the problem.