[Rovo Dev CLI] SSL Certificate and Encoding (cp932) issues on Windows 11

[sumi takashi]

I am experiencing two issues while running acli rovodev run in my environment. I've found temporary workarounds, but I’m looking for a permanent solution.

Environment:

• OS: Windows 11

• Shell: PowerShell

• Network: Behind a Zscaler proxy

Issue 1: SSL Certificate Verification Failed When running via proxy, I get a [SSL: CERTIFICATE_VERIFY_FAILED] error.

• Workaround: Disabling Zscaler temporarily.

• Question: Is there a way to specify a custom CA certificate bundle for Rovo Dev CLI?

###

2026-03-11 09:10:37.046 | 2608 (2608) | WARNING | Request error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1028). Retrying...
2026-03-11 09:10:37.047 | 2608 (2608) | ERROR | Failed to fetch sites from https://api.atlassian.com/rovodev/v3/sites: Failed to connect to the Rovo Dev API on request error, please try again later.

###

Issue 2: Character Decoding Error (cp932) The CLI fails with a 'cp932' codec can't decode byte 0x94 error, likely due to a full-width character (dash "—") in config.yml.

• Workaround: Enabling "Beta: Use Unicode UTF-8 for worldwide language support" in Windows Region settings.

• Question: Is it possible to make the CLI handle UTF-8 encoding by default on Windows without changing system-wide locale settings?

###

2026-03-19 17:05:57.437 | 11092 (11092) | ERROR | Error handling beta customer site selection: 'cp932' codec can't decode byte 0x94 in position 3191: illegal multibyte sequence

###

[Dr Valeri Colon _Connect Centric_]

@sumi takashi welcome to the community . This sounds like two separate Windows-specific issues, and neither looks like user error.

For SSL, Atlassian’s docs don’t show a supported way to pass a custom CA bundle into Rovo Dev CLI, so behind Zscaler it may fail unless the cert chain is trusted by the environment the CLI uses. For the cp932 error, there also doesn’t seem to be an official per-process UTF-8 setting for ACLI/Rovo Dev on Windows. So today this looks more like a CLI limitation/bug than a bad config. Best next step is Atlassian Support with logs.