Zscaler seems to have a configurable port but it requires access to the ZCC administrative console and a custom agent deployment. Unfortunately, on the GHUB side, the port is hard-coded into the front end app itself. Also GHUB only needs to bind for a split second before it will load and then work without issue. The GHUB front-end will keep "spinning" if it can't bind on this port (it just retries over and over again).
It seems that Zscaler and Logitech GHUB both bind on port 9010 for websocket calls to localhost.
Check my comment on "clean boot".įor those who have the Zscaler issue, I have traced the "why" after some digging. TLDR Other apps can block/ influence G Hub. You can then just select one app after another to start with windows again until you have the one that blocks G Hub. If G Hub works then you know that another app is causing the issue. It basically disables all 3rd party apps on the next reboot. There are guides on how to do a Windows 10 "clean boot" which would also have helped me identify the problematic app. When I close it G Hub consistently works. It always autostarted and hence always blocked my G HUB. Until - by accident - I had the ZSCALER app crashing and suddenly G Hub starts. Delete virtual logitech keyboard and mouse drivers Install all open windows updates incl optional ones which are usually drivers
Launch updater, agent and app in the right order manually
0 kommentar(er)
