Skip to main content
Announcements
Do More with Qlik - Qlik Cloud Analytics Recap and Getting Started, June 19: REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Benjamin_Qlik
Contributor
Contributor

http:// Protocol - Error 404 - Access is no longer possible since November 2021 update

Hello everyone,

we updated our Qlik Sense Enterprise to November 2021 at the beginning of the year.

Now the call via http:// no longer works.

Benjamin_Qlik_0-1643099492577.png

 

"Allow http" is also set in the QMC Proxy settings and everything else is configured correctly.

Benjamin_Qlik_1-1643099595311.pngBenjamin_Qlik_2-1643099610465.png

 

Does anyone have a solution?

 

Because the https:// call is much slower with us 😕

 

Thanks forward!

Labels (2)
1 Solution

Accepted Solutions
Andrew_Delaney
Support
Support

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\

As the proxy starts up it will log the attempt to grab port 80, it should look like:

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

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

View solution in original post

1 Reply
Andrew_Delaney
Support
Support

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\

As the proxy starts up it will log the attempt to grab port 80, it should look like:

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

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