Resolving UI and Access Issues in AiCenter Standalone Post-Certificate Update

News Knowledge Base
1

What are the steps to resolve UI and access issues in AiCenter Standalone following a certificate update?

Issue Description:

Users may encounter a 'Communication failed due to authentication issue, if this persists then please try refreshing the page' or other various frontend popup error messages in the AiCenter Standalone web application's GUI following an update to the SSL certificates. This error typically presents itself as a popup with specific error details, such as:

  • 'Error Loading Table Data'

  • 'Error Getting Projects'

  • 'Communication failed due to authentication issue, if this persists then please try refreshing the page'


Further identification of the issue can be found within the ai-helper logs:

  • Invalid signing key found

  • unable to find valid certification path to requested target

Note: If you are receiving other frontend web application errors and have not recently updated your certificates, this article may not be applicable.

Screenshot 2024-03-19 at 10.06.50 AM.png
Screenshot 2024-03-19 at 10.06.50 AM.png1795×1030 39.9 KB

Resolution: To resolve this issue, follow these steps:

  1. Ensure you have properly followed the documentation on updating the certificates that is applicable to your version

  2. Ensure that you have followed the steps to resync your AiCenter access token outlined in the two documents below

  3. Manually delete the relevant AiCenter deployment pods to clear the in-memory cache and ensure volume mount data is reloaded.

    • Connect to your Kubernetes cluster where AiCenter Standalone is deployed.

    • Execute the following commands to delete the affected AiCenter pods:

      kubectl delete pod -l app.kubernetes.io/name=ai-deployer -n uipath --force kubectl delete pod -l app.kubernetes.io/name=ai-helper -n uipath --force kubectl delete pod -l app.kubernetes.io/name=ai-app -n uipath --force kubectl delete pod -l app.kubernetes.io/name=ai-appmanager -n uipath --force kubectl delete pod -l app.kubernetes.io/name=ai-pkgmanager-n uipath --force kubectl delete pod -l app.kubernetes.io/name=ai-trainer-n uipath --force

      • These commands will delete the pods for ai-deployer-deployment, ai-appmanager-deployment, ai-app-deployment, ai-pkgmanager-deployment, ai-trainer-deployment, and ai-helper-deployment in the uipath namespace.

    • Wait for a few minutes to allow Kubernetes to automatically recreate the pods.

    • Once the pods are recreated, try accessing the AiCenter web application again. If the error persists, raise a ticket with UiPath Support.