Hi all,
firewall already uses a wildcard cert for WAF, I tried to set it up for "Admin console and end-user interaction" as it is called in the Admin settings. Applying the cert resultet in not being able to reach the Webadmin and Userportal, neither via hostname nor IP. Not a "no valid cert" error, but straight up not able to establish a connection, regardless of browser. Chaged back to default cert via CLI. As this firewall was setup, the company name was still being determined, so the firewall only has a host- and not a fully qualified named, with the domain name in the certificate. Could this be the problem? I am hesistent to change the hostname of the firewall, because I assume that all selfsigned certificates will be recreated. Are there any other things we have to consider?
Thanks
This thread was automatically locked due to age.