# Kibana dashboard is giving bad gateway

**URL:** <https://discuss.elastic.co/t/kibana-dashboard-is-giving-bad-gateway/312882>\
**Category:** Kibana\
**Created:** [August 25, 2022, 8:11am UTC](https://discuss.elastic.co/t/kibana-dashboard-is-giving-bad-gateway/312882 "2022-08-25T08:11:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandeep\_kumar5](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandeep_kumar5/32/109949_2.png) [@sandeep\_kumar5](https://discuss.elastic.co/u/sandeep_kumar5)\
**Post date:** [August 25, 2022, 8:11am UTC](https://discuss.elastic.co/t/kibana-dashboard-is-giving-bad-gateway/312882/1 "2022-08-25T08:11:32Z")

</div>

Hi

I have set up kibana and elasticsearch thru helm chart on a k8s cluster with Xpack. my elstic search urls is someting like [elk.abc.com](http://elk.abc.com) and kibana url is like [kibana.abc.com](http://kibana.abc.com)  
but kibana dashboard is giving me bad gateway.  
when i am putting elasticsearch url in kibana values.yaml it is npt able to retrieve the information and giving elasticsearch url not found

```auto
unable to retrieve version information from Elasticsearch nodes. getaddrinfo ENOTFOUND elasticsearch.pte.sgre.one

Could anybody please help me on this

```

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 25, 2022, 8:22am UTC](https://discuss.elastic.co/t/kibana-dashboard-is-giving-bad-gateway/312882/2 "2022-08-25T08:22:39Z")

</div>

> [@sandeep\_kumar5](#):
>
> `ENOTFOUND elasticsearch.pte.sgre.one`

That would suggest that this is not resolving to an IP, so it looks like an internal DNS issue.

---

<div class="post-metadata">

**Author:** ![sandeep\_kumar5](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandeep_kumar5/32/109949_2.png) [@sandeep\_kumar5](https://discuss.elastic.co/u/sandeep_kumar5)\
**Post date:** [August 25, 2022, 8:26am UTC](https://discuss.elastic.co/t/kibana-dashboard-is-giving-bad-gateway/312882/3 "2022-08-25T08:26:38Z")

</div>

@warkolm thanks for quick response  
one more input like if i am not passing any url to kibana values.yaml for ealstic search host it is workign with localhost but it is not working with hostname i.e. [kibana.abc.com](http://kibana.abc.com) it is giving bad gateway

Any suggestion on this`---

```auto
---
elasticsearchHosts: "http://elasticsearch-master:9200"
#elasticsearchHosts: "https://elasticsearch.pte.sgre.one"
replicas: 1

# Extra environment variables to append to this nodeGroup
# This will be appended to the current 'env:' key. You can use any of the kubernetes env
# syntax here
extraEnvs:
  - name: "NODE_OPTIONS"
    value: "--max-old-space-size=1800"
  - name: "ELASTICSEARCH_USERNAME"
    valueFrom:
      secretKeyRef:
        name: security-master-credentials
        key: username
  - name: "ELASTICSEARCH_PASSWORD"
    valueFrom:
      secretKeyRef:
        name: security-master-credentials
        key: password  
# - name: MY_ENVIRONMENT_VAR
# value: the_value_goes_here

# Allows you to load environment variables from kubernetes secret or config map
envFrom: []
# - secretRef:
# name: env-secret
# - configMapRef:
# name: config-map

# A list of secrets and their paths to mount inside the pod
# This is useful for mounting certificates for security and for mounting
# the X-Pack license
secretMounts: 
  - name: elastic-certificate-pem
    secretName: elastic-certificate-pem
    path: /usr/share/kibana/config/certs
# - name: kibana-keystore
# secretName: kibana-keystore
# path: /usr/share/kibana/data/kibana.keystore
# subPath: kibana.keystore # optional

hostAliases: []
#- ip: "127.0.0.1"
# hostnames:
# - "foo.local"
# - "bar.local"

image: "artifactory.pte.sgre.one:443/docker-local/kibana"
imageTag: "7.16.3"
imagePullPolicy: "IfNotPresent"

# additionals labels
labels: {}

podAnnotations:
  {}
  # iam.amazonaws.com/role: es-cluster

resources:
  requests:
    cpu: "2000m"
    memory: "3Gi"
  limits:
    cpu: "2000m"
    memory: "3Gi"

protocol: https

serverHost: "kibana.pte.sgre.one"

healthCheckPath: "/app/kibana"

# Allows you to add any config files in /usr/share/kibana/config/
# such as kibana.yml
kibanaConfig: 
  kibana.yml: |
    server.ssl:
      enabled: true
      key: /usr/share/kibana/config/certs/elastic-certificate.pem
      certificate: /usr/share/kibana/config/certs/elastic-certificate.pem
    xpack.security.encryptionKey: d5c503097193a7a5205fde00e19eef79
    elasticsearch.ssl:
      certificateAuthorities: /usr/share/kibana/config/certs/elastic-certificate.pem
      verificationMode: certificate
# kibana.yml: |
# key:
# nestedkey: value

# If Pod Security Policy in use it may be required to specify security context as well as service account

podSecurityContext:
  fsGroup: 1000

securityContext:
  capabilities:
    drop:
      - ALL
  # readOnlyRootFilesystem: true
  runAsNonRoot: true
  runAsUser: 1000

serviceAccount: ""

# Whether or not to automount the service account token in the pod. Normally, Kibana does not need this
automountToken: true

# This is the PriorityClass settings as defined in
# https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass
priorityClassName: ""

httpPort: 5601

extraVolumes:
  []
  # - name: extras
  # emptyDir: {}

extraVolumeMounts:
  []
  # - name: extras
  # mountPath: /usr/share/extras
  # readOnly: true
  #
extraContainers: ""
# - name: dummy-init
# image: busybox
# command: ['echo', 'hey']

extraInitContainers: ""
# - name: dummy-init
# image: busybox
# command: ['echo', 'hey']

updateStrategy:
  type: "Recreate"

service:
  type: ClusterIP
  loadBalancerIP: ""
  port: 5601
  nodePort: ""
  labels: {}
  annotations:
    {}
    # cloud.google.com/load-balancer-type: "Internal"
    # service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
    # service.beta.kubernetes.io/azure-load-balancer-internal: "true"
    # service.beta.kubernetes.io/openstack-internal-load-balancer: "true"
    # service.beta.kubernetes.io/cce-load-balancer-internal-vpc: "true"
  loadBalancerSourceRanges:
    []
    # 0.0.0.0/0
  httpPortName: http

ingress:
  enabled: true
  hosts:
    - host: kibana.pte.sgre.one
      paths:
        - path: /
  #tls: []
  # - secretName: chart-example-tls
      hosts:
        - chart-example.local

readinessProbe:
  failureThreshold: 3
  initialDelaySeconds: 10
  periodSeconds: 10
  successThreshold: 3
  timeoutSeconds: 5

imagePullSecrets: []
nodeSelector: {}
tolerations: []
affinity: {}

nameOverride: ""
fullnameOverride: ""

lifecycle:
  {}
  # preStop:
  # exec:
  # command: ["/bin/sh", "-c", "echo Hello from the postStart handler > /usr/share/message"]
  # postStart:
  # exec:
  # command: ["/bin/sh", "-c", "echo Hello from the postStart handler > /usr/share/message"]

# Deprecated - use only with versions < 6.6
elasticsearchURL: "" # "http://elasticsearch-master:9200"

```

this is kibana values file`

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 22, 2022, 8:27am UTC](https://discuss.elastic.co/t/kibana-dashboard-is-giving-bad-gateway/312882/4 "2022-09-22T08:27:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.