# Unable to initialise Vault with Consul HA backend on AKS

**URL:** <https://discuss.hashicorp.com/t/unable-to-initialise-vault-with-consul-ha-backend-on-aks/20128>\
**Category:** Vault\
**Tags:** k8s, vault, azure\
**Created:** [January 25, 2021, 11:40am UTC](https://discuss.hashicorp.com/t/unable-to-initialise-vault-with-consul-ha-backend-on-aks/20128 "2021-01-25T11:40:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![r3mattia](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/r3mattia/32/16716_2.png) [@r3mattia](https://discuss.hashicorp.com/u/r3mattia)\
**Post date:** [January 25, 2021, 11:40am UTC](https://discuss.hashicorp.com/t/unable-to-initialise-vault-with-consul-ha-backend-on-aks/20128/1 "2021-01-25T11:40:15Z")

</div>

Hi,

I am currently deploying Consul with TLS enabled and Vault in HA mode on top of Consul.

In both cases I am deploying using the Helm charts and I am deploying both clusters in separate namespaces, ie. consul in the consul namespace, vault in the vault namespace.

For now, I am creating the TLS CA and server certificates using `consul tls create` commands, and installing these as k8s secrets in both namespaces (vault and consul), whilst adding the extraVolume mounts in the Helm chart `.yaml` files accordingly.

Consul works fine with TLS, and Raft works fine. I have 3 instances, and 1/3 is a leader at all times. There are no errors in my logs related to bad certificate names, or any other errors, and I can port-forward on port 8501 to access the UI with HTTPS, in addition to extracting the CA certificate if necessary.

However, I am encountering a very annoying problem when I am deploying Vault. Regardless of how I setup the values in my `.yaml` file for the Helm chart installation, I keep getting:

```auto
/ $ vault status
Error checking seal status: Get "http://127.0.0.1:8200/v1/sys/seal-status": dial tcp 127.0.0.1:8200: connect: connection refused
/ $ vault operator init
Error initializing: Put "http://127.0.0.1:8200/v1/sys/init": dial tcp 127.0.0.1:8200: connect: connection refused
/ $

```

If I port-forward port 8200, and do a curl on http(s)://localhost:8200 I get a timeout , or a (35) SSL\_ERROR\_SYSCALL, or a (56) Recv Failure. This is regardless of whether I disable TLS, or not in my Vault values `.yaml` file.

I am truly stuck on this, so any help would be greatly appreciated.

Thank you!