Qlik Alerting Configuration Issue - Socket Closed/Internal Server Error

[KR_M]

Hello Experts,

I am configuring a new Qlik Alerting installation . As a part of that I installed Alerting in a separate server. And when I try to make connected to my QLik Sence i get following errors:

Not Connected, Socket Closed, Internal Server Error.

There is no blockage on firewall, all the ports are open. Not sure on what i need to check.

Could you please provide me some steps on how to debug this issue.

Many Thanks!

I exported the certificated and 

[Anil_Babu_Samineni]

Can you check If 9220 also enabled firewall from Qlik Alerting to Central node?

[KR_M]

There is no blockage in firewall. 

The installation and configuration is successful but unable to retrieve users from QLIK Sense . I saw that the QS license is not updated in Alerting setup file. Any idea on this?

My QS has the Alerting license included in it. Can we manually update the license any where in the Qlik Alerting server?

[asmitamkhrj]

Facing the same issue, tried to recreate SSL certificate, did not help. 

[Lucas_Gatling]

What version of Alerting do you have installed?

Take a look at this Alerting video: https://www.youtube.com/watch?v=nNrVFJB9wyo&t=1179s

[Deepakdk]

Anyone was able to resolve the issue ? We are facing the same issue.

[HeshamKhja1]

Hi, to resolve socket closed error you have to make sure these are done:

1. Ports are open from Qlik Alerting to Qlik Sense 443, 4242, 4243, 9200.
2. The correct proxy address is entered.
3. The user is root admin on Qlik Sense and has a valid license (Professional or Analyzer license).

I encountered this error missing point 3.