BAD CERTIFICATE with consul connect

Hi 👋🏻

#### Overview of the Issue

I tried to create hashistack with ACL and TLS on single node for now.
When I launch a test job with consul connect won't work

I posted issue here after this thread on discuss: [Nomad discuss](https://discuss.hashicorp.com/t/services-not-deregister-after-nomad-stop-job/51253/1) after it is advised to post on Consul forum.

Consul 1.15.1
Nomad 1.5

I see in [changes](https://developer.hashicorp.com/consul/docs/upgrading/upgrade-specific#changes-to-grpc-tls-configuration) what it needed to work. But I don't know how to apply with Nomad job deploy.

I'm not sure about which from Consul or Nomad come from issue

---

#### Reproduction Steps

Create a single node Hashistack with Consul 1.15.1 Vault 1.13 (consul backend) Nomad 1.5 .

Launch job with first Sidecar:
```
job "mosquitto" {
region = "global"
datacenters = ["dc1"]
type = "service"

group "mosquitto" {

count = 1

restart {
attempts = 10
interval = "5m"
delay = "10s"
mode = "delay"
}

network {
mode = "bridge"

port "mqtt" {
to = 1883
static = 1883
}
}

service {
name = "mqtt"
port = "1883"

connect {
sidecar_service {}

sidecar_task {
resources {
cpu = 64
memory = 64
}
}
}
}

task "mosquitto" {
driver = "docker"

config {
image = "eclipse-mosquitto:latest"

mount {
type = "bind"
target = "/mosquitto/config/mosquitto.conf"
source = "local/mosquitto.conf"
readonly = false
bind_options {
propagation = "rshared"
}
}

ports = ["mqtt"]
}

template {
data = <