Skip to main content
Announcements
Jan 15, Trends 2025! Get expert guidance to thrive post-AI with After AI: REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
mgranillo
Specialist
Specialist

Lots of users having to clear browser cache

On QSEoW we are getting a lot of reports of users unable to access Qlik. An error message does not pop up, the hub simply does not populate with content. Clearing their browser cache seems to resolve the issue. Does anyone know why this would start occurring? 

Labels (3)
3 Replies
Ray_Strother
Support
Support

Hello ,

1. Did this issue start after an upgrade?
2. Are you using SAML?
3. Please perform a HAR file trace for an affected user and look for the 431 error.
4. If you see the 431 error , review the remaining two article below (2 and 3)

Article links:

1. Save network web traffic (HAR/XML file) and console logs from the browser's developer tools

https://community.qlik.com/t5/Official-Support-Articles/Save-network-web-traffic-HAR-XML-file-and-co...



2. Error 431 when trying to access the Qlik Sense Management Console or Hub

https://community.qlik.com/t5/Official-Support-Articles/Error-431-when-trying-to-access-the-Qlik-Sen...



3. Qlik Sense Client Managed: Adjust the MaxHttpHeaderSize for the Micro Services run by the ServiceDispatcher

https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Client-Managed-Adjust-the-MaxHttp...

mgranillo
Specialist
Specialist
Author

Yes, it started after an upgrade to May 2024. We also had windows patching the same day.  

Yes, we use SAML

Thank you for the suggestions. I will attempt a HAR file trace the next time this comes up.

mgranillo
Specialist
Specialist
Author

@Ray_Strother I was able to confirm some of our problems are due to error 431. Before making changes to our environment as outlined in the articles, I want to ask why I wouldn't see the issue across browsers. One of our users typically uses Edge and was unable to access Qlik, but the same user was able to access Qlik without an issue in Chrome. Is this indicative of another problem?