Nomad Consul Connect with Consul TLS Active failing

Nomad
1

I have my consul, nomad with tls active, but when integrating the native nomad connect stanza to my job deployment it is failing to register the sidecar proxy

    2019-11-15T19:06:09.319Z [ERROR] client.alloc_runner.task_runner.task_hook.envoy_bootstrap: error creating bootstrap configuration for Connect proxy sidecar: alloc_id=6bfe4026-66a9-efdc-aa7e-8fbdbe0286ee task=connect-proxy-booking-api error="exit status 1" stderr="==> Failed looking up sidecar proxy info for _nomad-task-6bfe4026-66a9-efdc-aa7e-8fbdbe0286ee-group-booking-api-booking-api-3002: Unexpected response code: 400 (Client sent an HTTP request to an HTTPS server.
)
"
    2019-11-15T19:06:09.319Z [ERROR] client.alloc_runner.task_runner: prestart failed: alloc_id=6bfe4026-66a9-efdc-aa7e-8fbdbe0286ee task=connect-proxy-booking-api error="prestart hook "envoy_bootstrap" failed: error creating bootstrap configuration for Connect proxy sidecar: exit status 1"
    2019-11-15T19:06:09.319Z [INFO ] client.alloc_runner.task_runner: restarting task: alloc_id=6bfe4026-66a9-efdc-aa7e-8fbdbe0286ee task=connect-proxy-booking-api reason="Restart within policy" delay=18.131309709s

I can’t find in the docs where to enable tls for connect in nomad

2

Hi @Crizstian! Using Nomad with Consul’s TLS has some known issues (see https://github.com/hashicorp/nomad/issues/6594), which we’re still working through.