I run Caddy (v2) in a docker container as a proxy to other docker containers. To fix an example, I have https://test.example.com that is correctly displayed from a browser. 192.168.10.2 is the server that hosts the docker engine (and on which caddy exposes 443) test.example.com points to 192.16…

I think you’ll want to use the --resolve option of curl for this. The reason its failing is because setting the Host header isn’t enough to have SNI be set for the TLS handshake: https://hacksbrain.com/2018/08/27/testing-sni-enabled-servers-with-curl/

Thank you @francislavoie - that was it indeed!

Caddy Community

Why curl fails while browser calls succeed?

Help

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled