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: 
awqvuserneo
Creator
Creator

QMC shows the page can't be displayed

Hi there,

I'm installing Qlik Sense Server on Win8.1 64bit. The installation went successfully (I'm logging in to my computer using my own ID with local administrator privilege). Now, when I try to open the QMC using either IE or Firefox, it shows that "Page cannot be displayed".

Would you suggest where I might possibly miss a step?

I did the following as well:

1. Turn off windows firewall

2. Add the URL to the Trusted list

3. Using IP instead of URL

There's no new log is created in the C:\ProgramData\Qlik\Sense\Log subfolders when I attempted to open the QMC...(all existing logs are from when I completed the installation)

Thank you in advance,

Anton

19 Replies
Anonymous
Not applicable

I get the same behavior (Windows server 2012) . The browser shows “This page can't be displayed” when trying to access the <intrantetURL>/hub

  • The browser shows “Waiting for…” in the tab then it times out (info from F12 in Chrome), if I write a non-valid URL it shows the same “This page can't be displayed” but without any “Waiting for…”. 
  • If I log in (as user) to the server and open the same link (<intrantetURL>/hub), it works fine.

  • I can successfully ping the url from my local computer and I get the same “Waiting for…” when trying to access  <intrantetURL>/hub with ip-number instead of url.

  • I can’t find anything in the log-files (\ProgramData\Qlik\Sense\Log\...) about even trying to access the <intrantetURL>\hub.

  • Skype is not installed at the server (or local) and the server has no active IIS-installation.

Any suggestions what to examine next?

Not applicable

Dear Urban,

As you mentioned that hub is accessible from server local but not from another machine (but has waiting message), and meanwhile no entry in Proxy Log, this could be probably because some important ports are blocked or occupied.

Have you tried turning down the firewall on server?

//Bohua

Anonymous
Not applicable

Yes, it worked fine when firewall was set to Off.

I guess the best solution is to find what ports they both want to use and change that one in QMC proxy-settings?

Not applicable

In this case, it's very probably due to 4244, the windows authentication port. It's configurable in Proxy settings through QMC

Cheers,

Bohua

awqvuserneo
Creator
Creator
Author

Hi Mike,

Sorry for the late reply. I didn't have skype or IIS installed on my Windows 8.1 laptop (company owned). I did another attempt with Windows 7 (personal), and it went just fine. I did install/uninstall with combination of different account: local account (with admin privilege - sense_system), domain account (also with admin privilege to the laptop), & even with just using the local system account.

So, I guess I probably need to check the ports (though I did disabled Windows Firewall, but it could be there's another antivirus/firewall blocking these ports). Do you have any suggestions an easy way to check which ports are open/close? (My network skills is very limited, so I apologize in advance if I ask for a more detailed guidance from you )

Best regards,

Anton

Michael_Tarallo
Employee
Employee

HI Anton - at a command line - type:

netstat -a | find "LISTENING"

here is mine - and you can see all the ports used:

Note: 443 and the 42* ports - those are used by my Qlik Sense server on my machine.

4432 is the default postgreSQL port for the repository database

Other are there too, from other software I have running.

  TCP    0.0.0.0:135            mtarallo1234:0         LISTENING

  TCP    0.0.0.0:443            mtarallo1234:0         LISTENING

  TCP    0.0.0.0:445            mtarallo1234:0         LISTENING

  TCP    0.0.0.0:623            mtarallo1234:0         LISTENING

  TCP    0.0.0.0:902            mtarallo1234:0         LISTENING

  TCP    0.0.0.0:912            mtarallo1234:0         LISTENING

  TCP    0.0.0.0:1433           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:2382           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:2869           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:3389           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4241           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4242           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4243           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4244           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4444           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4747           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:4848           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:5050           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:5151           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:5252           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:5357           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:8000           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:8080           mtarallo1234:0         LISTENING

  TCP    0.0.0.0:16992          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:17500          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49152          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49153          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49154          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49155          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49158          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49162          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:49163          mtarallo1234:0         LISTENING

  TCP    0.0.0.0:53690          mtarallo1234:0         LISTENING

  TCP    127.0.0.1:1434         mtarallo1234:0         LISTENING

  TCP    127.0.0.1:4432         mtarallo1234:0         LISTENING

  TCP    127.0.0.1:5354         mtarallo1234:0         LISTENING

  TCP    127.0.0.1:12124        mtarallo1234:0         LISTENING

  TCP    127.0.0.1:59948        mtarallo1234:0         LISTENING

  TCP    192.168.2.121:139      mtarallo1234:0         LISTENING

HTH

Mike

Regards,
Mike Tarallo
Qlik
melghandour89
Partner - Contributor III
Partner - Contributor III

  1. Stop Qlik Sense Repository Service (this will also stop the other services)
  2. Applying an SSL Certificate to server

to apply an SSL Certificate to a Qlik Sense server

  1. Launch the MMC
  2. When the MMC opens go to File|Add/Remove Snap-in.
  3. Click on the Certificates snap-in on the left side list box and click the add button.
  4. Choose Computer account and click Next.
  5. Leave Local computer selected and click Finish.
  6. Click OK to go back to the MMC.

Then restart the server and running all qlik services and try again for more details please check this link
Hope it Work

awqvuserneo
Creator
Creator
Author

Thanks Mahmoud, I appreciate it your input.

Best regards,

Anton

melghandour89
Partner - Contributor III
Partner - Contributor III

You are welcome , If it's the correct answer please marked as an answer Thnks

bijoylalu007
Partner - Contributor II
Partner - Contributor II

Hi Michael,

     Even after the Qlik service is up, then also i am not able to open QMC

     Attaching screenshots here.

Browser.JPG

Services.JPG

Kindly advise.