How to Use Qlik Alerting Windows with HTTP Protocol?

[zolbae]

Hello,
I am using Qlik Alerting 2024 Nov SR1 on a Windows Server 2016 environment and I am trying to run it using the HTTP protocol. Despite trying several approaches, I haven’t been able to get it working, so I am reaching out for assistance.

Environment:

• Qlik Alerting Version: 2024 Nov SR1
• OS: Windows Server 2016
• Node.js: 20.17
• MongoDB: 6.0.17

Objective:

• Service URL: I want to use the HTTP protocol and access the service with an IP address like http://192.168.0.239:4551/#/login/.

What I Have Tried:

1. Editing the default.json file

   • I’ve modified the C:\Program Files\Qlik Alerting\config\default.json file, but nothing worked.
   • HSTS Settings: Tried setting hstsMaxAge to 0 ( or 31536000)
   • Gateway Settings: Changed localhost to the actual IP address.
     • "https": false
     • "trustProxy": 1 ( or o )
   • allowInsecure Settings: Added "allowInsecure": { "http": false, "TLSv1": false, "TLSv1_1": false, "TLSv1_2": true }.

2. Clean Reinstall

   • I uninstalled Qlik Alerting and MongoDB completely, and did several clean installations. Unfortunately, the issue persists.

Current Situation:

• I can access the service via http://localhost:4551, but for integration with Qlik Sense or access from clients, I cannot use localhost.
  • 127.0.0.1 works, but external IPs or domain names do not work.
• Issue Observed:
  • When I initially call the URL, the network tools show that static files are being loaded, but the address changes. For example, when calling http://192.168.0.239:4551/, it switches to https://192.168.0.239:4551/static/js/main.ea39ec04.js, causing an error.
  • Console error:
    GET https://192.168.0.239:4551/static/css/main.bde10e2a.css net::ERR_SSL_PROTOCOL_ERROR 192.168.0.239/:1

    
     

Request:

If anyone has experience running Qlik Alerting with HTTP protocol and IP address, I would really appreciate your help or suggestions on how to make this work.

Thank you!

[Frank_S]

Hello,

Check to ensure you have met all the requirements, tested the components therein, configured firewall settings and accurately exported the certificates. 
Each of these and many more critical requirements are covered in detail in the help page below.

https://help.qlik.com/en-US/alerting/November2024/Content/QlikAlerting/installation-prerequisites.ht...

Should you need detailed assistance in setting up your environment should you continue to observe your setup issues. Please consider contacting your Qlik Account manager who can arrange a professional services engagement to iterate with you directly to implement your Qlik Alerting Environment.

Kind regards...

[zolbae]

Thanks for the reply Frank.

I checked all the details in the official link,

and in my case, it is a basic error that goes way before Qlik Sense can communicate, so I don't think it is something that requires complex requirements.

Can you tell me what kind of service participation is involved and how to do it by asking the Qlik account manager you mentioned?

[AntonioC]

Have you found any solution to this?

[zolbae]

Unfortunately no.

I created a self-signed SSL and used the https protocol.

[AntonioC]

Have you tried removing the text ","upgrade-insecure-requests":[]" from the file "C:\Program Files\Qlik Alerting\gateway\server.js"?