[BUG] can‘t use kimi’s API in WSL2

[BailuH]

Problem (one or two sentences)

I can use roo code without any problems in my windows‘s VSCode, but when it comes to WSL2, it can not be used.

Context (who is affected and when)

Reproduction steps

run WSL2 by extension in VSCode, you'll find your API configurations all same as your parent OS, but it doesn't work.

Expected result

1

Actual result

1

Variations tried (optional)

No response

App Version

latest

API Provider (optional)

Not Applicable / Other

Model Used (optional)

kimi-k2

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

I'd like to help with this issue, but I need some clarification to ensure I implement the right solution. Could you please provide more details on the following:

1. What specific error messages do you see when trying to use Roo Code in WSL2? (e.g., "API key not found", "Authentication failed", etc.)

2. Can you confirm the API configurations appear in the settings UI when in WSL2? (Do you see your provider and model selections, but they just don't work?)

3. Have you tried re-entering your API key while connected to WSL2? If so, does it work after re-entering?

4. Which API provider are you using? (You mentioned kimi-k2, but I want to confirm if it's through Fireworks, OpenRouter, or another provider)

5. Do you see any error messages in the VSCode Developer Console? (Help > Toggle Developer Tools > Console tab)

This information will help me understand whether this is:

• A secrets storage synchronization issue between Windows and WSL2
• A network/connectivity issue specific to WSL2
• An API endpoint accessibility issue from WSL2

Please tag @roomote in your response with the answers, and I'll be happy to implement the fix once I have this information.

[BailuH]

Thanks for your response! I can provide some information you may need.

1. The specific error messages is "OpenAI completion error: Connection error."
2. yes, I can "see"(but I'm not sure if the API configuration is correct, since the error code mentioned OpenAI ) the API configurations just as I used in WINDOWS.
3. I've tried re-entering your API key while connected to WSL2, even used a brand new key. but it failed to work.
4. The API provider is moonshot. To be exact, api.moonshot.cn.
5. The console:

@roomote

Thanks for the detailed information! I've seen your comment and will explore a potential fix for the WSL2 connection issue with Moonshot API. The "Connection error" suggests this might be related to network configuration or SSL certificate handling in WSL2 environments. I'll investigate the codebase and open a PR to share my progress.

I've opened a draft PR with my attempt at addressing this issue: #10044

What I've Implemented

The fix includes:

1. WSL2 Detection - Added automatic detection of WSL2 environments
2. SSL Configuration - Modified the OpenAI client initialization to create custom HTTP agents with rejectUnauthorized: false in WSL2 environments
3. Enhanced Error Messages - Updated error handling to provide WSL2-specific troubleshooting guidance when connection errors occur
4. Test Coverage - Added comprehensive tests for the WSL detection functionality

Why This Should Fix Your Issue

The "Connection error" you're experiencing with the Moonshot API (api.moonshot.cn) is a known issue in WSL2 environments related to SSL certificate verification. WSL2 often has certificate store synchronization issues with Windows, causing SSL verification to fail for certain APIs.

This fix automatically detects when running in WSL2 and configures the HTTP agent to work around these certificate issues while maintaining security in non-WSL environments.

Testing

Could you test this fix when you have a chance? You can install the extension from the PR branch or wait for it to be merged and released.

Feedback welcome!

[hannesrudolph]

Apologies for the delayed response.

This is a bug report, but the current repro description (“run WSL2 by extension in VS Code”) is not specific enough to diagnose or test reliably, and the previously-linked draft PR is no longer active.

Please open a new issue (linking back to this one) with:

1. Concrete repro steps (numbered, deterministic)
2. Expected vs actual
3. Versions: Roo Code extension, VS Code, Windows, WSL distro, and whether this is Remote - WSL, Dev Containers, SSH, or local
4. Provider details: endpoint you are using (you mentioned api.moonshot.cn), model name, and whether any proxy is configured in WSL
5. Evidence the endpoint is reachable from inside WSL:
   • curl -v https://api.moonshot.cn (redact tokens)
6. Errors:
   • Full text stack trace from VS Code Developer Tools console
   • Relevant lines from the Roo Code output channel

Without the above, we cannot reproduce or validate a fix.