topic Sense doesn't display images when used standalone proxy over firewall in Management & Governance

Sense doesn't display images when used standalone proxy over firewall

Anonymous — Thu, 12 Jul 2018 14:23:25 GMT

Hello.

When working with QlikSense through a dedicated proxy, images are not displayed.
If open the central node directly, everything is displayed.
Probably, some tcp ports are not open between Proxy and Central Node (or Shared Directory)?

Tell me, what additional ports need to be opened, or what settings still need to be made?

Opened ports:

- from Proxy to Engine: 4747 (QES),4239 (QRS),4949 (QSD),4242 (QRS),4900 (QSD),9028 (QSD)

- from Engine to Proxy: 4444 (QRS), 4242 (QRS)

QlikSense Version: June 2018

Re: Sense doesn't display images when used standalone proxy over firewall

Levi_Turner — Tue, 17 Jul 2018 19:54:52 GMT

The root cause is likely that the service account on the RIM node in the DMZ does not have access to the Service Cluster > SharedContents folder. Either at a network level (SMB not allowed) or at an NT / Share level.

Re: Sense doesn't display images when used standalone proxy over firewall

Anonymous — Wed, 18 Jul 2018 08:45:02 GMT

Hi Levi.

Thank you.

I rechecked Rights

All nodes have access.

The cluster works in Shared Persistance mode with a shared directory.

Rights for the service account are given.

Re: Sense doesn't display images when used standalone proxy over firewall

BalaBhaskar_Qlik — Wed, 18 Jul 2018 16:04:50 GMT

May be try like this:

Check to see if you have both the external IP-address and/or the external DNS-entry listed in your proxy whitelist.

Please ensure you uploaded your images on the server (in the QMC: go to "content libraries" /select a library/ upload file button). You'll be able to use the uploaded image in your application.

https://help.qlik.com/en-US/sense/2.0/Subsystems/ManagementConsole/Content/upload-objects-to-content-libraries.htm?Highlight=Content%20Library

https://community.qlik.com/thread/178733.

Re: Sense doesn't display images when used standalone proxy over firewall

Anonymous — Thu, 19 Jul 2018 07:12:22 GMT

The proxy is not in the domain, and the domain names of all cluster servers are included in the host file.

The situation was corrected after a short file server name was added to the host

before:
10.10.10.10 fileshare.corp.com

after:
10.10.10.10 fileshare.corp.com

10.10.10.10 fileshare