Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
A qlik server just have been upgrade to may2024 version and a strange bug seems to happen to certain users.
While some users have no issue to connect to qlik and work on it, others are totally stuck on the "loading" process to the hub.
I tried to empty the cache, check the log that show that user succesfully connect to qlik.....I have no clue on what is happening here. I have found several post on the community regarding such a bug in 2014 but i can't be sure this is about the same problem.
Any clue ?
This fixed it for me Qlik Sense : "Qlik Sense G3 Broker API" error on t... - Qlik Community - 1711832
Have my login linked so SAML using GSuite, do not a big big number of groups. So not really linked to the described issue.
Steps:
[globals]
LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
MigrationPort=4545
(...)
MaxHttpHeaderSize=65534
I confirmed that I resolved this issue but I put a wrong link:
It works well.
Hi @mpc ,
Thanks for your answer.
What does that security rule do?
This one enable/disable user cache for the QMC to ContentAdmin or DeploymentAdmin
I have the issue on both HUB and QMC.
I guess the security rule is not the cause.
Hi agilliotti,
Do you use SAML or OIDC config in your virtual proxy ? After an Qlik Upgrade, a request can return a 431 error (header size) due to the number of groups return in your token. I already encounter this problem after an upgrade and we modified the header size in dispatcher configuration file at C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf (Same step described by p_verkooijn). To confirm if you encounter this issue you can open your developer tool and in network size track http request in error 431.
We experienced same issue with Feb 2024 version. Patch 10 did not resolve the issue.
Hi,
Can you share Qlik Sense logs from collector and share timetstamp of this (common) issue please ?
Regards