<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Urgent Issue: License Synchronization Failure After Public IP Change - License Key: 1230 4250 1407 9635 in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531219#M32233</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I don't think Qlik whitelists customer's IP addresses. Most of our customers don't have public IP's.&lt;/P&gt;&lt;P&gt;Can you telnet to license.qlikcloud.com on tcp443 from the qliksense server.&lt;/P&gt;&lt;P&gt;The licensing page will also show last successful update.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Sep 2025 09:39:22 GMT</pubDate>
    <dc:creator>SivenM2020</dc:creator>
    <dc:date>2025-09-18T09:39:22Z</dc:date>
    <item>
      <title>Urgent Issue: License Synchronization Failure After Public IP Change - License Key: 1230 4250 1407 9635</title>
      <link>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531216#M32232</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Qlik Support Team,&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;We are writing to report an urgent issue regarding our Qlik Sense license (Key: &lt;CODE&gt;1230 4250 1407 9635&lt;/CODE&gt;). Our system has been failing to synchronize the license since &lt;STRONG&gt;September 17, 2025&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;This issue started immediately after a planned change of our company's public-facing IP address. We have conducted a thorough investigation, and all evidence strongly suggests that the Qlik License Service is rejecting requests from our new IP because it is not whitelisted for our license key.&lt;/P&gt;
