"This Connection is Not Private" Errors on Cross-Browser Mobile Instances

About Article:

This article will cover how to achieve the following-

• Understand why the "This Connection is Not Private" error occurs during Cross-Browser Mobile executions.
• Implement potential workarounds for navigating SSL-related warnings.

Problem Statement:

During Cross-Browser execution on mobile devices (e.g., Google Pixel on Android 10/11, iPhone on iOS 13/14), the journey encounters the error "This Connection is Not Private". This issue does not occur during Live Authoring or executions on Virtuoso Chrome. Attempts to navigate past the warning page using extensions and predefined steps often face click limitations, preventing further progress in the journey.

Cause:

The error occurs due to SSL certificate mismatches. In this specific case:

• The certificate is not self-signed; it was issued by ca.jato.goskope.com for *.jato.com.
• The bypassBadSSLOnSafari extension (Link) is designed for self-signed certificates, which explains why it does not resolve the issue for this certificate type.
• Self-signed certificates can work with iOS devices when using the extension but will not work for Android devices, as noted in previous documentation.

Workaround:

1. Use a Self-Signed Certificate for Testing:

   • The bypassBadSSLOnSafari extension works with self-signed certificates and can navigate past the "This Connection is Not Private" page for iOS devices.
   • For example, testing with a self-signed certificate on https://self-signed.badssl.com/ confirms successful execution using the extension on iOS 13 through BrowserStack.

        2. Steps to Incorporate the Extension:

• Add the following steps to your journey:

  Navigate to "URL" 
  bypassBadSSLOnSafari 
  Wait for "element on the page"

• These steps only work for self-signed certificates and may still face limitations on Android devices.

      3. Verify Certificate Type:

• If using a domain-signed certificate (as illustrated below), the bypassBadSSLOnSafari extension will not work. Ensure testing environments utilize self-signed certificates for bypassing SSL errors during Cross-Browser executions.

     4. Alternative Options:

• Client certificates are not applicable in this case as they serve a different purpose (authenticating Virtuoso rather than addressing SSL warnings).

Note:

• The workaround is limited to self-signed certificates and does not resolve domain-signed SSL mismatch issues.
• Android devices currently lack support for bypassing "This Connection is Not Private" errors using extensions like bypassBadSSLOnSafari.
• For further testing, the customer can validate with SSL testing sites like https://badssl.com/ to replicate scenarios.

Example:

• A customer encountered the SSL warning while executing a journey on iOS and Android devices during Cross-Browser testing. By switching to a self-signed certificate, the bypassBadSSLOnSafari extension successfully navigated past the warning on iOS devices, allowing the journey to proceed.