Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Knowledge
Qlik Sense - Binding to IPv6 Only
Article Number: 000059278 | Last Modified: 2019/10/23Description
Environment:
Qlik Sense June 2017 or Higher
With Qlik Sense, some services and activities may fail due to the Qlik Sense Repository Database and Qlik Sense Repository Service inability to successfully communicate between nodes of Qlik Sense installation.
One example of this being able to send certificates over port 4444.
The primary symptom of this behavior is when using netstat -ano reveal services only listening on IPv6.
If you find that a service is failing due to use of IPv6, then a specific Operating System changes may be required.
Qlik Sense June 2017 or Higher
With Qlik Sense, some services and activities may fail due to the Qlik Sense Repository Database and Qlik Sense Repository Service inability to successfully communicate between nodes of Qlik Sense installation.
One example of this being able to send certificates over port 4444.
The primary symptom of this behavior is when using netstat -ano reveal services only listening on IPv6.
If you find that a service is failing due to use of IPv6, then a specific Operating System changes may be required.
Resolution
- Click the Windows Start button.
- In the Start Menu, either in the Run box or the Search box, type regedit and press Enter.
- If prompted by User Account Control, click Yes to open the Registry Editor.
- The Windows Registry Editor window should open and look similar to the example shown below.
- Navigate to HKey_Local_Machine\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
- Look for entry for ListenOnlyList.
- Remove this Key.
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us