topic Re: Is Qlik Branch not working? in Integration, Extension & APIs

Is Qlik Branch not working?

Wed, 13 Jan 2016 11:48:05 GMT

Hello all,

For the last couple of weeks I've been trying to access Qlik Branch, but since the last webpage update I've been unable to see the projects. It appears to be loading all the time:

Is this happening to anyone else? I also can't access the Forum so I really don't know where else to ask.

Thank you very much,

Joan

Re: Is Qlik Branch not working?

Alexander_Thor — Wed, 13 Jan 2016 12:08:55 GMT

It should be up and running.

What browser are you running?

Re: Is Qlik Branch not working?

Wed, 13 Jan 2016 12:19:37 GMT

Google Chrome, latest version ( 47.0...).

Re: Is Qlik Branch not working?

Wed, 13 Jan 2016 13:54:02 GMT

Hello all,

At this moment I experience the same issue. I tried with different navigators but still the same result.

Re: Is Qlik Branch not working?

Alexander_Thor — Wed, 13 Jan 2016 15:32:08 GMT

Hmm strange, try to just empty our your cache and cookies

Re: Is Qlik Branch not working?

Alexander_Thor — Wed, 13 Jan 2016 15:33:00 GMT

Try emptying our your cookies and cache. Also pop open the console and see if there are any error messages there, usually F12 in your browser.

Re: Is Qlik Branch not working?

Wed, 13 Jan 2016 15:47:00 GMT

Hi Alexander,

I tried it as you suggested: cleaning my cookies and checking the possible error messages but the issue continues. I tried with Internet Explorer 11, Mozilla Fierfox and Chrome v46 but nothing happens.

Kind regards.

Re: Is Qlik Branch not working?

Alexander_Thor — Wed, 13 Jan 2016 22:01:48 GMT

If you browse to websocket.org Echo Test - Powered by Kaazing and try to connect and send a request. Does that work for you? Something is blocking websockets on your end as the site is up and running.

Re: Is Qlik Branch not working?

Thu, 14 Jan 2016 06:31:26 GMT

Hi Alexander,

I checked the socket connection as you suggested and it works correctly. However the message given by chrome about the socket connection is a timeout:

" qsocks.bundle.js:2738 WebSocket connection to 'wss://branch.qlik.com/anon/app/9573041f-0c45-4cb6-8166-64c2aac3c05d' failed: Error in connection establishment: net::ERR_TIMED_OUT "

I checked my firewall and other security options but none of them are blocking the connection.

Thanks.

Re: Is Qlik Branch not working?

Thu, 14 Jan 2016 08:30:02 GMT

Cleaning my cookies and caché didn't work for me as well, but when I open the console I get the following message, so I'm guessing it is a problem with the websockets:

WebSocket connection to 'wss://branch.qlik.com/anon/app/9573041f-0c45-4cb6-8166-64c2aac3c05d' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT

Do you have any idea of how I could solve this issue?

Thanks

Re: Is Qlik Branch not working?

Fri, 15 Jan 2016 10:30:31 GMT

I have the exact same problem, I have tried it on multiple browsers and it won't work.

Re: Is Qlik Branch not working?

Brian_Munz — Fri, 15 Jan 2016 13:40:10 GMT

Are you still experiencing this problem?

Re: Is Qlik Branch not working?

rbecher — Fri, 15 Jan 2016 13:43:18 GMT

same to me..

Re: Is Qlik Branch not working?

Fri, 15 Jan 2016 13:45:01 GMT

Hi Brian,

Yes, the issue continues. However now I tried with my smartphone (android) and it works. I don't know why it happens

Thanks.

Re: Is Qlik Branch not working?

kevincase — Mon, 25 Jan 2016 16:49:04 GMT

I believe that the issue has to do with a proxy server. I had the same issue but after turning off the proxy in IE, the page loads fine. With the proxy server enabled, the page does not load.

Re: Is Qlik Branch not working?

Alexander_Thor — Mon, 25 Jan 2016 17:02:06 GMT

Yes, Branch (and Qlik Sense which powers Branch) relies on WebSockets.

If the search page hangs it usually due to,

You are using a browser which does not support websockets all though Branch should tell you if that was the case.
You are using a connection with a proxy that does not support websocket passthrough. Can be common in certain old enterprise proxy scripts
Your ISP is blocking websockets, this is very rare but we have heard reports from Australia for example where certain cellular network providers block websockets.