[Bug] Account suspended after normal usage

[mingzu1204]

📦 部署方式

Other

📌 软件版本

latest

💻 系统环境

Windows

📌 系统版本

Windows 11

🐛 问题描述

After using this project for normal conversations and testing, the account was suspended unexpectedly

📷 复现步骤

No response

🚦 期望结果

No response

📝 补充信息

No response

[Arayaki]

same

[githubdulong]

Can confirm this issue. Multiple accounts (+86 phones) got muted/suspended silently with biz_code=14 and user is muted in logs around May 12-13. The /users/login and /chat/create_pow_challenge endpoints return EOF or fail with upload failures.\n\nDeepSeek might have updated their risk control/fingerprinting system to target the script's request patterns.

[ostapBender97]

same

[blazelicn]

same，由于违反用户使用规范，你的账号已被禁言至 2026 年 5 月 14 日 08:30，如有疑问请 。

[quanghufi]

same issue

[qq458249269]

+1，仅仅点了测试api

[FuCheng-G]

same

[shenyaocan]

[parkerisme]

是不是要凉了

[sdsdsdff]

I can reproduce a related symptom on a Docker deployment running the latest image.

Environment:

• Deployment: Docker (ghcr.io/cjackhwang/ds2api:latest)
• Image label version: v4.6.1
• Image revision: 8316cf8a0352e900e03ce600b792083f590d80e2
• /v1/models still returns HTTP 200, so the service itself is alive.
• current_input_file is enabled with min_chars: 0 via /admin/settings.

Observed logs:

time=2026-05-13T09:48:21+08:00 level=WARN msg="[upload_file] failed" status=200 code=0 biz_code=14 msg="" biz_msg="user is muted" account=<redacted> filename=DS2API_HISTORY.txt
2026/05/13 09:48:23 "POST http://<host>/v1/chat/completions HTTP/1.1" ... - 500 131B

This repeats across multiple configured accounts. The admin account list still reports test_status: ok for the accounts, but real /v1/chat/completions requests fail because the upload-file path returns biz_code=14 / user is muted.

This seems related to the account suspension / muted-account behavior reported here, and also related to #285 because the upload-file failure is surfaced to clients as a generic 500, making it look like a server crash even though the local service and model-list endpoint are healthy.

Possible useful detail: since current_input_file.enabled=true and min_chars=0, the service appears to hit the DeepSeek file-upload path for ordinary requests. If DeepSeek is now restricting or muting accounts when this path is used, disabling current_input_file or raising min_chars might be a temporary mitigation, but I have not applied that change yet.

[shenyaocan]

是否意味只配置一个账号，就可以安全使用吗？ 在 2026-05-13 10:16:57，"sunss" ***@***.***> 写道： sdsdsdff left a comment (CJackHwang/ds2api#506) I can reproduce a related symptom on a Docker deployment running the latest image. Environment: Deployment: Docker (ghcr.io/cjackhwang/ds2api:latest) Image label version: v4.6.1 Image revision: 8316cf8 /v1/models still returns HTTP 200, so the service itself is alive. current_input_file is enabled with min_chars: 0 via /admin/settings. Observed logs: time=2026-05-13T09:48:21+08:00 level=WARN msg="[upload_file] failed" status=200 code=0 biz_code=14 msg="" biz_msg="user is muted" account=<redacted> filename=DS2API_HISTORY.txt 2026/05/13 09:48:23 "POST http://<host>/v1/chat/completions HTTP/1.1" ... - 500 131B This repeats across multiple configured accounts. The admin account list still reports test_status: ok for the accounts, but real /v1/chat/completions requests fail because the upload-file path returns biz_code=14 / user is muted. This seems related to the account suspension / muted-account behavior reported here, and also related to #285 because the upload-file failure is surfaced to clients as a generic 500, making it look like a server crash even though the local service and model-list endpoint are healthy. Possible useful detail: since current_input_file.enabled=true and min_chars=0, the service appears to hit the DeepSeek file-upload path for ordinary requests. If DeepSeek is now restricting or muting accounts when this path is used, disabling current_input_file or raising min_chars might be a temporary mitigation, but I have not applied that change yet. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.Message ID: ***@***.***>