topic Re: QV11 Plug-in mixed content error in QlikView

QV11 Plug-in mixed content error

rothtd — Mon, 26 Jan 2026 18:19:17 GMT

I have QV11 SR2 deployed using IIS, QVS is clustered and a F5 load balancer is out in front. When I hit my QVWs with the IE Plug-in I get the ‘Mixed Content’ error message (AJAX does not display this message).

I noticed that if (using the plugin) I set the browser to http://<servername>/qlikview I do not get the mixed content error, while I do get it when browse to https://<servername>/qlikview or http://<loadbalancer>/qlikview.

Questions:

Are there any special configuration settings I need to be aware of on the load balancer? I noticed that my infrastructure team set the load balancer to redirect from http to https – might this be causing problems with the plug-in?

Also, when I run a netstat on my machine I can see a port open to my QVS on 4747 – my infrastructure team is doubting this and telling me that communication is happening on 80/443. My understanding is that when I use the plug-in all communication is happening on 4747 / 4774 – is this correct?

Any thoughts on next steps in troubleshooting this?

Thanks in advance!

Re: QV11 Plug-in mixed content error

danielrozental — Tue, 16 Oct 2012 19:48:01 GMT

Are you working with QV11 SR2? someone posted a similar error a few months back.

http://community.qlik.com/message/228592#228592

Also, have you checked the certificate?

Re: QV11 Plug-in mixed content error

rothtd — Tue, 16 Oct 2012 20:05:34 GMT

I did see the thread you listed - and many others. None seemed to help unfortunately. We are on QV11 SR2. When you stated to 'check the certificate' what would I be looking for specifically? I only get the issue when I'm using the plug-in (AJAX is fine) so what would be different about the cert when using the plug-in vs. AJAX?

Thanks in advance!

Re: QV11 Plug-in mixed content error

danielrozental — Tue, 16 Oct 2012 20:26:51 GMT

Using HTTP you don't get the error even if you're not getting through the load balancer? Why is HTTP even responding then?

Sorry, I'm not really a specialist in Webservers or SSL but I believe certificates could be issued to a single domain or to a subdomain, are you getting the same behaviour out of both servers when accessed directly?