Google Citrix Workspace

1. Recommended solution: Update the certificates. Alternatively, you can try this workaround: Close the Citrix Workspace app for Chrome / Citrix Receiver for Chrome. Open Chrome browser in your Chromebook.
2. Citrix Receiver for Windows product software. Citrix Workspace App Workspace app for Windows Current Release Subscribe to RSS notifications of new downloads.

The Citrix Workspace app allows for secure, unified access to all of your SaaS apps, web apps, virtual apps, files, and desktops. If your company uses Citrix, simply login with your company credentials to access all of the resources you need to be productive from anywhere.

Google Play Store Citrix Workspace App

Applicable Products

• Receiver for HTML5
• Receiver for Chrome

Symptoms or Error

Connection to StoreFront/VDA will fail and may show cannot connect to server error or some SSL Certificate error in console logs. One of the reason could be invalid SSL certificate.

Google Play Citrix Workspace

Applicable Products:

Citrix Receiver for HTML5, Citrix Receiver for Chrome, Citrix Workspace app for Chrome, Citrix workspace app for HTML5

Solution

Recommended solution: Update the certificates.

Alternatively, you can try this workaround:

1. Close the Citrix Workspace app for Chrome / Citrix Receiver for Chrome.

2. Open Chrome browser in your Chromebook.

3. Visit your site.
   

4. It will show some error as below.

Now, open the Citrix Workspace app for Chrome or Citrix Receiver for Chrome and it might allow you to access your StoreFront/VDA.

Other possible workaround for specific certificate error:

1. NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM error
   Latest Firefox and Chrome browsers do not support SHA-1 certificate and StoreFront connection fails with error: NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM
   Citrix Receiver for Chrome/HTML5 or Citrix Workspace app for Chrome/HTML5 cannot establish secure connection and session launch will fail
   

2. NET::ERR_CERT_COMMON_NAME_INVALID error
   Chrome requires Subject Alternative Name for SHA-2 certificate, without SAN (Subject Alternative Name) in the SHA-2 certificate, the connection will fail with error NET::ERR_CERT_COMMON_NAME_INVALID
   Session launch fails with CERT_COMMON_NAME_INVALID(-200) error dialog
   Workaround for NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM and
   NET::ERR_CERT_COMMON_NAME_INVALID:

   • Mozilla:

     Enable network.websocket.allowInsecureFormHTTPS from about:config

   • Chrome:
     Chrome by default requires SHA2 Certificate with Subject Alternative Names (SAN)
     Add the following registry keys at : SoftwarePoliciesGoogleChrome

   • EnableCommonNameFallbackForLocalAnchors – true
     (Note: Chrome need SAN by default)

   • EnableSha1ForLocalAnchors – true
     (Note: SHA1 is not supported)
     Recommended Solution: Use SHA2 certificates with Subject Alternative Names (SAN).

     Problem Cause:

   • CTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URL

   • CTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5

3. NET::ERR_CERT_SYMANTEC_LEGACY
   From Chrome OS version 66 onwards the SSL certificate from Symantec is distrusted. You can go through https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html to know more about it.
   Workaround: Try general workaround mention above.
   Recommended Solution: Update SSL certificates.

Problem Cause

• CTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URL

• CTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5 Cd and dvd label maker for mac.