# Not working Https Elasticsearch with GKE default ingress **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [August 17, 2020, 5:43am UTC](https://discuss.elastic.co/t/not-working-https-elasticsearch-with-gke-default-ingress/245180 "2020-08-17T05:43:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kumar\_abhishek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar_abhishek/32/73973_2.png) [@kumar\_abhishek](https://discuss.elastic.co/u/kumar_abhishek)\ **Post date:** [August 17, 2020, 5:43am UTC](https://discuss.elastic.co/t/not-working-https-elasticsearch-with-gke-default-ingress/245180/1 "2020-08-17T05:43:28Z")
Hi, Can Anyone help me here? I was able to configure and install an elastic search /kibana using Eck Operator in my environment (GKE GCP) and also able to enable Kibana with an https using GCP managed certificate for SSL with GCP Default Ingress. but I'm not able to do with elastic search only with Kibana. when I use ingress and point to elastic search its throw 502 bad gateway. but it's working with kibana . can anyone let me know if you also faced some issues similar to that or how it should be resolved? ![Screenshot 2020-08-17 at 11.14.32 AM](https://us1.discourse-cdn.com/elastic/original/3X/8/b/8b6b224c22097346b435d1a4020b119aab05eecc.png) ---
**Author:** ![charith-elastic](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@charith-elastic](https://discuss.elastic.co/u/charith-elastic)\ **Post date:** [August 18, 2020, 6:47am UTC](https://discuss.elastic.co/t/not-working-https-elasticsearch-with-gke-default-ingress/245180/2 "2020-08-18T06:47:49Z")
It's difficult to give you an answer without more information about your setup. Pasting the contents of the manifests here would be helpful to diagnose the issue. My hunch is that you are getting errors for the Elasticsearch endpoint because the Google Cloud Load Balancer (GCLB) creates an implicit health check by reusing the readiness probe. The default readiness probe created by ECK is not an HTTP probe and therefore GCLB fails to create the health check and considers the backend to be unavailable. The reason ECK does not create an HTTP readiness probe by default is because it requires anonymous access to be enabled for Elasticsearch. You can restrict the scope of anonymous access but it is something that needs to be carefully considered as the Elasticsearch cluster will be open to the internet. If you are comfortable doing so, we have an example of configuring GCLB at [https://github.com/elastic/cloud-on-k8s/tree/1.2/config/recipes/gclb](https://github.com/elastic/cloud-on-k8s/tree/1.2/config/recipes/gclb). Alternatively, you can configure a reverse proxy in front of Elasticsearch and expose the proxy through the ingress. That way, you don't have to change the Elasticsearch security to allow anonymous access. ---
**Author:** ![kumar\_abhishek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kumar_abhishek/32/73973_2.png) [@kumar\_abhishek](https://discuss.elastic.co/u/kumar_abhishek)\ **Post date:** [September 4, 2020, 10:38am UTC](https://discuss.elastic.co/t/not-working-https-elasticsearch-with-gke-default-ingress/245180/3 "2020-09-04T10:38:04Z")
Thanks for the help Charith , i was able to test https for Elastic-search. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 2, 2020, 10:38am UTC](https://discuss.elastic.co/t/not-working-https-elasticsearch-with-gke-default-ingress/245180/4 "2020-10-02T10:38:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.