Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us at Qlik Connect 2026 in Orlando, April 13–15: Register Here!
cancel
Showing results for 
Search instead for 
Did you mean: 
AdnanRafiq1
Partner Ambassador
Partner Ambassador

Qlik Sense Nodes certficates currupted

Hi,

I have situation on Cluster environment on Qlik Sense. Currently its Windows 2022 (QS Nov 2024). 

There are 3 nodes on server, an I have this issue on Rim-Nodes usually happens every month when server restarts for any reason. Most of the time its windows update but sometime there is no update (windows updates turned off for some time).

The issue is recurring for more than year , and fix involves varying level of actions:

1. Level 1. have to recreate certificate and Re-register node

2. Level2: Repair Qliksense on RimNode and Re-register node

3. Reinstall QS on RIM node

The question is why that is happening? and how we can avoid it?

PS. Logged the case with Qlik but it was taking too long, so we decided to spin a new server. and Qlik Support is happy that its not production issue and closed it.

Any thoughts will really be appreciated.

 

Labels (1)
3 Replies
rubenmarin

Hi, I never found that issue, time to time on one server, but is very rare, maybe once each 2-3 years, and we managed different clusters.

I suppose you already did it, but... next time it happens try to get all the possible info before repairing it, qlik sense and windows logs.

Maybe it's an antivirus or something quarentining some critical files, check the exclussions on the links of this article: https://community.qlik.com/t5/Official-Support-Articles/Anti-virus-Endpoint-detection-and-response-a...

AdnanRafiq1
Partner Ambassador
Partner Ambassador
Author

Thanks Ruben,

Thanks a lot for your comments. I will investigate this angle next time that happens. Another thing I noticed was port 4570 get failure in Port Connection test. 

Infra teams maintains that they don't have any additional security and firewall rules indicates that port is open. 

 

ifytra
Contributor III
Contributor III

Hello there,

We faced a similar issue in specific nodes of a multi-node environment after upgrading to November 2025 version.

The workaround in our case was to apply Best Practices Template in IIS Crypto, reboot the server and redistribute the certificates to the specific nodes.