Skip to main content
Announcements
See why Qlik is a Leader in the 2024 Gartner® Magic Quadrant™ for Analytics & BI Platforms. Download Now
cancel
Showing results for 
Search instead for 
Did you mean: 
zchitishvili
Contributor
Contributor

Extensions not loading from external access server

Hello everyone,

We are experiencing the following problem in Qlik Sense Enterprise (June 2020 Patch 3 / qliksenseserver 13.82.11):

We are running two nodes in our environment: (1) the central node with all services activated and (2) another node with proxy and repository services activated.

Dedicated proxy server is for external access with external web address. However, we can also access the system via an internal address.

We have recently started using extensions in our apps and noticed that they don't work when the system is accessed via the external address (external_ext.PNG). The error message is: "Invalid visualization. The visualization was not found on the server. This extension is not available". However, if the same app is accessed via the internal address, everything is alright (internal_ext.PNG). We've also noticed that app thumbnails are not showing up when the system is accessed from the external address (external_thumb.PNG).

We are running exactly the same setup elsewhere in our company and in that environment everything is alright. The only difference with these two environments is that the other setup is running on an older version of Qlik Sense Enterprise (February 2020 Patch 2).

Has anyone experienced similar issues?

Any help will be greatly appreciated. Thanks in advance.

1 Solution

Accepted Solutions
zchitishvili
Contributor
Contributor
Author

Hello everyone,

In case anyone is experiencing similar issues, I'll share what worked for us:

We put both servers (central node and proxy) under the same domain and it did the trick. Now everyhing works great.

View solution in original post

1 Reply
zchitishvili
Contributor
Contributor
Author

Hello everyone,

In case anyone is experiencing similar issues, I'll share what worked for us:

We put both servers (central node and proxy) under the same domain and it did the trick. Now everyhing works great.