topic Qlik Sense Hub not opening up in App Development

Qlik Sense Hub not opening up

neerajthakur — Sat, 28 Mar 2026 08:13:33 GMT

Hi,

I have done a fresh installation of Qlik Sense Enterprise on Windows Nov 2025, and not able to open HUB by any means and getting Internal Server Error, QMC is working fine and have configured many things there to make it work. I have assigned all the roles to domain\user I am using it to open - Content, Admin, Hub etc.

I am able to open up apps I Imported through QMC, https://localhost/sense/app/....... Its opening up with this.

I have also set up two virtual proxies and wants one of them to become default instead of Central.

On comparing with other system which is working fine on another VM, I noticed in Nodes - Hostname is written in FQDN format i.e. host.analytics.local and on which I am working its just host, could this be a problem? and can we correct it without reinstallation?

I am using a Development License to set this server first and replace with Production License once it starts running as expected.

Re: Qlik Sense Hub not opening up

hugo_andrade — Mon, 06 Apr 2026 19:22:51 GMT

Good hunting @neerajthakur !

I like how you are thinking and trying to find the differences between existing environments.

If the nodes are showing that all services are running, the hostname is not an issue.

I would like you to check on the Virtual Proxy instead. There, you should see on the right "Advanced". MAke sure it's enabled.

Then, find the Host allow list option and confirm the hostname you are using is listed there. That is the #1 cause of the issue you are referring to. There, you can add the hostname, fqdn and any aliases/cname that are associated with the environment. Repeat that for the other virtual Proxies.

Re: Qlik Sense Hub not opening up

neerajthakur — Mon, 06 Apr 2026 21:58:25 GMT

Hi @hugo_andrade

Thanks for the reply, but since it was urgent, I made changes in to config files first but it didn't work out so reinstalled it, thankfully it was fresh and nothing hampered.

Only one problem lies from this post making one of my Virtual Proxies as default instead of Central. So that when mapped with DNS it can open like this:

https:analytics.site.com/analytic - and this open up the login page

analytic - here is one VP I am using and without it https:analytics.site.com it points to anonymous user