# Ingress Controller registers HTTPS services as HTTP (and port 443 as port 80)

**URL:** https://discuss.konghq.com/t/ingress-controller-registers-https-services-as-http-and-port-443-as-port-80/2784
**Category:** General
**Tags:** kubernetes
**Created:** [February 10, 2019, 1:42am UTC](https://discuss.konghq.com/t/ingress-controller-registers-https-services-as-http-and-port-443-as-port-80/2784 "2019-02-10T01:42:21Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![ravibagri5](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/ravibagri5/32/1305_2.png) [@ravibagri5](https://discuss.konghq.com/u/ravibagri5)
#### Post date: [September 2, 2019, 12:46pm UTC](https://discuss.konghq.com/t/ingress-controller-registers-https-services-as-http-and-port-443-as-port-80/2784/6 "2019-09-02T12:46:14Z")

</div>

@hbagdi I’m also facing the same issue and using the mentioned KongIngress doesn’t resolve the issue.  
Is there any other way to use E2E TLS in kong. Basically, i need to istio kiali UI using kong.

---

_[View the full topic](https://discuss.konghq.com/t/ingress-controller-registers-https-services-as-http-and-port-443-as-port-80/2784)._