Skip to main content
Announcements
See why Qlik is a Leader in the 2024 Gartner® Magic Quadrant™ for Analytics & BI Platforms. Download Now
cancel
Showing results for 
Search instead for 
Did you mean: 
LuigiA
Contributor II
Contributor II

Hub in HTTP not working on Edge and Chrom, fine on Firefox

Hello,

we currently have an old installation of QlikSense 2019 that works fine, but we decided to upgrade and deploy a new installation with the most recent version : QlikSense 2024 February Patch 3 14.173.6

Everything works fine when we use HTTPS , but for internal reasons we have to allow HTTP connection.

Unfortunately, the HTTP works perfectly fine in Firefox, but does not work in Edge and Chrome: in both browsers, the hub loads , apparently in a correct way, but after a second it gives a Connection closed error and keeps reloading indefinetely showing the error every time.

Do you have any idea how this could be fixed?

 

Thanks a lot

Labels (1)
6 Replies
mpc
Partner - Specialist
Partner - Specialist

Hi, 

Can you check and share if an error is displayed in the console web browser (press f12) to display it ? 
Can you share the Proxy logs too ? 

Kind regards

From MPC (and Next Decision) with love
LuigiA
Contributor II
Contributor II
Author

In Microsoft Edge I can see an error on every reload attempt, but immediatly deletes it. Howether when it stops trying to reload in the console i have this error

vendors.js?1710231671455:1 TypeError: Cannot set properties of undefined (setting 'navActive')
at Object.closeNav (hub.js?1710231671455:1:404503)
at hub.js?1710231671455:1:253899
at o.$digest (vendors.js?1710231671455:1:194178)
at o.$apply (vendors.js?1710231671455:1:196043)
at vendors.js?1710231671455:1:159864
at $ (vendors.js?1710231671455:1:162762)
at f.onload (vendors.js?1710231671455:1:162226)
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
$apply @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$ @ vendors.js?1710231671455:1
f.onload @ vendors.js?1710231671455:1
load (async)
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
$apply @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$ @ vendors.js?1710231671455:1
f.onload @ vendors.js?1710231671455:1
load (async)
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
$apply @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$ @ vendors.js?1710231671455:1
f.onload @ vendors.js?1710231671455:1
load (async)
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
$apply @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$ @ vendors.js?1710231671455:1
f.onload @ vendors.js?1710231671455:1
load (async)
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
completeTask @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
setTimeout (async)
s.defer @ vendors.js?1710231671455:1
$evalAsync @ vendors.js?1710231671455:1
$observe @ vendors.js?1710231671455:1
(anonimo) @ hub.js?1710231671455:1
e @ vendors.js?1710231671455:1
t @ vendors.js?1710231671455:1
setTimeout (async)
(anonimo) @ vendors.js?1710231671455:1
a @ vendors.js?1710231671455:1
fireWith @ vendors.js?1710231671455:1
fire @ vendors.js?1710231671455:1
a @ vendors.js?1710231671455:1
fireWith @ vendors.js?1710231671455:1
s.<computed> @ vendors.js?1710231671455:1
(anonimo) @ hub.js?1710231671455:1
(anonimo) @ hub.js?1710231671455:1
execCb @ require.js?1710231671455:1
check @ require.js?1710231671455:1
(anonimo) @ require.js?1710231671455:1
(anonimo) @ require.js?1710231671455:1
(anonimo) @ require.js?1710231671455:1
each @ require.js?1710231671455:1
emit @ require.js?1710231671455:1
check @ require.js?1710231671455:1
enable @ require.js?1710231671455:1
init @ require.js?1710231671455:1
a @ require.js?1710231671455:1
completeLoad @ require.js?1710231671455:1
onScriptLoad @ require.js?1710231671455:1
load (async)
req.load @ require.js?1710231671455:1
load @ require.js?1710231671455:1
load @ require.js?1710231671455:1
fetch @ require.js?1710231671455:1
check @ require.js?1710231671455:1
enable @ require.js?1710231671455:1
enable @ require.js?1710231671455:1
(anonimo) @ require.js?1710231671455:1
(anonimo) @ require.js?1710231671455:1
each @ require.js?1710231671455:1
enable @ require.js?1710231671455:1
init @ require.js?1710231671455:1
(anonimo) @ require.js?1710231671455:1
setTimeout (async)
req.nextTick @ require.js?1710231671455:1
s @ require.js?1710231671455:1
e @ hub.js?1710231671455:1
setup @ hub.js?1710231671455:1
(anonimo) @ hub.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
completeTask @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
setTimeout (async)
s.defer @ vendors.js?1710231671455:1
$evalAsync @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
f @ vendors.js?1710231671455:1
t @ vendors.js?1710231671455:1
p @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
o @ vendors.js?1710231671455:1
(anonimo) @ vendors.js?1710231671455:1
dragomanClosure.webpackJsonp_name_ @ vendors.js?1710231671455:1
(anonimo) @ en-cd1ba64f0de8e760ad8f.js:1

