<?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: Qlik Nprinting Connection Error in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/2432627#M20231</link>
    <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/168129"&gt;@manish_2991&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did you get any solution on this?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Mar 2024 05:26:58 GMT</pubDate>
    <dc:creator>TusharDev_Qlik</dc:creator>
    <dc:date>2024-03-20T05:26:58Z</dc:date>
    <item>
      <title>Qlik Nprinting Connection Error</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/1983418#M17378</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;I am some error while doing connection of Nprinting with Qliksense.&lt;/P&gt;
&lt;P&gt;We have a multinode setup of Qliksense, so we have taken a Load balancer to route the request on qliksense, which is working fine (able to open qliksense hub &amp;amp; qmc with Load balancer IP).&lt;/P&gt;
&lt;P&gt;But when I am creating connection to App in the QlikNprinting it is not making connection successfully. It's giving error at '&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ng-scope"&gt;Qlik NPrinting webrenderer can reach Qlik Sense hub&lt;/SPAN&gt;' while I am putting hub URL of load balancer in the proxy address. But when I put qliskense server IP instead of Load balancer IP it's working fine. Do we need to do any settings in Load balancer or I am missing out something in this.&lt;/P&gt;
&lt;P&gt;Please guide.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 05:31:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/1983418#M17378</guid>
      <dc:creator>manish_2991</dc:creator>
      <dc:date>2022-09-21T05:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Nprinting Connection Error</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/1983442#M17380</link>
      <description>&lt;P&gt;Hi, maybe the name is not added to the whitelist in vistualproxy-&amp;gt;advanced.&lt;/P&gt;
&lt;P&gt;This support post says that this error "This error can safely be ignored as this does not affect generation of NPrinting connections":&lt;A href="https://community.qlik.com/t5/Knowledge/How-to-resolve-Verification-Error-x-Qlik-NPrinting-webrenderer/ta-p/1786382" target="_blank"&gt;https://community.qlik.com/t5/Knowledge/How-to-resolve-Verification-Error-x-Qlik-NPrinting-webrenderer/ta-p/1786382&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Have you tried to save the connection with the error and make a test?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 06:32:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/1983442#M17380</guid>
      <dc:creator>rubenmarin</dc:creator>
      <dc:date>2022-09-21T06:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Nprinting Connection Error</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/2432627#M20231</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/168129"&gt;@manish_2991&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did you get any solution on this?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Mar 2024 05:26:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Nprinting-Connection-Error/m-p/2432627#M20231</guid>
      <dc:creator>TusharDev_Qlik</dc:creator>
      <dc:date>2024-03-20T05:26:58Z</dc:date>
    </item>
  </channel>
</rss>

