liquidware-ninjaSecond brain & toolkit
Personal project. Research and learning only. Not for production. No warranty.Not for production
  • Built on my own time for research and learning. Not affiliated with, endorsed by or supported by my employer, Liquidware or Microsoft.
  • Bring your own Liquidware licenses. Don't run any of it in production or against tenants and subscriptions that matter. Test in a dedicated lab first.
  • Provided "as is", without warranty of any kind, under each repository's license. You use it at your own risk and own the Azure charges it incurs.
  • Contributions and forks are welcome and encouraged on public repos. See Contribute.

Known errors

partialReviewed 2026-10-18Source: troubleshooting/README.md

Errors we've hit, what caused them and what fixed them. The table is generated from known-errors.yaml; fixes marked (unverified) haven't been confirmed yet.

Symptom Cause Fix Source
Connector ID Keys are installed but the Hub shows no data from them The key calls the address in its mgrcert.pem, taken from the Hub's DNS name when the installer was downloaded; the address is wrong or unreachable on TCP 443 Set the Hub's DNS name (Configuration > Edit Network Configuration), download the installer again and reinstall, or edit mgrcert.pem and restart the key's service; allow TCP 443 from the desktops to the Hub (unverified) link

Adding an entry

Add an entry to known-errors.yaml with the exact error text as the symptom, the versions it was seen on in applies_to, and a source (a KB page or an https link). Or open a Known error issue, and a maintainer turns it into a pull request.

Linked from 2 pages