Credentials are entered to access Qlik Sense hub, and it takes 20+ seconds to load the page. This occurs in a multi-node setup where one of the rim nodes is the designated Proxy node. Not an external load balancer issue as issue persists when Proxy is accessed directly. The standard out of the box Windows authentication pattern is used.
Environment:
- Qlik Sense Enterprise June 2019 and above.
We review the Qlik Sense Repository log files located in:
C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\<servername>_Audit_Proxy.txt
And locate the following lot entry during the delay:
Issued ticket 'tGU4LU1kfjC.r44h' for user, valid for 1 minute(s)
Further log reading shows:
Error connecting to capability service: Unable to connect to the remote server
Finally, the response is:
ProxyRequestType : Http | GET /api/capability/v1/list HTTP/1.1
If adding the time from the ticket was requested and the error message about capability service being down, plus the capability call response, adds up, the amount of the lag that the end user takes to get to see the hub, then issue could be because the Proxy's RIM is unable to get to central node via port 4900.
Reason for the delay:
The slightly simplified story is that the proxy changed the order in which it calls to the central node. Earlier it tried to get a session before fetching capabilities, but after the June 2019 release it is done capability first, get-session second, simply because get-session may depend on capabilities.
Reason Port 4900 is needed for capability service:
The broker is just forwarding call based on the URL (similar as the proxy does). If we take the external call done by hub-UI "GET /api/capability/v1/list" this goes to the proxy which sees the "/api" and forward that to the broker (port 4900) which see the "/capability" and forward that to the capability service (port 9301).
Resolution:
Verify if communication from Proxy node to Central node over port 4900 in available. Use PowerShell to check the port communication, read more under How To Check Open Ports Using PowerShell
According to help.qlik.com, port 4900 must be open inbound from Proxy RIM to Central node, read more here.
