Access to Qlik Sense Server - error message but access!

[chrisg]

Hello everybody,

the customer would like to access the hub (or the QMC) directly on the Internet via his subdomain.
The server was set up by another service provider (but I can do everything myself
view in the QMC and view on the system - the SubDomain is entered in the whitelist)

Now I have behaved as follows:
1. The server can be reached on CHROME - and would like the login data.
  (Access via Safari brings an error message directly! )
2. I reach the HUB - I see all the APPs in the background but do not come across the error message

3. I can log on to the QMC with all rights, even though an error message appears !? Working on the QMC is possible without restrictions

Now my questions!

What's wrong here? where should I start?
How can it be that he lets me through despite the error message?
what are your important questions that I need to clarify?
Why isn't it on safari at all?
What do we need to change?

(There is no separate certificate stored in the Qlik Sense server - an error message (connection not secure) does not come either. The certificate that Safari draws is a generic one for the entire domain = * .domain.de.
Access via VPN works as expected)

best regards and many thx
Christoph

[chrisg]

Someone an idea? 

[ChotanaBI · Accepted solution]

Have tou checked the websockets? 

Try the Websocket connectivity tester for that

What's the error in the console using F12?

[chrisg]

Hi @ChotanaBI - many thx. 

That probably puts us on the right track! 

-----------------------------------------------------------
........ failed: Error during WebSocket handshake: Unexpected response code: 403
createSocket @ hub.js?1589806286714:1

Possibly unhandled rejection: {"isTrusted":true}
(anonymous) @ vendors.js?1589806286714:1

-----------------------------------------------------------
what could be the cause of this?

Many thx
Christoph

[ChotanaBI]

https://community.qlik.com/t5/Qlik-Support-Knowledge-Base/Qlik-Sense-Websocket-Connectivity-Tester/t...

[ChotanaBI]

https://www.youtube.com/watch?v=JmEGsdmaoC4&pbjreload=101

[ChotanaBI]

@chrisg  did it work?

[chrisg]

Hi @ChotanaBI ,
The hint with the websockets was the right hint. In addition, a few changes to the firewall were necessary. Thanks for the tipps.
Many Thx
Christoph

[matKa]

Hello @chrisg,

I have the same issue and it worked fine before. But after updating SSL certificate in Proxy the error appeared. Could you elaborate on what you had to change?