Common issues
| Issue | Possible cause | Resolution |
|---|---|---|
| Cannot access the Omnissa Monitor URL | DNS not configured | Add a DNS A record mapping the appliance IP address to the appliance domain |
| SSH login fails with admin credentials | Admin password not set or incorrect | Use the password set during OVF deployment |
| Horizon pod shows Disconnected | Connection Server unreachable, or credentials incorrect | Verify that ports 443 and 4002 are open. Re-validate Connection Server credentials in Data Sources > Edit |
| UAG shows Failed status | Port 9443 blocked, or UAG VM unreachable | Ensure port 9443 is open from the Omnissa Monitor appliance to the UAG VM. Verify the UAG is running |
| No session data on dashboards | Horizon Agent not reporting, or MQTT port blocked | Confirm inbound port 31883 is open. Verify that a compatible Horizon Agent is installed on the VDI VMs |
| Certificate expiry warning on the UAG dashboard | UAG SSL certificate expiring within 30 days | Renew the UAG certificate. The dashboard updates on the next collection cycle |
| Connection Server credential validation fails | Service account lacks required permissions | Ensure the Horizon service account has at minimum the built-in Read Only Administrator role |
| Connection Server onboarding blocked, Invalid Connection Server License | No valid Horizon license detected for the Connection Server | Ensure a valid Horizon license is available for the Connection Server, then retry onboarding. See License Validation |
| Connection Server onboarding blocked, Connection Server License Check Failed | The license validation check could not complete | Omnissa Monitor retries automatically. If the message persists, contact Omnissa Support. See License Validation |
Diagnostics
A diagnostic script runs automatically on the first boot and every subsequent boot of the appliance VM. It performs the following validations:
- Infrastructure: cluster access, system services, and namespaces
- Deployments: Helm releases, pod readiness, and service endpoints
- Application health: PostgreSQL, Vault, Keycloak, Kafka, EMQX, Flink, Admin-Lite, UI, and Ingress
- Security and resources: TLS certificates, PVC states, and resource usage
Each check is recorded with a PASS, FAIL, or WARN status in a timestamped log file. A consolidated summary is printed at the end, highlighting all failures and warnings.
Log file location
/opt/horizon/var/log/
Manually trigger the diagnostic script
sh /opt/horizon/bin/diagnostic.sh
Collect logs from all deployed modules
sh /opt/horizon/hem/scripts/collect_diagnostic.sh
此頁面對您有幫助嗎?