Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
saranya
Contributor II
Contributor II

Unable to access Qlik Sense server outside the system it is installed

I have installed Qlik Sense Server in an  RDP, inside the System if i give https://localhost/qmc/ i am able to access but when i give the public ip i.e External ip of the system in place of localhost i get 503 error.

 

I have added external ip in the whitelisting part of qmc still i get 

Untitled.png

 

Qlik Sense 503 errorQlik Sense 503 error

 

 

 

 

 

 

 

 

How to solve this issue?

1 Solution

Accepted Solutions
Gysbert_Wassenaar

Why are you trying to open it on port 4244? It should be reachable on port 443, i.e. just https://myhosthere/qmc

talk is cheap, supply exceeds demand

View solution in original post

6 Replies
Vegar
MVP
MVP

You would need to open the firewall on your server to the incoming communication on port 80, 443 (and 4244).

https://help.qlik.com/en-US/sense/November2018/Subsystems/PlanningQlikSenseDeployments/Content/Sense...
saranya
Contributor II
Contributor II
Author

Untitled.png

I I have already enabled the ports but i get the same issue.

 

 

Gysbert_Wassenaar

Why are you trying to open it on port 4244? It should be reachable on port 443, i.e. just https://myhosthere/qmc

talk is cheap, supply exceeds demand
Vegar
MVP
MVP

@Gysbert_Wassenaar @ 4244 is for windows authentication.

 

@saranya what's the scope of your firewall rule? Does it include access from external ip?

 

Screenshot_20190525-130343.jpg

 

Gysbert_Wassenaar

I know. But the url posted is not an url that you would enter in the browser and it's not an url generated by the older qlik sense versions (pre April2018 iirc) that needed port 4244 open for windows authentication.

talk is cheap, supply exceeds demand
Vegar
MVP
MVP

I where not aware of this change, thanks for pointing that out.

So then it is external access to 443 that seems to be the issue in this post.