LLM provider error: Connection error. But my network is working fine.

[n-WN]

What version of Kimi CLI is running?

kimi, version 0.60

Which open platform/subscription were you using?

kimi-for-coding

Which model were you using?

kimi-for-coding

What platform is your computer?

No response

What issue are you seeing?

New seesion:

test@VideoApps✨ 分析当前repo
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 分析当前repo                                                                                                                                                                        │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
LLM provider error: Connection error.

What steps can reproduce the bug?

New seesion:

test@VideoApps✨ 分析当前repo
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 分析当前repo                                                                                                                                                                        │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
LLM provider error: Connection error.

What is the expected behavior?

Normal interaction.

Additional information

No response

[stdrc]

Is this temporary or lasting for a long time?

[n-WN]

Is this temporary or lasting for a long time?

This has been going on for a long time.

[n-WN]

sembra che la logica lato client non sia abbastanza robusta.

• Per un certo dominio, IPv6 ha un errore;
• Il client ha provato IPv6 solo una volta e ha segnalato un errore direttamente, senza tentare automaticamente IPv4.

---

it seems that the client-side logic is not robust enough.

• For a certain domain, IPv6 has an error;
• The client only tried IPv6 once and reported an error directly, without automatically trying IPv4.

[n-WN]

Can you assign this issue to me? @stdrc

[stdrc]

Can you assign this issue to me? @stdrc

Sure

[n-WN]

@stdrc 已经确认：
我的电脑当前 IPv6 出口不通（TCP 能连上，TLS 握手读不到字节），而 IPv4 一切正常。这与当前 issue 场景完全一致，说明“默认优先 IPv6 且失败即报错”的客户端会在我的环境无法正常通讯

预期：首次连接失败 -> 本会话自动切换到 IPv4 并保持，也能避免创造一个 export KIMI_PREFER_IPV4=1，一个不那么重要的环境变量/用户配置

---

@stdrc has confirmed:
My computer's current IPv6 export is blocked (TCP can be connected, but TLS handshake cannot read bytes), but everything is normal with IPv4. This is completely consistent with the current issue scenario. It means that the client that "prefers IPv6 by default and reports an error if it fails" will not be able to communicate normally in my environment.

Expectation: First connection failure -> This session automatically switches to IPv4 and remains, which also avoids creating an export KIMI_PREFER_IPV4=1, a less important environment variable/user configuration

[n-WN]

Analysis report, I find it quite interesting (I can learn some things).

https://gist.github.com/n-WN/a8ea44a5367c5f3cf9e61f672694500d

[n-WN]

If this is the case, it seems reasonable to modify {OpenAI SDK / HTTPX} Argument. Do you think it's a good idea?

@stdrc 已经确认： 我的电脑当前 IPv6 出口不通（TCP 能连上，TLS 握手读不到字节），而 IPv4 一切正常。这与当前 issue 场景完全一致，说明“默认优先 IPv6 且失败即报错”的客户端会在我的环境无法正常通讯

预期：首次连接失败 -> 本会话自动切换到 IPv4 并保持，也能避免创造一个 export KIMI_PREFER_IPV4=1，一个不那么重要的环境变量/用户配置

@stdrc has confirmed: My computer's current IPv6 export is blocked (TCP can be connected, but TLS handshake cannot read bytes), but everything is normal with IPv4. This is completely consistent with the current issue scenario. It means that the client that "prefers IPv6 by default and reports an error if it fails" will not be able to communicate normally in my environment.

Expectation: First connection failure -> This session automatically switches to IPv4 and remains, which also avoids creating an export KIMI_PREFER_IPV4=1, a less important environment variable/user configuration