Bad - 钛刻 - 科技风向旗 - 深度刻画技术趋势,引领数字未来 - 钛刻科技 | TCTI.cn - 钛刻 (TCTI.cn) 为您提供最前沿的硬核科技资讯、深度评测和未来技术趋势分析。
如题，刚刚还好好的，突然就报错无法使用了。 错误：bad response status code 422, message: model not found: “gemini-3.1-pro-preview”, body: {“error”:{“message”:“model
tech LinuxDo 最新话题 2026-05-13 17:30:41+08:00
Bad request (400) 供应商拒绝了请求格式。健康检查的探测格式可能与实际使用不同。 10 个帖子 - 5 位参与者 阅读完整话题
tech LinuxDo 最新话题 2026-05-13 13:55:12+08:00
报错502：Unexpected status 502 Bad Gateway: Unknown error, url: 但是cc-switch接中转站codex的api就用的好好的，接我朋友的自建号池的api也是好好的 让gpt排查下说是"Codex v0.130.0
tech LinuxDo 最新话题 2026-05-13 11:36:56+08:00
API Error: {“type”:“error”,“error”:{“message”:“操作失败”,“code”:“500”},“request_id”:“20260511163032ac828d5a89f04071”} 502 Bad Gateway Powered by
tech LinuxDo 最新话题 2026-05-11 16:34:58+08:00
求助佬友们，ccswitch配置了cc第三方apikey之后，报错400 “ 1. newapi 检查被拒: Bad request (400) 供应商拒绝了请求格式。健康检查的探测格式可能与实际使用不同。” 配置如下： 4 个帖子 - 2 位参与者 阅读完整话题
tech LinuxDo 最新话题 2026-05-11 15:48:00+08:00
报错信息如下 cap的网络代理配置 代理用的clash端口是7897 clash里配置了规则代理 ccswitch的配置如下 9 个帖子 - 6 位参与者 阅读完整话题
tech LinuxDo 最新话题 2026-05-09 16:53:11+08:00
HTTP 400 {"error":{"message":"Error","details":[{"error":"ERROR_BAD_REQUEST",&qu
tech LinuxDo 最新话题 2026-05-09 15:36:36+08:00
刚刚似乎有一分钟500 bad gateway不知道有没有人遇到，反正是被我抓到了 我的心理活动 1.先自我怀疑 怀疑浏览器是不是缓存或者是啥的问题 换浏览器后排除不是 再怀疑提子，换了梯子还不行 再怀疑是不是我欠费断网了，发现正常联网 得出结论L站挂了，结论刚得出来，他又好了。
tech LinuxDo 最新话题 2026-05-08 22:01:21+08:00
bad response status code 503, message: Service is too busy. We advise users to temporarily switch to alternative LLM API service providers.,
tech LinuxDo 最新话题 2026-05-08 17:21:38+08:00
Trajectory ID: b3761e14-3144-xxx-9e94-xxxxx Error: HTTP 400 Bad Request Sherlog: TraceID: 0x533faxxxxxcf2f Headers: {“Alt-Svc”:[“h3=":4
tech linux.do 2026-05-06 16:47:41+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech V2EX - 技术 2026-05-06 15:31:48+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech www.v2ex.com 2026-05-06 15:09:16+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 14:08:03+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech www.v2ex.com 2026-05-06 14:02:59+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 13:56:13+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 13:44:32+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 13:16:39+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 12:28:07+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 12:10:01+08:00
，今天调用报 bad response status code 429, message: Error from provider (DeepSeek): Too many requests. Please pace your requests reasonably. Your
tech v2ex.com 2026-05-06 11:58:16+08:00