&lt;P&gt;Here is a summary of our findings:&lt;/P&gt;
&lt;OL start="1"&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Application Log Evidence:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Our service logs have changed from a successful &lt;CODE&gt;"message":"updated license"&lt;/CODE&gt; on Sept 10 to a persistent &lt;CODE&gt;"message":"failed to sync"&lt;/CODE&gt; error since Sept 17.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;A key error log entry shows: &lt;CODE&gt;{"error":"Patch '&lt;A href="https://license.qlikcloud.com/v1/assignments" target="_blank" rel="noopener"&gt;https://license.qlikcloud.com/v1/assignments&lt;/A&gt;': OK", "level":"error"}&lt;/CODE&gt;. This indicates that while our server can establish a basic HTTP connection to your endpoint (receiving an "OK" status), the license assignment transaction itself is being rejected at the business logic level.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Network Packet Analysis:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;
&lt;P&gt;Packet captures confirm that connections to some of your IPs are successful. However, connections to your server at IP &lt;CODE&gt;3.219.17.6&lt;/CODE&gt; are being immediately terminated by a &lt;STRONG&gt;TCP Reset (RST)&lt;/STRONG&gt; packet right after the 3-way handshake completes.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;This TCP RST behavior occurs &lt;I&gt;before&lt;/I&gt; any TLS negotiation and is a strong indicator of an IP-based filtering rule or firewall policy on your end.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Based on this evidence, we are confident that the root cause is our license key being bound to our old public IP address.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Our request is simple:&lt;/STRONG&gt; Could you please check the IP address(es) registered to our license key (&lt;CODE&gt;1230 4250 1407 9635&lt;/CODE&gt;) and update your system to authorize requests from our new public IP?&lt;/P&gt;
&lt;P&gt;We are available to provide the full logs and packet capture files if needed. Your prompt attention to this matter is greatly appreciated as this is impacting our operations.&lt;/P&gt;
&lt;P&gt;A proxy Server Success&lt;BR /&gt;{"active":true,"caller":"update.go:64","checksum":"YK6L-RQF3-U9FS-ZM98-VJL8","level":"info","license":"1230 4250 1407 9635","logTraceId":"899d0893d1f55c841d6f6bc45a28c753","message":"updated license","timestamp":"2025-09-10T08:33:54.9558234Z"}&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;B proxy Server failed&lt;BR /&gt;{"caller":"sync.go:101","error":"Patch \"&lt;A href="https://license.qlikcloud.com/v1/assignments\" target="_blank" rel="noopener"&gt;https://license.qlikcloud.com/v1/assignments\&lt;/A&gt;": OK","level":"error","license":"1230 4250 1407 9635","logTraceId":"3fc2e2a2b87bce1475d361a1171922da","message":"failed to sync","timestamp":"2025-09-17T07:46:13.5652187Z"}&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:35:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531216#M32232</guid>
      <dc:creator>RonaldChin</dc:creator>
      <dc:date>2025-09-18T09:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent Issue: License Synchronization Failure After Public IP Change - License Key: 1230 4250 1407 9635</title>
      <link>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531219#M32233</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I don't think Qlik whitelists customer's IP addresses. Most of our customers don't have public IP's.&lt;/P&gt;&lt;P&gt;Can you telnet to license.qlikcloud.com on tcp443 from the qliksense server.&lt;/P&gt;&lt;P&gt;The licensing page will also show last successful update.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:39:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531219#M32233</guid>
      <dc:creator>SivenM2020</dc:creator>
      <dc:date>2025-09-18T09:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent Issue: License Synchronization Failure After Public IP Change - License Key: 1230 4250 1407 9635</title>
      <link>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531220#M32234</link>
      <description>&lt;P&gt;Thank you for your reply and suggestions.&lt;/P&gt;
&lt;P&gt;While we understand that IP whitelisting may not be a standard procedure for all customers, our troubleshooting results strongly point to this as the root cause in our specific case. We have a critical piece of information from our recent tests that isolates the issue down to the public IP.&lt;/P&gt;
&lt;P&gt;We conducted an A/B test using two different proxy servers:&lt;/P&gt;
&lt;OL start="1"&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Old Setup (Working):&lt;/STRONG&gt; Qlik Server -&amp;gt; Old Proxy (Brocade) -&amp;gt; &lt;STRONG&gt;Old Public IP&lt;/STRONG&gt; -&amp;gt; License sync with &lt;CODE&gt;license.qlikcloud.com&lt;/CODE&gt; was &lt;STRONG&gt;SUCCESSFUL&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;New Setup (Failing):&lt;/STRONG&gt; Qlik Server -&amp;gt; New Proxy (FortiProxy) -&amp;gt; &lt;STRONG&gt;New Public IP&lt;/STRONG&gt; -&amp;gt; License sync with &lt;CODE&gt;license.qlikcloud.com&lt;/CODE&gt; &lt;STRONG&gt;FAILS&lt;/STRONG&gt;.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;The Qlik server, its internal configuration, and all internal network paths and proxy permissions remain identical in both scenarios. The &lt;STRONG&gt;only variable that changed is the final public IP address&lt;/STRONG&gt; used to reach &lt;CODE&gt;license.qlikcloud.com&lt;/CODE&gt;. This leads us to the firm conclusion that the source Public IP is the deciding factor.&lt;/P&gt;
&lt;P&gt;Regarding the telnet test, our servers are in an isolated internal network and do not have direct internet access. All outbound traffic must go through a proxy. We have already confirmed with our network team that the proxy policies for our Qlik server have been granted the highest level of permission to access &lt;CODE&gt;license.qlikcloud.com:443&lt;/CODE&gt;. Furthermore, our previous packet captures showed that we &lt;I&gt;can&lt;/I&gt; establish a TCP connection, but it is then terminated by a TCP RST from your end, which is a classic sign of IP filtering.&lt;/P&gt;
&lt;P&gt;Thank you for your continued support.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:51:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531220#M32234</guid>
      <dc:creator>RonaldChin</dc:creator>
      <dc:date>2025-09-18T09:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent Issue: License Synchronization Failure After Public IP Change - License Key: 1230 4250 1407 9635</title>
      <link>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531221#M32235</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/350608"&gt;@RonaldChin&lt;/a&gt;&amp;nbsp;I would highly recommend opening a ticket with support, rather than posting on Community, for prompt resolution of the issue you seem to be having.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:49:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531221#M32235</guid>
      <dc:creator>Or</dc:creator>
      <dc:date>2025-09-18T09:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: Urgent Issue: License Synchronization Failure After Public IP Change - License Key: 1230 4250 1407 9635</title>
      <link>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531222#M32236</link>
      <description>&lt;P&gt;Have you updated the new proxy info on your Qliksense server.&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/May2024/Subsystems/Server/Content/QV_Server/QlikView-Server/QVS_LicenseServiceProxySetUp.htm" target="_blank" rel="noopener"&gt;https://community.qlik.com/t5/Official-Support-Articles/Example-quot-services-conf-quot-file-for-Qlik-Sense-License/ta-p/1795986https://help.qlik.com/en-US/qlikview/May2024/Subsystems/Server/Content/QV_Server/QlikView-Server/QVS_LicenseServiceProxySetUp.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/sense-admin/May2025/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/LicenseServiceProxySetUp_QSEoW.htm" target="_blank"&gt;https://help.qlik.com/en-US/sense-admin/May2025/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/LicenseServiceProxySetUp_QSEoW.htm&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 09:57:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Urgent-Issue-License-Synchronization-Failure-After-Public-IP/m-p/2531222#M32236</guid>
      <dc:creator>SivenM2020</dc:creator>
      <dc:date>2025-09-18T09:57:40Z</dc:date>
    </item>
  </channel>
</rss>