[NEW] Explain Console errors by using Copilot in Edge: click
to explain an error.
Learn more
Don't show again
5vendors.js?1710231671455:1 Error: Socket closed
at p (enigma.js?1710231671455:1:6523)
at t.value (enigma.js?1710231671455:1:17963) 'Possibly unhandled rejection: {"code":-1,"enigmaError":true,"original":{"isTrusted":true}}'

 

LuigiA
Contributor II
Contributor II
Author

For the Proxy, which of the various file would you need? Apparently, I can't find any error, just a series of User Authnticated / User got ticket for session repeated.

mpc
Partner - Specialist
Partner - Specialist

Ok, I think the info we need are in the audit logs, in the ArchivedLogs folder in the last file per exemple. 

Can you try in Chrome too ? The erro isn't explicit att all in Edge

Maybe it's a websocket issue, you can check that here: https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Websocket-Connectivity-Tester/ta-...

 

From MPC (and Next Decision) with love
LuigiA
Contributor II
Contributor II
Author

It looks similar on Chrome

vendors.js?1710231671455:1 Error: Socket closed
at p (enigma.js?1710231671455:1:6523)
at t.value (enigma.js?1710231671455:1:17963) 'Possibly unhandled rejection: {"code":-1,"enigmaError":true,"original":{"isTrusted":true}}'
(anonime) @ vendors.js?1710231671455:1
(anonime) @ vendors.js?1710231671455:1
d @ vendors.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
$apply @ vendors.js?1710231671455:1
(anonime) @ vendors.js?1710231671455:1
completeTask @ vendors.js?1710231671455:1
(anonime) @ vendors.js?1710231671455:1
setTimeout (asinc)
s.defer @ vendors.js?1710231671455:1
e @ vendors.js?1710231671455:1
f.controller @ vendors.js?1710231671455:1
instantiate @ vendors.js?1710231671455:1
(anonime) @ vendors.js?1710231671455:1
(anonime) @ hub.js?1710231671455:1
$digest @ vendors.js?1710231671455:1
$apply @ vendors.js?1710231671455:1
u @ vendors.js?1710231671455:1
n.show @ vendors.js?1710231671455:1
show @ vendors.js?1710231671455:1
show @ hub.js?1710231671455:1
n.showAlert @ hub.js?1710231671455:1
c @ hub.js?1710231671455:1
n.emit @ enigma.js?1710231671455:1
value @ enigma.js?1710231671455:1
n.emit @ enigma.js?1710231671455:1
value @ enigma.js?1710231671455:1
vendors.js?1710231671455:1 Possibly unhandled rejection: {"code":-1,"message":""}

 

mpc
Partner - Specialist
Partner - Specialist

It really seems to be a Websocket related issue, you can try to follow the dedicated post: https://community.qlik.com/t5/Official-Support-Articles/How-to-troubleshoot-web-socket-issue-for-Qli...

 

From MPC (and Next Decision) with love