Thread Info
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 29 subscribers
  • Views 5864 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

WAF not allowing wildcard certificate for HTTPS firewall rule

Steen Paulsen

I have several web servers on my network.

Until now I have provisioned a LetsEncrypt ssl cert for each sub domain:

  • subdomain1.mydomain.com
  • subdomain2.mydomain.com
  • ...

Now I have so many servers that its an extensive process to renew all of the certificates individually every two months.

I obtained a wildcard certificate *.mydomain.com and would like to use that, but when using that certificate in a Business Application Rule for my webservers, I get this message:

"The following domains in the HTTPS certificate "WILDCARD.mydomain.com" are invalid and have been removed: 1. *.mydomain.com"

Am I doing something wrong, or does XG not support wildcard certificates for my purpose?



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to Steen Paulsen

    I'm having same issue. Added my wildcard cert under Certificates. And when i add this i am getting same error message. How did you fix this?

     

    any idea? i've it downloaded from the existing AWS server into Azure VM as pfx. Should i try it with PEM instead?

Children