Cursors that employ shadow effects for example are classed as 32-bit cursors and not currently supported by Receiver for Mac. This is a known issue and 32-bit cursors are being investigated as part of the product road maps for Citrix Receiver for Mac. When using HDX 3D Pro, a black box may appear around some custom cursors. This issue will be fixed under an existing enhancement request. If NetScaler cannot resolve the domain name then users will get an invalid response. The Mac VPN client does not support split DNS so all DNS requests are sent to NetScaler for resolution. Windows Mac users connect to NetScale full VPN, they cannot reach external websites. Redirection of this device is not fully supported but there is a method to follow that can be tried to get it working, as explained in the CTX article. Receiver for Mac / Workspace app for Mac:Īpplicable Product Versions Affected (if known)īloomberg keyboard and finger print scanner not redirecting to Citrix session. You can also use your browsers search feature which will perform a search against the whole page based on the words you enter. For example if you have an error code or error message, use that to perform a search. There is a search box that you can use if looking for a specific fault. For each issue, known product versions affected are recorded however that does not mean product versions that aren’t listed are not affected. Links may also expire or change so if you find broken links, please again let me know. Articles will change from time and if information here is outdated or incorrect please let me know using the comments. The page is updated daily with new support articles and information. Recommended Solution: Update SSL certificates.A list containing the majority of Citrix Workspace app for Mac (formerly Receiver for Mac) support articles collated to make this page a one stop place for you to search for and find information regarding any issues you have with the product and its related dependencies. 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 Comments
Leave a Reply. |