# General troubleshooting

> The `net::ERR_CERT_AUTHORITY_INVALID` error occurs when your certificate expires or is involved in a certificate rotation process, indicating that it is now invalid.

## The remote certificate is invalid because of errors in the certificate chain: UntrustedRoot

The `net::ERR_CERT_AUTHORITY_INVALID` error occurs when your certificate expires or is involved in a certificate rotation process, indicating that it is now invalid.

It is most likely that the error occurs for the following reasons:

* You cannot access UiPath standalone product installations.
* Your robot is disconnected.

Figure 1. Your connection is not private warning

  !['Your connection is not private'image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-your-connection-is-not-private-image-459857-56510639.webp)

Figure 2. UiPath Error message

  ![UiPath error message image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-uipath-error-message-image-460982-20cbf1a8.webp)

To fix this error, take the steps, described in the following example:

1. Select the **Not secure** warning prompt. Then select **Certificate is not valid** from the dropdown menu.

Figure 3. Certificate is not valid warning

   ![Certificate is not valid image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-certificate-is-not-valid-image-459666-4cf7df94.webp)

2. In the **Certificate Viewer**, select the **Details** tab. Then select **Export** and save the certificate.

Figure 4. Details tab

   ![Details tab image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-details-tab-image-459695-4dfb974b.webp)

3. On your local machine, open **certlm.msc** and right-select the **Personal** folder, then select **All Tasks**, then select **Import**. Select the previously generated certificate and import it.

Figure 5. Importing certificate

   ![Import certificate image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-import-certificate-image-459702-3810b88f.webp)

4. In the same **certlm.msc** window from the previous step, select the **Trusted Root Certification Authorities** folder, then select **All tasks**, then select **Import**. Select the previously generated certificate and import it again.

Figure 6. Importing certificate

   ![Import certificate image](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-import-certificate-image-459712-267ec665.webp)
   
5. Connect the robot again to check that the error is fixed.

Select the **View site information** icon. Select **Connection is secure** from the dropdown menu.

## Browser group policies

Signing in to your Orchestrator service from the Assistant redirects you to the SSO page. In some browsers, you may be prompted to open UiPath Assistant. This happens due to the Assistant's protocol handler not being added to the browser's group policies.

To prevent this behavior, make sure to follow the next steps, depending on the browser (Chrome/Microsoft Edge):

1. Open **Registry Editor**.
2. Navigate to `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome`/ or `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge`, depending on the browser you use.
3. Add a new key and name it `AutoLaunchProtocolsFromOrigins`.
4. Select **(Default)** to edit the key.
5. In the **Edit String** dialog, in the **Value data** field, add `[{"allowed_origins": ["https://myOrchestrator.uipath.com/"],"protocol": "com.uipath.robot.oidc"}]` and select **OK**.
   :::important
   The `AutoLaunchProtocolsFromOrigins` policy requires Chrome 85 or later.
   :::
6. Close all browser tabs and relaunch the browser.
7. Verify that your browser applied the new policy by navigating to `chrome://policy` or `edge://policy`. The recently added policy should be listed under the **Chrome Policies** or **Microsoft Edge** section with the **OK** status.

## Cron Expressions

When updating from v2018.1.x or v2018.2.x to either v2018.4.x or v2019.x, the use of invalid cron expressions in your schedules causes them to stop working. See below examples of incorrect cron syntax, the corrected expression, and its description.

| Incorrect Syntax | Corrected Syntax | Description |
| --- | --- | --- |
| `0 45/60 09-16 ? * MON-FRI *` | `0 45 09-16 ? * MON-FRI *` | At 45 minutes past the hour, between 09:00 AM and 04:59 PM, Monday through Friday. |
| `0 30/60 09-15 ? * MON-FRI *` | `0 30 09-15 ? * MON-FRI *` | At 30 minutes past the hour, between 09:00 AM and 03:59 PM, Monday through Friday. |
| `0 0/120 22-03 ? * MON-SAT *` | `0 0 22-03/2 ? * MON-SAT *` | Every 2 hours, between 10:00 PM and 03:59 AM, Monday through Saturday. |

Please note that this issue is only encountered for schedules defined specifically with cron expressions, using the **Advanced** option.