Forum Discussion
teemo_13
Cirrus
CirrusF5 XC | Stuck at VIRTUAL_HOST_PENDING_A_RECORD
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...
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.
MattHarmon
Employee
EmployeeAre you doing an HTTP LB on port 80 or doing HTTPS with Auto Cert or Bring Your Own Cert?
teemo_13Cirrus
CirrusI 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
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.- teemo_13
Thanks it works now
jdurandIf 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
HomesteadbrewerNimbostratus
Trying to follow the instructions as you pointed out... however, the cert status is stuck in "PreDomainChallengePending". There is no entry in the acme challenge field.