If you’re talking about the errors directive; I just added it in and nothing is shown in that log. The access logs via the “log” directive also does not show anything.
It does use SNI. Using IIS/ARR it works fine so I’m not fully understanding why this isn’t; mainly because I see Caddy respond with a response header when using http but as soon as the flip to HTTP happens it no longer works; the AWS/ALB gives a 502 and on the Caddy server I see the attempted handshake for TLS 1.2 but it errors out. I’ve verified that caddy/tomcat is working fine by accessing the site via a browser on the local server that has Caddy/Tomcat.