GlobalProtect Error, Secure Connection Failed""

Issue

Self-signed certificates have been configured for use with GlobalProtect, but the user is now getting the error response, "Secure Connection Failed." when browsing the web.

Resolution

When setting up GlobalProtect with self-signed certificates, always make sure the common names on the Root CA cert and the Server cert are different.  This error occurs when the two have the same name.  Similarly, this error will occur if the same FQDN is used for the Root CA and the server certificate.

owner: jnguyen