QMC and HUB not accessable after installation - only with localhost

[andreas_schoedlbauer]

Hi guys, we have a very special problem for the dedectives among us 🙂

We installed Qlik Sense Enterprise on a VM using the CNAME qlik-dev.ad.ourdomain.de. Everything lookes fine after installation. Services are running under the service account. Ports are open, Qliks certificates are correct.

When using localhost/qmc or hub, logged in with the service account, everything works fine but no authentication window appears.

When using qlik-dev.ad.ourdomain.de/qmc or hub or even localhost in incognito mode the windows authentication window appers but after entering the correct user/password the attached ERR_UNEXPECTED appears.

Has anyone of you experienced a problem like that?

Kind regards, Andy

Qlik Sense Enterprise on Windows 

[rubenmarin]

Hi, I have found similar error when the url doesn't match the computer name, I thougth (just a guessing) it is caused by the query exiting the computer and returning by the same port, causing the conflict, it only happens on the server, so from outside I can use the full url, and from server I can use localhost, so I didn't dedicated the time to check if it's solvable

[andreas_schoedlbauer]

Thanks for your update. We also face the problem from outside. The only adress working is directly from the server on localhost/qmc. All other - no matter if directly on the server or from outside - fail.

[rubenmarin]

Hi, can you check on virutal proxies -> Advanced -> the url (qlik-dev.ad.ourdomain.de) is included in the host allow list

[andreas_schoedlbauer]

Hi, yes it is. We tried different ways. Installing with the computername and also installing with the cname and put every adress in the host allow list. Did not work. Seems like qlik does not reach the auth module (windows server 2022). We also tried with forms authentication but did not work either.

[rubenmarin · Accepted solution]

In c:\ProgramData\Qlik\Sense\Log you can check if any log is registering any error, try first with the proxy folder, but maybe it is on the repository folder.

You can also check windows event log to check if any error is being logged.

You can try stopping all services and starting all of them to have clean logs since the server session start, try to open the qmc and then check the logs looking for something more specific that 'unexpected'.