Skip to main content

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Qlik Cloud Maintenance is scheduled between March 27-30. Visit Qlik Cloud Status page for more details.

Internal Server Error when opening Hub

Showing results for 
Search instead for 
Did you mean: 

Internal Server Error when opening Hub

In QlikSense, Hub login page is accessible but issue happens after username and password is provided with the error message "Internal Server Error" displayed. Qlik Management Console (QMC) has no issues.



Qlik Sense Enterprise on Windows 


This can have multiple root causes. 


The Load Balancing URI

When looking into browser developer tool F12 it registers: (Save network web traffic (HAR/XML file) and console logs from the browser's developer tools)

"500 (Cannot get engine services from the load balancing module for the following app: __hub)"

Opening an app directly also says there is no engine available. Does not matter which user is login nor which app is opened.

Load balancing URI in virtual proxy used but not set up correctly

To resolve:

Remove/modify settings under QMC -> Virtual Proxies -> Edit virtual proxy -> Central -> Integration -> Load balancing module base URI

Settings depend on the 3rd party load balancer used.

Related content:

Load Balancing in Qlik Sense


Port 9028 not listening, wrong parameters configured

Verify the [hub.parameters].

  1. Stop the Qlik Sense Dispatcher Service
  2. Locate C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf
  3. Take a backup of the service.conf file
  4. Open the file and locate [hub.parameters]
  5. Locate and remove the following to parameters:
    • --high-dpi-support=1
    • --force-device-scale-factor=1
  6. Start the Service Dispatcher services once the changes are done.


Port 9028 was not listening because of the below two parameters present in C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf and under [hub.parameters] and save the confg file.


Port 4900 and 4747 not available

Reviewing the Proxy's Trace System_Proxy logs indicates an issue with connectivity on port 4900.
Reviewing the Proxy's Trace Audit_Proxy logs indicates an issue with WebSocket connectivity on port 4747.

These ports are used by Qlik Sense Engine and Blocking services. See Sense used Ports.

The result of the following commands indicate PIDs that are not of Qlik Sense services origin:

netstat -bano | findstr :4900
netstat -bano | findstr :4747


Third-party applications such as HFSQL / HyperFile use port 4900 which may cause conflicts. 
Note: Only port 4900 is documented to be used by HFSQL publicly.


Related Content

How to approach Qlik Sense Error 404 Not Found The following URL is unknown for Hub and QMC 
Qlik Sense - How to troubleshoot issue to access QMC and HUB  
How to approach Error 500 - Internal server error issue 

Labels (1)
Version history
Last update:
‎2021-05-26 09:29 AM
Updated by: