If muted, you’ll see an Unmute site option. Make sure the page is not muted by right-clicking on its tab.Refresh the current Chrome tab not playing sound.Play sound in another browser this will help determine the origin of the problem.Try these fixes to get your sound working: If the solution above didn’t solve your sound issues, there are more options that might. Recommended Solution: Update SSL certificates.Further Sound Troubleshooting the Chrome Browser Workaround: Try general workaround mention above. You can go through to know more about it. Recommended Solution: Use SHA2 certificates with Subject Alternative Names (SAN).ĬTX134123 - Receiver for HTML5 - Unable to Launch Apps Using HTTPS URLĬTX217352 - How to Collect Logs in Receiver for Chrome and Receiver for HTML5įrom Chrome OS version 66 onwards the SSL certificate from Symantec is distrusted. Workaround for NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM andĮnable from about:configĬhrome by default requires SHA2 Certificate with Subject Alternative Names (SAN)Īdd the following registry keys at : Software\Policies\Google\Chrome\ĮnableCommonNameFallbackForLocalAnchors – true Session launch fails with CERT_COMMON_NAME_INVALID(-200) error dialog Latest Firefox and Chrome browsers do not support SHA-1 certificate and StoreFront connection fails with error: NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHMĬitrix Receiver for Chrome/HTML5 or Citrix Workspace app for Chrome/HTML5 cannot establish secure connection and session launch will failĬhrome 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 NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM error
Other possible workaround for specific certificate error:
Now, open the Citrix Workspace app for Chrome or Citrix Receiver for Chrome and it might allow you to access your StoreFront/VDA. Alternatively, you can try this workaround:Ĭlose the Citrix Workspace app for Chrome / Citrix Receiver for Chrome. Recommended solution: Update the certificates.
0 kommentar(er)
