# TLS Certificates with Kong Ingress Controller without Host **URL:** \ **Category:** General\ **Tags:** kubernetes\ **Created:** [August 6, 2019, 6:39pm UTC](https://discuss.konghq.com/t/tls-certificates-with-kong-ingress-controller-without-host/4173 "2019-08-06T18:39:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Bosterito95](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@Bosterito95](https://discuss.konghq.com/u/Bosterito95)\ **Post date:** [August 6, 2019, 6:39pm UTC](https://discuss.konghq.com/t/tls-certificates-with-kong-ingress-controller-without-host/4173/1 "2019-08-06T18:39:24Z")
Hi, I’m trying to follow the steps here: [https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/guides/cert-manager.md](https://github.com/Kong/kubernetes-ingress-controller/blob/master/docs/guides/cert-manager.md) Is there a way to do this without having a domain name? If I don’t use TLS certificates, I don’t put any host and I end up just using the kong-proxy URL + a path as a URL. The main problem faced is that when trying to create it with a random name for the host, the certificate is stuck at temporary and at “OrderCreated”. When looking into the cert-manager pod, I see the following logs: I0806 18:36:11.974987 1 ingress.go:91] cert-manager/controller/challenges/http01/selfCheck/http01/ensureIngress “level”=0 “msg”=“found one existing HTTP01 solver ingress” “dnsName”=\ “related\_resource\_kind”=“Ingress” “related\_resource\_name”=“cm-acme-http-solver-k4jpd” “related\_resource\_namespace”=“default” “resource\_kind”=“Challenge” “resource\_name”= “resource\_namespace”=“default” “type”=“http-01” E0806 18:36:12.465886 1 sync.go:180] cert-manager/controller/challenges “msg”=“propagation check failed” “error”=“wrong status code ‘404’, expected ‘200’” “dnsName”=\ “resource\_kind”=“Challenge” “resource\_name”= “resource\_namespace”=“default” “type”=“http-01” ---
**Author:** ![Bosterito95](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@Bosterito95](https://discuss.konghq.com/u/Bosterito95)\ **Post date:** [August 6, 2019, 8:10pm UTC](https://discuss.konghq.com/t/tls-certificates-with-kong-ingress-controller-without-host/4173/2 "2019-08-06T20:10:25Z")
If anyone is facing the same issue, this is what I used for a DNS domain name: > **[Create an HTTPS ingress with Azure Kubernetes Service (AKS) cluster](https://docs.microsoft.com/en-us/azure/aks/ingress-tls#configure-a-dns-name)** > > Learn how to install and configure an NGINX ingress controller that uses Let's Encrypt for automatic TLS certificate generation in an Azure Kubernetes Service (AKS) cluster. ---
**Author:** ![hbagdi](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/hbagdi/32/562_2.png) [@hbagdi](https://discuss.konghq.com/u/hbagdi)\ **Post date:** [August 6, 2019, 9:59pm UTC](https://discuss.konghq.com/t/tls-certificates-with-kong-ingress-controller-without-host/4173/3 "2019-08-06T21:59:12Z")
@Bosterito95 Was your issue resolved? It is unclear from your second post. To get a TLS certificate, you will need to setup DNS correctly so that Let’s Encrypt can verify the ownership of the domain and then give you a certificate for it. If you wish to automate DNS creation based on your Ingress definition, try using external-dns: > **[kubernetes-incubator/external-dns](https://github.com/kubernetes-incubator/external-dns)** > > Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services - kubernetes-incubator/external-dns ---
**Author:** ![Bosterito95](https://avatars.discourse-cdn.com/v4/letter/b/ccd318/32.png) [@Bosterito95](https://discuss.konghq.com/u/Bosterito95)\ **Post date:** [August 7, 2019, 1:37pm UTC](https://discuss.konghq.com/t/tls-certificates-with-kong-ingress-controller-without-host/4173/4 "2019-08-07T13:37:32Z")
@hbagdi Yup, was running on Azure and set up a FQDN for the kong-proxy external IP.