<?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: http:// Protocol - Error 404 - Access is no longer possible since November 2021 update in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/http-Protocol-Error-404-Access-is-no-longer-possible-since/m-p/1885143#M30172</link>
    <description>&lt;P&gt;That is curious, can you restart the proxy service and then look at the System_Proxy logs in C:\ProgramData\Qlik\Sense\Logs\Proxy\Trace\&lt;/P&gt;
&lt;P&gt;As the proxy starts up it will log the attempt to grab port 80, it should look like:&lt;/P&gt;
&lt;P&gt;28 20220125T164600.655+0100 INFO QlikServer1 System.Proxy.Proxy.Core.RequestListener 10 776d804a-30e0-4233-9d29-a7bf2f9ed95b DOMAIN\qservice Started 'non-ssl' listener at port '80' 776d804a-30e0-4233-9d29-a7bf2f9ed95b&lt;/P&gt;
&lt;P&gt;If it can't instead you will see an error logged. Most often I see this happen when there is some other webservice active on the server that has already taken port 80&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jan 2022 15:47:12 GMT</pubDate>
    <dc:creator>Andrew_Delaney</dc:creator>
    <dc:date>2022-01-25T15:47:12Z</dc:date>
    <item>
      <title>http:// Protocol - Error 404 - Access is no longer possible since November 2021 update</title>
      <link>https://community.qlik.com/t5/Management-Governance/http-Protocol-Error-404-Access-is-no-longer-possible-since/m-p/1884878#M30171</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;we updated our Qlik Sense Enterprise to November 2021 at the beginning of the year.&lt;/P&gt;
&lt;P&gt;Now the call via http:// no longer works.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Benjamin_Qlik_0-1643099492577.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/70882i633491F441A58373/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Benjamin_Qlik_0-1643099492577.png" alt="Benjamin_Qlik_0-1643099492577.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Allow http" is also set in the QMC Proxy settings and everything else is configured correctly.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Benjamin_Qlik_1-1643099595311.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/70883i6E5A5232A521FC9D/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Benjamin_Qlik_1-1643099595311.png" alt="Benjamin_Qlik_1-1643099595311.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Benjamin_Qlik_2-1643099610465.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/70884i148A74A8707142F9/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Benjamin_Qlik_2-1643099610465.png" alt="Benjamin_Qlik_2-1643099610465.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does anyone have a solution?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Because the https:// call is much slower with us &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks forward!&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 16:38:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/http-Protocol-Error-404-Access-is-no-longer-possible-since/m-p/1884878#M30171</guid>
      <dc:creator>Benjamin_Qlik</dc:creator>
      <dc:date>2025-01-29T16:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: http:// Protocol - Error 404 - Access is no longer possible since November 2021 update</title>
      <link>https://community.qlik.com/t5/Management-Governance/http-Protocol-Error-404-Access-is-no-longer-possible-since/m-p/1885143#M30172</link>
      <description>&lt;P&gt;That is curious, can you restart the proxy service and then look at the System_Proxy logs in C:\ProgramData\Qlik\Sense\Logs\Proxy\Trace\&lt;/P&gt;
&lt;P&gt;As the proxy starts up it will log the attempt to grab port 80, it should look like:&lt;/P&gt;
&lt;P&gt;28 20220125T164600.655+0100 INFO QlikServer1 System.Proxy.Proxy.Core.RequestListener 10 776d804a-30e0-4233-9d29-a7bf2f9ed95b DOMAIN\qservice Started 'non-ssl' listener at port '80' 776d804a-30e0-4233-9d29-a7bf2f9ed95b&lt;/P&gt;
&lt;P&gt;If it can't instead you will see an error logged. Most often I see this happen when there is some other webservice active on the server that has already taken port 80&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 15:47:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/http-Protocol-Error-404-Access-is-no-longer-possible-since/m-p/1885143#M30172</guid>
      <dc:creator>Andrew_Delaney</dc:creator>
      <dc:date>2022-01-25T15:47:12Z</dc:date>
    </item>
  </channel>
</rss>

