# Transport: Error while dialing remote error: tls: internal error"

**URL:** <https://discuss.hashicorp.com/t/transport-error-while-dialing-remote-error-tls-internal-error/29177>\
**Category:** Vault\
**Tags:** k8s, helm\
**Created:** [September 6, 2021, 2:22pm UTC](https://discuss.hashicorp.com/t/transport-error-while-dialing-remote-error-tls-internal-error/29177 "2021-09-06T14:22:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![julienMichaud](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/julienmichaud/32/22133_2.png) [@julienMichaud](https://discuss.hashicorp.com/u/julienMichaud)\
**Post date:** [September 6, 2021, 2:22pm UTC](https://discuss.hashicorp.com/t/transport-error-while-dialing-remote-error-tls-internal-error/29177/1 "2021-09-06T14:22:24Z")

</div>

Hi,

Im using the Vault helm chart to install Vault in my k8s cluster.

Im seeing this error when the pods are starting:

```auto
2021-09-06T14:09:34.357Z [ERROR] core: error during forwarded RPC request: error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing remote error: tls: internal error""
2021-09-06T14:09:34.357Z [ERROR] core: forward request error: error="error during forwarding RPC request"

```

I did disable TLS in the helm chart:

```auto
global:  
  enabled: true  
  tlsDisable: true

  service:
    enabled: true
    type: NodePort

  ha:
    enabled: true
    replicas: 3
    config: |
      ui = true
      listener "tcp" {
        address = "[::]:8200"
        cluster_address = "[::]:8201"
        tls_disable = 1
      }
      storage "postgresql" {
        connection_url = "postgres://${rds-username}:${rds-password}@${rds-address}.:5432/${rds-db-name}?sslmode=disable"
        table = "vault_kv_store"
        ha_enabled = "true"
        ha_table = "vault_ha_locks"
      }
      service_registration "kubernetes" {}
      seal "awskms" {
        region = "eu-west-1"
        kms_key_id = "${kms-key-id}"
      }

```

do you know why I still see this error ?  
EKS version 1.21  
Thanks

---

<div class="post-metadata">

**Author:** ![tlazo](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/tlazo/32/22141_2.png) [@tlazo](https://discuss.hashicorp.com/u/tlazo)\
**Post date:** [September 6, 2021, 6:04pm UTC](https://discuss.hashicorp.com/t/transport-error-while-dialing-remote-error-tls-internal-error/29177/2 "2021-09-06T18:04:38Z")

</div>

We started having the same issue today. Same a Julien, we host Vault on a k8s cluster.

---

<div class="post-metadata">

**Author:** ![Mais316](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/mais316/32/24765_2.png) [@Mais316](https://discuss.hashicorp.com/u/Mais316)\
**Post date:** [January 18, 2023, 3:08pm UTC](https://discuss.hashicorp.com/t/transport-error-while-dialing-remote-error-tls-internal-error/29177/3 "2023-01-18T15:08:54Z")

</div>

We have the same issue.

---

<div class="post-metadata">

**Author:** ![fram.souza14](https://avatars.discourse-cdn.com/v4/letter/f/b5ac83/32.png) [@fram.souza14](https://discuss.hashicorp.com/u/fram.souza14)\
**Post date:** [January 26, 2024, 2:17pm UTC](https://discuss.hashicorp.com/t/transport-error-while-dialing-remote-error-tls-internal-error/29177/4 "2024-01-26T14:17:44Z")

</div>

how did you get that fixed @julienMichaud ?