Standalone Orchestrator UI not loading after the SSL certificate was changed. Returns an HTTP 500 error. The config files in the automation environment are encrypted. How to get past this issue?
Issue Description:
The Orchestrator server becomes inaccessible due to the expiration of the certificate. This led to an inability to read the encrypted config files, which resulted in the breakdown of the UiPath Orchestrator.
This scenario arises due to the "Orchestrator UiPath.Orchestrator.dll.config" and Identity "appsettings.Production.json" files being encrypted using a certificate that later expired, which results in the Orchestrator being unreachable and not functioning as expected.
Resolution:
- Reinstall the expired certificate using these steps and decrypt the "appsettings.Production.json" file using these steps.
- After the successful decryption of the file, you can edit it and set the new Certificate Thumbprint in the 'Name' key within the 'SigningCredentialSettings' section.
- After following the above steps, Orchestrator is observed to be functional and accessible again. As a final step, the appsettings.Production.json file should be encrypted back with the new certificate using these steps.
- Note: Always ensure to take a proper backup before making any config changes.