Extension Permission issue on hub

[dgranic]

We have deployed an application that is causing an error on execution via access through the proxy server. We get 

INVALID VISUALIZATION

The visualization was not found on the server. The extension is not available : sn-table()

I realize this is a permission issue but I am unable to pinpoint the issue as Everyone has access to the extensions and the users have permission to the Application via OKTA group membership.. The application and the data is being displayed just this visualization is failing and some png files

Running the app directly on the server runs OK , just fails through the proxy

[Eduardo_Monteiro]

Hi @dgranic 

Two approaches:

Can you confirm the extension is not corrupted by remotely connecting to the server and opening it? In case you confirm it's working, you can check for the networking block proxy/reverse proxy.

Open browser DevTools > Network tab, reload the app through the proxy, and filter for failed requests (red, status 404/502/0).

The URL pattern will tell you which path is being blocked, and then you can compare the failed URL against your proxy location/routing rules.

BR,

[dgranic]

the file is not corrupt .. I get a 404 accessing from the proxy.. I even verified the shared drive is available and readable using the service account login

[Eduardo_Monteiro]

Hi @dgranic 

Try adding advisorreporting-dev.worldsourcewealth.com to the virtual proxy host allow list, then restart the proxy.

Regards,

[dgranic]

the allow host is already set .. BTRW: I have a production pair that works and I have compared every single configuration option and they are exactly the same except for FQDNs of course.. I am thinking there is a permission issue that is not obvious .. the issue is only the extensions . normal views/apps works just fine

[Eduardo_Monteiro]

I see.

Can you please share the log from: C:\ProgramData\Qlik\Sense\Log\Repository\Audit\ and the proxy server IP?

[dgranic]

advisorreporting-dev.worldsourcewealth.com/extensions/sn-table/sn-table.js

you can access via external IP but it will need authentication via OKTA .. I access via an internal IP 

192.168.38.75]

[dgranic · Accepted solution]

resolved the issue .. cluster setting was incorrect... had to add FQDN .. 

[Eduardo_Monteiro]

Awesome, thanks for sharing!

[dgranic]

thanks for helping