F5 XC | Stuck at VIRTUAL_HOST_PENDING_A_RECORD

[Joven]

I have a running OWASP Juice Shop in Azure and have assigned a public IP on it. Trying to build a load balancer using XC. I am stuck at the VIRTUAL_HOST_PENDING_A_RECORD status. Question is do I need to use my own DNS to create a domain name entry for my load balancer? Can I do anything to bypass this or any workaround you may have?

[MattHarmon]

Are you doing an HTTP LB on port 80 or doing HTTPS with Auto Cert or Bring Your Own Cert?  

[Joven]

I am trying both actually. Currently HTTPS with Auto Cert because when I try to use HTTP, I encounter an error that says cant change HTTPS to HTTP 

[netta2 · Accepted solution]

You will need to build a new LB for port 80 as you cannot switch between the 2 types.  When building a HTTPS LB you can click the button to build a HTTP Redirect and it will be created for you.

Also you have a few options for auto cert.  You can delegate a sub-domain and allow Distributed Cloud to manage the DNS records for the subdomain and provision the auto-cert.  You also can perform an auto-cert without sub-domain delegation.  You will get a cname for the acme challenge which you will have to create the record in the DNS system of the parent domain. 

[Joven]

Thanks it works now

[jdurand]

If you are trying to use Auto Cert generation for HTTPS you must either delegate your domain or set up a DNS challenge for LetsEncrypt.  Please find the instructions here https://docs.cloud.f5.com/docs/ves-concepts/load-balancing-and-proxy