Qlik Community

Qlik Scalability

A group dedicated to advancing Qlik scalability and performance. In this group we will share knowledge on how to perform load tests of Qlik products.

Employee
Employee

Qlik Sense Scalability Tools Connection Troubleshooting Tips

I put together check lists as a help troubleshooting connection settings problems when using Qlik Sense Scalability Tools.

Using header auth

  1. Is the app published?
  2. Can you connect manually to the virtual proxy with header auth using modify header plugin in firefox, fiddler or similar.
    1. If it works, make sure the user which get logged in is the one from the header not your ntlm user.
    2. Can the header user access the app you want to simulate?
  3. If manual connection (1) with header works, make sure all these settings correspond to your tool settings
    1. VirtualProxyPrefix settings same as Prefix defined in QMC on the virtual proxy
    2. HeaderName same as Header authentication header name on the virtual proxy
    3. ConnectionType set to Header.
    4. Server is set to the same server name as the certificate, default fully qualified domain name, without defining protocol etc, i.e. myserver not https://myserver/hub.
    5. A default sense installation uses https and a self-signed certificate. Make sure the SSL checkbox is checked when using SSL or TLS (default) and the AllowUntrustedCertificate checkbox is checked if using the self-signed or any other “untrusted” certificate.
  4. If Connect to App doesn’t work, try doing a simple scenario of 1 user 1 iteration with only a small timerdelay in the scenario, then execute this using the executor (i.e. not connect to app). Does this get any errors?
  5. If you are getting license access denied, make sure the header users have an appropriate amount of tokens allocated.

Using NTLM auth

  1. Make sure the user has access to the app by manually connecting to it.
  2. If manual connection (1) with header works, make sure all these settings correspond to your tool settings
    1. VirtualProxyPrefix settings same as Prefix defined in QMC on the virtual proxy or blank if using root (default)
    2. ConnectionType set to NTLM.
    3. Server is set to the same server name as the certificate, default fully qualified domain name, without defining protocol etc, i.e. myserver not https://myserver/hub.
    4. A default sense installation uses https and a self-signed certificate. Make sure the SSL checkbox is checked when using SSL or TLS (default) and the AllowUntrustedCertificate checkbox is checked if using the self-signed or any other “untrusted” certificate.
  3. If Connect to App doesn’t work, try doing a simple scenario of 1 user 1 iteration with only a small timerdelay in the scenario. Does this get any errors?
  4. If you are getting license access denied, make sure the header users have an appropriate amount of tokens allocated.
Tags (1)
6 Replies
Highlighted
josefaria92
New Contributor III

Re: Qlik Sense Scalability Tools Connection Troubleshooting Tips

Hi, I have checked most of the troubleshooting tips

Still, I'm not able to connect to the App Structure, please give me some guidance, I have no idea what I can do more or how to spot the error I'm making.

Message error: Failed to get app structure. Failed to connect to the app

Some context & actions already performed:

- client server I setup the Scalability tool has other software running (Amazon cloud machine)

- I have a Nginx reverse proxy in front of Qlik Sense (Amazon)

- QMC and Hub in a Amazon Cloud Server as well, all three in different machines

- My certificate (dunno why) are untrusted by I exported from QMC and I'm calling them on Nginx configuration

Trial and error based on community suggestions:

- I can make the manually header authentication

     * Virtual Proxy works

     * Tokens are automatically assigned for user

- I have tried to change the ports of the proxy to 81 in QMC and Client but no different result (didn't touch into Nginx config)

- Tried NTLM as well (didn't touch into Nginx config only scalability interface)

Personal background and Experience:

- I'm new into this topic's of back end config, probably some rookie mistake, as well some bad terminology use in the description.

I'm currently lost on this topic any details or specifics missing for troubleshooting let me know so I can describe them.

Error - Failed to connect.png

Highlighted
Employee
Employee

Re: Qlik Sense Scalability Tools Connection Troubleshooting Tips

I would assume it has something to do with putting nginx inbetween. The tool will add a header with the simulated user according to settings. In your case the header X-QLIK-HEADER-NAME with the first username of Exerciser_1 as it looks like. is this header properly sent through to the sense server?

Can you try doing this part?

4. If Connect to App doesn’t work, try doing a simple scenario of 1 user 1 iteration with only a small timerdelay in the scenario. Does this get any errors?

Highlighted
josefaria92
New Contributor III

Re: Qlik Sense Scalability Tools Connection Troubleshooting Tips

Hi Daniel,

Thank you for replying, I reviewed the check list for authentication header.

Using header auth

  1. Check
  2. Check
  3. Manual connection - check
    1. Check
    2. Check
    3. Check
    4. Which certificate? SSL I have used in the Nginx Reverse Proxy? Is the IP address enough?
    5. Check
  4. Done – Same message as the picture "Failed to get the App Structure"
  5. Checked, Tokens allocated successfully
Highlighted
Employee
Employee

Re: Qlik Sense Scalability Tools Connection Troubleshooting Tips

I rewrote to bullet 4 to make it a bit clearer what I meant. Changing concurrentusers and iterations won't make a difference for the connect app as it will only use one user anyway. So what I meant was to run it through the executor, which should give a different error message, which might or might not help us.

When doing the manual connection. Did you use a header modifying plugin, setting the header and user according to your settings (i.e. in your specific case X-QLIK-HEADER-NAME : excerciser_1). Then did it show has the user exerciser_1 logged in, and the app showing up in the hub?

Highlighted
josefaria92
New Contributor III

Re: Qlik Sense Scalability Tools Connection Troubleshooting Tips

Ok, based on your guidance we have a different error:

- I add a scenario

scenario.png

- I used the same user as the manual authentication (using the header changer - an Chrome extension) and gave me on the executor the following error:

09:00:52 Workers:0 Errors:0 Warnings:0 Requests:0 Sessions:0

09:00:52   Illegal user id: some-domain\some-user\nParameter name: headerUserId

09:01:02 Workers:0 Errors:1 Warnings:0 Requests:0 Sessions:1

Test Execution Finished.

WarningCount: 0

ErrorCount: 1

Finishing writing logs...

this was done on test Client server, I'll try to repeat it on my personal computer to see if I get the same error message. It's really weird this having different results with the same properties...

Cheers Daniel

Highlighted
josefaria92
New Contributor III

Re: Qlik Sense Scalability Tools Connection Troubleshooting Tips

Problem solved:

The issue was with dynamic header expression " $ud\\$id " was blocking the authentication, I have added the double "\\" on the user and still didn't manage to authenticate.

Once I changed to " $id@$ud " and edited on Scalability tool the user equally, I manage to connect with the app.

Conclusion: Do not use " $ud\\$id " it seems it needs a specific configuration or might getting in conflict with my Reverse Proxy that I have in front of Qlik Sense machine.