SSL Error in RovoDev CLI: Missing Authority Key Identifier

[Key Wang]

Hi there,

I'm trying to use the RovoDev CLI, but I am encountering an SSL certificate error. Could you please assist me in resolving this issue?

Attached below is the log output from my terminal.

PS C:\Users\****> acli rovodev log
2026-04-14 11:17:30.782 | ERROR | rovodev.common.return_stale_and_refresh_cache:get:101 - Failed to fetch value for cache key _get_config|user@****.com|rovo_dev_cli_client_config: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)
2026-04-14 11:17:30.783 | WARNING | rovodev.common.dynamic_config_base:config:85 - Failed to retrieve dynamic configuration, using defaults.
2026-04-14 11:17:30.813 | ERROR | rovodev.common.return_stale_and_refresh_cache:get:101 - Failed to fetch value for cache key _get_config|user@****.com|rovo_dev_cli_session_feedback_config: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)
2026-04-14 11:17:30.813 | WARNING | rovodev.common.dynamic_config_base:config:85 - Failed to retrieve dynamic configuration, using defaults.
...
2026-04-14 11:17:31.189 | ERROR | rovodev.common.return_stale_and_refresh_cache:get:101 - Failed to fetch value for cache key _get_config|user@****.com|devai_axis_client_proof_config: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)
2026-04-14 11:17:31.190 | WARNING | rovodev.common.dynamic_config_base:config:85 - Failed to retrieve dynamic configuration, using defaults.
2026-04-14 11:17:33.317 | ERROR | rovodev.common.return_stale_and_refresh_cache:get:101 - Failed to fetch value for cache key _get_config|user@****.com|rovo_dev_cli_client_config: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Missing Authority Key Identifier (_ssl.c:1028)
2026-04-14 11:17:33.317 | WARNING | rovodev.common.dynamic_config_base:config:85 - Failed to retrieve dynamic configuration, using defaults.
PS C:\Users\****>

Thank you for your assist.

[hayato yamazaki]

To resolve a similar issue, I contacted support and had them file a request for an optional feature that allows you to specify a custom CA in the Rovo Dev CLI.

Please vote in favor!

[ROVODEV-25] Support for Custom CA Certificates in Rovo Dev CLI - Create and track feature requests for Atlassian products.

Thanks.

[Arkadiusz Wroblewski]

Hello @Key Wang 

Your log is failing at the SSL certificate validation step while the CLI tries to fetch config, and the error is CERTIFICATE_VERIFY_FAILED / Missing Authority Key Identifier.

That usually points to a local proxy / TLS inspection / certificate-chain problem.

The first thing to check is whether you are behind a corporate network, VPN, proxy, or endpoint security tool that is re-signing HTTPS traffic. Atlassian’s own CLI guidance calls out proxy environments as a common source of SSL errors.

Try the same command from a clean network like a hotspot. If it works there, your network/security team will need to fix or bypass the TLS inspection path for the Atlassian endpoints the CLI uses. 

https://developer.atlassian.com/platform/forge/enterprise/use-forge-cli-on-corporate-network/ 

[Key Wang]

Hi @Arkadiusz Wroblewski 

Thank you very much for your help.

Due to strict security policies, I can only connect to the company's Wi-Fi, so I cannot test this on another network.

I have tried the methods you provided and also consulted AI tools. However, since my company doesn't use a proxy server, the problem is still unresolved.

Please let me know if there is anything else I can try.

[Arkadiusz Wroblewski]

@Key Wang 

This strict polices can be also a reason so you should Adress that probably to you IT Team.

[Key Wang]

Hi @Arkadiusz Wroblewski 

Thank you very much for the help.

[Arkadiusz Wroblewski]

@Key Wang 

I don't done nothing besides couple advices. We are here for each other.

Can you figure that out with your IT ?

I can say you from my own esp experience as IT Administrator, strict policies are needed but they are also pain in ... For User.

[Key Wang]

Our IT team is working on it. 

so hopefully the problem will be solved soon. haha

thank you :D

[Arkadiusz Wroblewski]

” Our IT Team working on it ”

Heard that before. Said that before. Even still saying that 🤣🤭

Nothing to thanks, let know when it Solved.