Installation completed successfully, but you cannot access Action Center.

Install the ASP.NET Hosting Bundle
• minimum version 3.1.x, available here, or 5.0.x, available here

You cannot access Action Center using the load balancer URL.

Follow the steps below:

1. For each Action Center node specify their corresponding hostname and port in the Action Center IIS Settings screen.
2. Update the common load balancer URL with the Action Center URL (for example, https://action-center.domain.com) in the Action Center UiPath Identity Settings screen.

When accessing Action Center using the load balancer URL, Identity Server responds with the Unregistered Client Error message.

Update the Subject Alternative Name (SAN) to include all node and load balancer hostnames:
• use a wildcard pattern such as DNS Name = *.domain.com, or
• specify each hostname in the SAN

Image or PDF files are not loading in Action Center forms.

Verify the <appSettings> property in the UiPath.Orchestrator.dll.config file and make sure that:
• the value of the AcceptedRootUrls key does not include space characters,
• the port value for Action Center URL is specified only when it is different than 80 or 443 (default ports).

Find out more info here.

Action Center does not load because .json and .woff2 MIME types used by the Action Center WebApp provide a 404 response code.

For each Action Center node, add the .json and .woff2 MIME types in IIS > Mime types > Add:
• File name extension: .json, MIME type: application/json
• File name extension: .woff2, MIME type: application/font-woff2

PaaS installation using Terraform

This issue occurs for PaaS installations run through Terraform.

Installation completed successfully, however Action Center does not load and displays the following message: "You do not have permissions to view this directory or page"

Add index.html in the Default documents section of your cloud provider:

1. Go to your App Services in Azure.
2. Navigate to Settings.
3. Open the Configuration page.
4. Switch to the Default documents tab.
5. Click + New Document.
6. Add index.html.

Upgrading to higher versions of Action Center was successful, but cannot access Action Center via the load balancer URL.

This issue applies if the Host URL is different than the load balancer URL.

Follow these steps:

1. In the ActionCenter/Actions/environments/env.json key, manually update the values for businessUserPortalProxyServiceUrl and postLogoutRedirectUri to the correct load balancer URL.

2. In the ActionCenter/Processes/environments/env.json key, manually update the values for businessUserPortalProxyServiceUrl and postLogoutRedirectUri to the correct load balancer URL.