< class="prominent-subhead ">

Redirect after authenticating on K2 Application Sites when using Chrome

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


When browing to a K2 site on Chrome, after providing credentials, the user will get the following redirect error:
"The webpage at xxx might be temporarily down or it may have moved permanently to a new web address".


This issue only occurs on Chrome, Internet Explorer works fine and all environment field entries for K2 are correct (i.e. webpage has not actually been moved). Additionally, after updating Chrome users may begin seeing the issue. This redirect error may also not happen to every single user.

Troubleshooting Steps

This may be due to the use of Symantec certificates on your environment. If you are using a Symantec certificate issued prior to June 1, 2016, then your certificates will be distrusted by Chrome following update Chrome 66. By Octover 23, 2018, Chrome 70 will distrust all Symantec certificates. For more on this, please refer to the following documentation: https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html

If you are uncertain if you are using Symantec certificates, or when those were issued, you can check this by going to the Microsoft Management Console > File > Add/Remove Snap-in..., Add the "Certificates" snap-in for your user account, and click "OK". From here, you should be able to see all certificates on the machine, including the Issuer and the Issue date. 

If you don't know what version of Chrome you are running on, you can go to Chrome Settings and select "About Google Chrome".