Streams are not visible at all on the Hub

[SK005]

Hi Team,

We have installed Qliksense with two nodes central and rim. On opening the development mode, all the streams i.e work, everyone, etc are visible. But the normally the hub doesn't show any of the streams. 

Regards,

SK

[Ray_Strother]

Hello ,

Take look at the article link below.

https://community.qlik.com/t5/Official-Support-Articles/Stream-are-not-visible-or-available-on-the-h...

[SK005]

For us the streams are not at all visible on hub whatever we clik. Not a
single stream is visible.
Regards
SK

[Anil_Babu_Samineni]

@SK005 When you say the problem after upgrade with enabling the Central and RIM node.

So, does it mean in your Load balance any one the service (Engine.exe) used to access the content in hub?

The best approach accessing hub to see the issue (could be in Central node), Is this problem with central node server URL as well or this is still with FQDN name when you have good resources to use it from load balance?

[hugo_andrade · Accepted solution]

Hi @SK005 ,

For troubleshooting purposes, elect a stream. After each step below, test your access to the HUB. Open a brand-new Private window for each test.

• Ensure the user account has read access to the Stream. 
• Publish an app to that stream. 
• Verify the Load Balancing rules in QMC. Make sure all are enabled for testing.
• Confirm the Security Rule "Stream" is enabled.
• On Virtual Proxy settings, check that there's a server assigned as Load Balancing for both Virtual Proxies (Central and RIM).

If all of the above are true. Check firewall rules between the servers.

[vinieme12]

RootAdmins by default won't have access to streams, you need to modify the Security Rules

[SK005]

Thanks, seems one of the load balancing rule for non central node was disabled and was creating the problem. But the strange thing is same rule is disabled on the production environment and everything is working fine there.

[hugo_andrade]

@SK005 ,

The main difference between PROD and this environment is probably the fact that the Virtual Proxies in PROD might be using the same engine, the Central Engine.