Caddy v2 issues with internal certificates

[dallas007]

Hi there,

I’m using Caddy v2.1 and trying to understand how are different certs (self sign) V1 from Caddy V2.

I’m getting this error with certs from Caddy V2:

{
   "level":"error",
   "ts":1594645952.7374322,
   "logger":"http.log.access",
   "msg":"handled request",
   "request":{
      "method":"POST",
      "uri":"/PATH/api/accessgroups",
      "proto":"HTTP/1.1",
      "remote_addr":"10.255.0.2:44314",
      "host":"localhost:8070",
      "headers":{
         "Cache-Control":[
            "no-cache"
         ],
         "Postman-Token":[
            "token"
         ],
         "Connection":[
            "keep-alive"
         ],
         "Authorization":[
            "SharedAccessSignature cid=blabla"
         ],
         "User-Agent":[
            "PostmanRuntime/7.26.1"
         ],
         "Accept":[
            "*/*"
         ],
         "Content-Type":[
            "application/json"
         ],
         "Accept-Encoding":[
            "gzip, deflate, br"
         ],
         "Content-Length":[
            "27"
         ]
      },
      "tls":{
         "resumed":false,
         "version":772,
         "ciphersuite":4865,
         "proto":"",
         "proto_mutual":true,
         "server_name":"localhost"
      }
   },
   "common_log":"10.255.0.2 - - [13/Jul/2020:13:12:32 +0000] \"POST /PATH/api/accessgroups HTTP/1.1\" 502 0",
   "duration":3514.782453623,
   "size":0,
   "status":502,
   "resp_headers":{
      "Server":[
         "Caddy"
      ]
   }
}

Is it there any reason for that?

My Caddy config for certs is like this:

tls internal {
  on_demand
}

Regards,

[francislavoie]

A 502 error just means that Caddy couldn’t connect to your proxy upstream. Doesn’t have anything to do with TLS.