Failed to connect to the Rovo Dev API, please try again later.

[Raymond Tong]

Tried to execute `acli rovodev run` and prompted error `Failed to connect to the Rovo Dev API, please try again later.`

check `~/.rovodev/rovodev.log` and found below

```

2025-07-16 13:54:21.463 | ERROR    | - Failed to connect to the Rovo Dev API after multiple attempts.

2025-07-16 13:54:21.464 | ERROR    | - Failed to initialize analytics: Failed to connect to the Rovo Dev API, please try again later.

2025-07-16 13:54:21.497 | WARNING  | - Request error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Basic Constraints of CA cert not marked critical (_ssl.c:1018). Retrying...

2025-07-16 13:54:21.561 | WARNING  | - Request error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Basic Constraints of CA cert not marked critical (_ssl.c:1018). Retrying...

2025-07-16 13:54:21.607 | WARNING  | - Request error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Basic Constraints of CA cert not marked critical (_ssl.c:1018). Retrying...

2025-07-16 13:54:21.608 | ERROR    | - Failed to connect to the Rovo Dev API after multiple attempts.

2025-07-16 13:54:21.608 | ERROR    | -

Failed to connect to the Rovo Dev API, please try again later.

```

I think it is related to SSL cert issue but have no clue how to update the config.

No relevant config available in `~/.rovodev/config.yml`

Tried running command `acli jira dashboard search` and successfully retrieve result, wonder `jira` and `rovodev` have different way to authenticate.

[Jovana Dunisijevic]

Hey @Raymond Tong 

Sorry for my late reply - I just got back from my 3 weeks of PTO.

Sorry you're having issues!

The error message indicates that the Rovo Dev CLI is unable to verify the SSL certificate of the API endpoint it’s trying to reach. This is typically due to one of the following:

• The local machine’s certificate store is missing a required CA certificate.

• The certificate chain on the server is misconfigured.

• There’s a custom or self-signed certificate that isn’t trusted by your system.

Let's try to go through a few troubleshooting steps!

Update Your System CA Certificates

• On macOS: Run sudo security find-certificate -a -p /Library/Keychains/System.keychain > ~/Desktop/all-certs.pem and ensure your system is up to date.

• On Linux: Run sudo update-ca-certificates or sudo yum update ca-certificates (depending on your distro).

• On Windows: Make sure Windows Update is current and your root certificates are up to date.

Clear ACLI Plugin Cache

Sometimes, a corrupted or outdated plugin binary can cause issues. Try clearing the cache:

rm -rf ~/.local/share/acli

Then re-run your acli rovodev command to force a fresh download

Check for Proxy or Custom SSL Interception

If your network uses a proxy or SSL inspection, you may need to add your organization’s CA certificate to your system trust store.

Check for Minimum ACLI Version

Ensure you’re running the latest version of ACLI and the rovodev plugin, as older versions may have SSL bugs

If You’re Using a Custom or Self-Signed CA

You may need to manually add your CA to the system trust store. (See your OS documentation for how to do this.)

If you're still stuck:

• Check the full log at ~/.rovodev/rovodev.log for more details.

• If the problem persists after updating certificates and clearing the cache, please raise a report here: Bug report - Rovo Dev in CLI

Let me know if the situation changes and/or you need more help!

Kindest regards,

Jovana