WebHMI Helm Chart Installation Troubleshooting

If the WebHMI Helm Chart installation does not complete successfully or some pods remain in a non-ready state (for example, Pending, CrashLoopBackOff, or Error), you can use Rancher’s built-in tools to identify and resolve the problem.

To identify and resolve WebHMI Helm chart installation issues:

  1. Check the pod status.

    1. Open your cluster view and go to Workload > Pods .

    2. In State , find the pods whose state does not show Running , and check the short description of the issue in the pod's row.

    3. Select the pod to open its Details page, and then check the Recent Events and Conditions tab. This is often the quickest way to spot issues like “insufficient memory” or “image pull errors.”

  2. View the pod logs.

    By default, WebHMI pods log into the standard output with logging level set to notice.

    1. To see more detailed logs, change the logging level by updating the logging.level value in your values.yaml file.
      You can set one of the following levels:

      • all

      • debug

      • info

      • notice

      • warning

      • error

    2. On the pod’s Details page, click and select View Logs to check logged error messages or missing environment variables.

    3. Use the Exec tab to open an interactive shell inside the container for deeper inspection.

  3. Use the following solutions to common causes to resolve the issue.

    • Insufficient resources : If your cluster does not have enough CPU or memory to start all pods, try lowering the replica count or adding more worker nodes. Learn more

    • Image pull issues : If you are using a private image registry, verify that your Docker Hub secret is correctly configured under Cluster > Storage > Secrets .

    • Incorrect configuration : Double-check that the values in your chart configuration (for example, FrameWorX hostname or ingress settings) are correct.

    • TLS certificate issues : To rule out possible issues related to the TLS certificate, you can temporarily enable HTTP by clearing the Enable HTTPS checkbox (selected by default) in General Settings . After upgrading the chart in step 4, try to access WebHMI in your browser using an HTTP URL, such as http://WebHMI.example.com .

  4. Follow the instructions in the Edit/Upgrade the Helm Release section to update the configuration values and redeploy the chart.

  5. Once all pods are running, open your browser and enter the ingress hostname (for example, https://WebHMI.example.com). You should see the WebHMI welcome page.