Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have a Qlik Sense server running, can access the Hub via my desktop machine. Whenever I try to open the Hub on my Ipad, I login successfully and then get a popup stating: "An error occurred" Connection lost. Make sure Qlik Sense is running.....
In QMC, I have added the server name (external, internal ip) to the Whitelist, but to no avail.
On an older Ipad (Version 3), I could access the Hub, but not on a Version 4 Ipad (neither on the internal browser, nor on the Chrome).
Any suggestions?
Thanks,
Martin
Hi Kristofer,
I am facing the same issue of running the application on Iphone /Ipads
Now please suggest me about the above discussion :
"You would need a signed certificate for the iPad to access the hub in SSL mode".
from where i can get this signed certificate.?
Please Assist
Thanks in advance
Hi Martin,
I tried using the follwing settings and now its working on every apple device.
Step - 1 Make Allow HTTP check box as True in QMC > Proxies
Step -2 Use Any other port except 80 , ( please ask the server admin to enable this new port on your server )
Step - 3 Put the IP in Whitelist in QMC > Virtual Proxies.
Restart the QMC
and its works
Hope you get the resolution. Cheers
Gaurav
What port did you switch to? Did you have to make any other changes?
thanks
Frank
Hi Frank,
I Tried with Port 82
My issues when connecting via an iPad (iOS 7.0.6) were that the Hub would display fine but apps would not load. This was due to my browser (Safari) being configured in private mode, preventing local data from being cached.
I disabled private mode and apps are now loading.
I have the same issue. did you get a solution ?
I'm deploying some app's on a website.
https://sites.google.com/view/genelabinsightmetadataanalysis/astrobiology-crosskingdom
They work on my computer but give security threats/ issues on other people computers.
In addition, on ipad's (latest model and iOS) the app's also do not load.
I've tried changing to HTTP, i've tried changing service listen port HTTP from 80 to 82...