"Authorization failed, please check your login status"

[emresaracoglu]

What version of Kimi Code CLI is running?

1.1

Which open platform/subscription were you using?

/login

Which model were you using?

kimi-for-codin

What platform is your computer?

Debian 13 Server

What issue are you seeing?

• Used WriteFile (xxxxxxx.xxx)
Authorization failed, please check your login status
root@www💫

On an ongoing mission, the session is suddenly closed.

What steps can reproduce the bug?

It is determined that the ongoing duties should be held suddenly. I re-entered 5-6 times in one hour.

What is the expected behavior?

No response

Additional information

No response

[xiaoju111a]

Perhaps you can use /setup to set the Kimi code apikey. The /login endpoint may be unstable.

[xxchan]

Should be fixed by #738

[zxch3n]

It still happens in v1.3.

[evenluo]

still in v1.3

[xiaoju111a]

still in v1.3

try new version, v1.5 fixed it.

[Downchuck]

still broken. using v1.5.

[evenluo]

use api-key instead. It's stable

[xxchan]

Should be fixed by #898.
Sorry for the bad experience. Please try 1.7 and report if you meet authorization failure again.

[Downchuck]

Should be fixed by #898. Sorry for the bad experience. Please try 1.7 and report if you meet authorization failure again.

Almost there! So in 1.7 a long running task still hit an authentication issue, though exiting and just re-entering (potentially just saying continue could have worked) did work, I didn't have to log back in again -- but I suspect that the token it had expired after 15 minutes or such and it just gave up on renewing instead of renewing and continuing.

[oldtree]

Authorization failed, please check your login status.
1.重新生成、配置新的key ，失败。登录后继续报错
2.登出后再登入，失败。登录后继续报错
3.尝试不同的登录方式，都失败。登录后继续报错

3.1. Kimi Code
3.2. Moonshot AI Open Platform (moonshot.cn)
3.3. Moonshot AI Open Platform (moonshot.ai)

4.清理 credentials/kimi-code.json 文件，重新登录 /login，登录完成后，仍是 Authorization failed, please check your login status. 的错误
5.更新

[services.moonshot_fetch]
            base_url = "https://api.kimi.com/coding/v1/fetch"
            api_key = ""

依旧失败

6. kimi web 可以打开，但是同样的错误

---

kimi --version
kimi, version 1.7.0

---

Authorization failed, please check your login status.

1. Regenerate and configure new keys, but failed. Error continues after logging in
2. Log out and then log in again, failed. Error continues after logging in
3. Tried different login methods, all failed. Error continues after logging in

3.1. Kimi Code
3.2. Moonshot AI Open Platform (moonshot.cn)
3.3. Moonshot AI Open Platform (moonshot.ai)

4. Clean the credentials/kimi-code.json file and log in to /login again. After the login is completed, the error "Authorization failed, please check your login status." is still there.

---

kimi --version
kimi, version 1.7.0

[oldtree]

kimi, version 1.8.0 也有同样的问题 。vibe coding 重构系统，记得 系统测试

[oldtree]

~/.kimi/config.toml 在这个文件中，即使我手动填写 key,但是 /login 之后，还是会清空我填写的 api-key

---

~/.kimi/config.toml In this file, even if I fill in the key manually, the api-key I filled in will still be cleared after /login

[oldtree]

kimi --config-file ~/.kimi/config.toml
通过命令行指定文件启动，仍旧失败

---

kimi --config-file ~/.kimi/config.toml
Starting by specifying a file on the command line still fails.

[xiaoju111a]

Authorization failed, please check your login status. 1.重新生成、配置新的key ，失败。登录后继续报错 2.登出后再登入，失败。登录后继续报错 3.尝试不同的登录方式，都失败。登录后继续报错

3.1. Kimi Code
3.2. Moonshot AI Open Platform (moonshot.cn)
3.3. Moonshot AI Open Platform (moonshot.ai)

4.清理 credentials/kimi-code.json 文件，重新登录 /login，登录完成后，仍是 Authorization failed, please check your login status. 的错误 5.更新

[services.moonshot_fetch]
            base_url = "https://api.kimi.com/coding/v1/fetch"
            api_key = ""

依旧失败

6. kimi web 可以打开，但是同样的错误

kimi --version kimi, version 1.7.0

Authorization failed, please check your login status.

1. Regenerate and configure new keys, but failed. Error continues after logging in
2. Log out and then log in again, failed. Error continues after logging in
3. Tried different login methods, all failed. Error continues after logging in

3.1. Kimi Code
3.2. Moonshot AI Open Platform (moonshot.cn)
3.3. Moonshot AI Open Platform (moonshot.ai)

4. Clean the credentials/kimi-code.json file and log in to /login again. After the login is completed, the error "Authorization failed, please check your login status." is still there.

kimi --version kimi, version 1.7.0

尝试删除config.toml试试

[oldtree]

Authorization failed, please check your login status. 1.重新生成、配置新的key ，失败。登录后继续报错 2.登出后再登入，失败。登录后继续报错 3.尝试不同的登录方式，都失败。登录后继续报错

3.1. Kimi Code
3.2. Moonshot AI Open Platform (moonshot.cn)
3.3. Moonshot AI Open Platform (moonshot.ai)

4.清理 credentials/kimi-code.json 文件，重新登录 /login，登录完成后，仍是 Authorization failed, please check your login status. 的错误 5.更新

[services.moonshot_fetch]
            base_url = "https://api.kimi.com/coding/v1/fetch"
            api_key = ""

依旧失败

6. kimi web 可以打开，但是同样的错误

kimi --version kimi, version 1.7.0
Authorization failed, please check your login status.

1. Regenerate and configure new keys, but failed. Error continues after logging in
2. Log out and then log in again, failed. Error continues after logging in
3. Tried different login methods, all failed. Error continues after logging in

3.1. Kimi Code
3.2. Moonshot AI Open Platform (moonshot.cn)
3.3. Moonshot AI Open Platform (moonshot.ai)

4. Clean the credentials/kimi-code.json file and log in to /login again. After the login is completed, the error "Authorization failed, please check your login status." is still there.

kimi --version kimi, version 1.7.0

尝试删除config.toml试试

重装之后，依旧是登录返回 success，但是输入提示词报 ‘Authorization failed, please check your login status.’ 错误。
删除 config.toml 文件之后，输入提示词就会报‘LLM provider error: Connection error.’

到现在还没有哪一个 AI coding 工具有过这么糟糕的体验

[oldtree]

我撤销了export 的环境变量配置（https://moonshotai.github.io/kimi-cli/zh/configuration/env-vars.html），
重装之后，问题不再有了。

---

I revoked the export environment variable configuration (https://moonshotai.github.io/kimi-cli/zh/configuration/env-vars.html),
After reinstalling, the problem is no longer there.