Qlik Community

Ask a Question

Knowledge Base

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

Live chat with experts, bring your API Integration questions. June 15th, 10 AM ET. REGISTER TODAY

Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized)


Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized)

Reload failed and in Script log shows error:

Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized):
Requested resource requires authentication.
Execution Failed
Execution finished.

  QlikSense all versions


Refer to manual: https://help.qlik.com/en-US/sense/Subsystems/Monitoring/Content/Troubleshooting/troubleshooting-moni...


Possible cause  

The proxy's HTTPS port has been customized but the data connections have not been updated to match this port, a prefix was added to a virtual proxy but the data connections were not updated to match, or in multi-node the reload node where the monitoring apps are reloaded does not have any proxy set up.



Check every " qrs_* " (pre- June 2017 version) OR "monitor_apps*" (June 2017 and newer versions) connection in QMC -> Data Connections

In versions previous to June 2017 (such as 3.2.5 and older), Data connections affected include the following:

  • qrs_app
  • qrs_appobject
  • qrs_event
  • qrs_licenseSummary
  • qrs_loginAccess
  • qrs_task
  • qrs_user
  • qrs_userAccess

In June 2017 and newer versions, "qrs_*" data connections were renamed to "monitor_apps_rest_*"... these need to be modified instead.

  • monitor_apps_REST_app
  • monitor_apps_REST_appobject
  • monitor_apps_REST_event
  • monitor_apps_REST_license_access
  • monitor_apps_REST_license_login
  • monitor_apps_REST_license_user
  • monitor_apps_REST_task
  • monitor_apps_REST_user

Make sure that the URL used to connect to Qlik Rest Connector can be resolved for the node it is reloaded on. 

It is recommended to use either localhost (if reloaded on same machine) or the central node FQDN. Using the FQDN in every data connection is preferred.

Note that by default Operation Monitor and License Monitor are only reloaded on the central node.

Labels (1)
Version history
Revision #:
4 of 4
Last update:
‎2020-08-24 06:50 AM
Updated by: