Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.
The QMC and the Hub portal was up and running until a recent change. In the QMC, we added a new Win AD group and since then we are getting the below error message whenever we try to access the admin console. We are unable to go to QMC and undo the change. We have followed a couple of solutions from the forums and the qlik articles, but still no luck. Did anyone have similar issue? Please advise how can I go about troubleshooting and fixing this issue?
I am little new to the qliksense work.
I appreciate your responses.
The website declined to show this webpage
Most likely causes:
What you can try:
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help.
l There are too many root certificates on the computer (> ~300), and as a consequence, the Qlik
Senseservices are not allowed to communicate.
l You are trying to access a resource that you are not granted access to, according to the rule engine in
Remove any unused root certificates. See also the following Microsoft help documentation:
≤ SSL/TLS communication problems after you install KB 931125
You can set your user to "delete prohibited" and thereby avoid the problem with your user getting deleted.
We use LDAP filters now and they are working as expected.
I cannot do that, but I would recommend that you check out this post as it shows you how to build a LDAP filter:
I had the same issue after changing the LDAP filter.
You can log in to the QCM with the Qlik Sense Service User (By default it should be "qs_admin"). Than you correct the LDAP filter, sync and the problem should be gone.
You can also open a remote desktop connection to the Qlik Sense Sever using the Qlik Sense Service User. (The user is member of the group "Qlik Sense Service User", if you don't know the name.) And then you open the QMC directly on the server. Than you correct the LDAP filter, sync and the problem should be gone.