Troubleshooting ================================================================================ I am installing the solution for the first time, but there are errors when I run setup.sh. ------------------------------------------------------------------------------------------------------- #. :ref:`connect-to-file-share`. #. In the terminal, enter the command ``kubectl logs deployment/db`` to investigate if the ``db`` deployment has any issues. #. Similarly, you may investigate the ``ejbca`` and ``signserver`` deployments with ``kubectl logs deployment/ejbca`` and ``kubectl logs deployment/signserver``. #. Try reinstalling the Helm Chart, as in :ref:`deployed-setup-failed`. #. If the issue cannot be resolved, contact us for support and include ``config/logs.txt`` and the deployment logs above. The ``db`` logs repeatedly show ``FATAL: no pg_hba.conf entry for host "10.xx.xx.xx", user "xx", database "xx", no encryption``. -------------------------------------------------------------------------------------------------------------------------------- This is known intermittent issue with the installation. See :ref:`deployed-setup-failed` to reinstall the Helm Chart in the Azure Kubernetes Cluster. .. _deployed-setup-failed: My Azure Resource Deployment was successful but the setup failed. -------------------------------------------------------------------------------- The following steps will reinstalling the Helm Chart in the AKS cluster. This also means that your File Share, along with any files you uploaded will be deleted and a new one will be deployed. #. In the Azure `portal `_, enter ``Kubernetes Services`` in the search box. Select **Kubernetes Services**. #. Click ``inoQulate``. #. Click ``Connect``. #. Under the **Set cluster context** section, click **Open Cloud Shell**. It is not necessary to mount the File Share. #. Run the following commands. .. code-block:: shell helm get values $(helm list -q) --all -o yaml > values.yaml helm uninstall $(helm list -q) helm install --generate-name oci://pqceepub.azurecr.io/helm/inoqulate --values values.yaml rm values.yaml #. The solution will take about 15 minutes to be installed and ready for further setup. #. Continue your setup from :ref:`connect-to-file-share`. .. _chrome-firefox-client-cert: My Chrome/Firefox browser won't recognise my SuperAdmin certificate. -------------------------------------------------------------------------------- The Chrome and Firefox browsers, and other browsers of the same derivative, use a certificate store different from the Operating System's certificate store. You need to install your ``.p12`` certificate or the ``ManagementCA.crt`` certificate in Chrome/Firefox's certificate store instead.