8/24/2023 0 Comments G hubI can't think of an easy work around for Mac given my environment's limitations (so I'm stuck doing the service restart method on Zscaler for now). However, when I tried to run the updated program I got hit with Apple's code signing protection and the app crashes on load :(. I got far enough to adjust the port and unpack a new keytar.node file with the updated port (node command "sudo npx asar extract-file app.asar keytar.node" and replace keytar.node in folder). If you are adventurous, the code references look something like: "ws://localhost:9010" and "" in the app.asar file. After more digging I found that the front end for GHUB on mac uses electron and it is packed in a file (app.asar at "/applications/lghub.app/Contents/MacOS/lghub_ui.app/Contents/Resources/app.asar") that gets unpacked into a keytar.node file that has two references where the port is bound and then called on program load. In my case, (I'm on Mac) and I don't have that flexibility to modify Zscaler's bind port so I spent some time trying to "hack" the GHUB app to bind on a different port (of course Logitech doesn't have any configurable port option in GHUB). So, if you administer Zscaler on your side, one fix is to just modify the port that ZCC binds on (make sure you pick a port that doesn't have a conflict or you will be back to square one with some other program). 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |