Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.
I have one single user who is not able to access any apps due to the "Connection to the Qlik Sense engine failed for unspecified reasons" error. He is able to log in successfully, but as soon as he lands on the hub page he gets this message and is unable to proceed. This is the only user in our deployment that has ever reported this issue. I have not been able to replicate the error circumstances myself. The user works/lives remote so it's been a little challenging to troubleshoot this, but I have read and tried suggestions from several other posts on the issue.
The problem is I'm not finding anyone else who has experienced this issue for just one user only. Does anyone have any ideas for me?
I'm on Sense Feb 2019, I have the server address white listed in QMC, and all recommended ports open in my firewall rules. The user is on Windows 7/Google Chrome.
I have a similar problem: Same situation, same message as soon as the hub opens up.
Sense Feb 19, my user works from chrome and Safari on a Mac, but not from an iphone.
I made sure the phone has the latest ios, Safari and Chrome, but no luck.
Oh, and the QMC works just fine on the phone.
When this happens for one user, I agree, it can be a struggle to figure it out. Nonetheless, checkout this article https://support.qlik.com/articles/000036046 as it is often the solution for the broad case.
Consider changing their location using an RDP session to a known working browser on another machine. From there you can rule out the user itself and divide an conquer what variables remain (VPN, Browser, Proxy settings in a browser, etc...).
The development tools (network and console) on the browser could also lead to clues as to why it is failing.
Here is what worked for us:
Used http: instead of https: to access the hub from the iPhone.
In QMC, made sure "Allow HTTP" is turned on in the Ports section of the Central Proxy properties.
Since then, we've had no more issues.
Hope this helps!
The HTTP works for your iPhone would be correct for a condition where the Central Node does not contain Apple Certified certificates configured in the proxy security thumbprint. (ones IT support would could be contacted to add these in the central node)
But its also an interesting idea for troubleshooting whether HTTP vs HTTPS is a factor.