Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Feb 8, 2023 4:02:48 AM
Nov 22, 2022 5:23:54 AM
After a recent Windows System Update and system restart, access to the Qlik Management Console (QMC) and hub is lost.
Example error:
ERR_CONNECTION_REFUSED
A problem has been identified following a server restart. This may happen regardless of whether Windows patches were installed or not. This is caused by the restart enabling IPv6 or changing the previous IPv6 address.
If, during the initial setup, Qlik Sense was not set up to allow connections to the repository database at all IPv6 addresses, the change to IPv6 or change of the address will lead to access being refused.
To allow all servers to access the repository database, modify the postgresql.conf file and use the ::/0 (for all IPv6 addresses).
For more information on configuring the postgresql.conf, see PostgreSQL: postgresql.conf and pg_hba.conf explained.
Qlik is investigating additional resolutions.
Disable IPv6 on the Network Card used by Qlik Sense.
This is caused by the restart enabling IPv6 or changing the previous IPv6 address.
If, during the initial setup, Qlik Sense was not set up to allow connections to the repository database at all IPv6 addresses, the change to IPv6 or change of the address will lead to access being refused.
We have also identified Microsoft Security upgrades which introduce the problem more frequently:
The currently suspected KBs* affecting Qlik Sense are:
KB5019081
KB5020619
KB5019966
KB5020615
*This list is not exhaustive and may be updated if more are identified.
Qlik Sense Enterprise on Windows
Another alternative solution is to add the IPv6-address (central node seems to be enough) to the pg_hba.config-file.
Update to my post: it should be the Link-local IPv6 Address (or ::0/0 to represent all IPv6 addresses).
Hello, has there been an update on the post above that doesnt involve a workaround? Thanks.
Hello @beckm
I have updated the article with additional informational and a more permanent solution that does not involve disabling IPv6 - as well as clarification on the root cause.
All the best,
Sonja