diff --git a/document/content/docs/faq/error.en.mdx b/document/content/docs/faq/error.en.mdx deleted file mode 100644 index ef6479462d..0000000000 --- a/document/content/docs/faq/error.en.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Errors ---- - -1. ### "Current group upstream load is saturated, please try again later" (request id: 202407100753411462086782835521) - -This is an OneAPI channel issue. Try switching to a different model or a different relay provider. - -1. ### "Connection Error" in logs when using the API - -Most likely the API key is pointing to OpenAI's API, but the server is deployed in mainland China and can't reach overseas endpoints. Use a relay service or reverse proxy to resolve the connectivity issue. diff --git a/document/content/docs/faq/error.mdx b/document/content/docs/faq/error.mdx deleted file mode 100644 index 344a8008ba..0000000000 --- a/document/content/docs/faq/error.mdx +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: 报错 ---- - -1. ### 当前分组上游负载已饱和，请稍后再试(request id:202407100753411462086782835521) - -是oneapi渠道的问题，可以换个模型用或者换一家中转站 - -2. ### 使用API时在日志中报错Connection Error - -大概率是api-key填写了openapi，然后部署的服务器在国内，不能访问海外的api，可以使用中转或者反代的手段解决访问不到的问题 - -3. ### 开启图片索引报 400 -需在 Admin→系统配置中正确配置OCR模型 - diff --git a/document/content/docs/faq/meta.en.json b/document/content/docs/faq/meta.en.json index e48398132a..1efec50f09 100644 --- a/document/content/docs/faq/meta.en.json +++ b/document/content/docs/faq/meta.en.json @@ -7,7 +7,6 @@ "chat", "dataset", "external_channel_integration", - "error", "points_consumption", "other" ] diff --git a/document/content/docs/faq/meta.json b/document/content/docs/faq/meta.json index 6c8c391933..f7feca99e7 100644 --- a/document/content/docs/faq/meta.json +++ b/document/content/docs/faq/meta.json @@ -7,7 +7,6 @@ "chat", "dataset", "external_channel_integration", - "error", "points_consumption", "other" ] diff --git a/document/content/docs/self-host/meta.en.json b/document/content/docs/self-host/meta.en.json index 6a949147fa..c445b10453 100644 --- a/document/content/docs/self-host/meta.en.json +++ b/document/content/docs/self-host/meta.en.json @@ -13,6 +13,7 @@ "config/json", "config/signoz", "---Troubleshooting---", + "troubleshooting/attention", "troubleshooting/faq", "troubleshooting/methods", "troubleshooting/model-errors", diff --git a/document/content/docs/self-host/meta.json b/document/content/docs/self-host/meta.json index 9ec4e5ef2b..3f2954d343 100644 --- a/document/content/docs/self-host/meta.json +++ b/document/content/docs/self-host/meta.json @@ -13,6 +13,7 @@ "config/json", "config/signoz", "---故障排查---", + "troubleshooting/attention", "troubleshooting/faq", "troubleshooting/methods", "troubleshooting/model-errors", diff --git a/document/content/docs/self-host/troubleshooting/attention.en.mdx b/document/content/docs/self-host/troubleshooting/attention.en.mdx new file mode 100644 index 0000000000..7f45d2e097 --- /dev/null +++ b/document/content/docs/self-host/troubleshooting/attention.en.mdx @@ -0,0 +1,27 @@ +--- +title: Troubleshooting Notes +description: FastGPT usage notes +--- + +# Troubleshooting Notes + +If you encounter issues while using FastGPT, follow the steps below to troubleshoot and resolve them. + +## 1. Check Version and Upgrade +Many known issues are fixed in newer releases. Before reporting a problem, verify your version first: +- **Check version**: View the current running version on the FastGPT homepage or in the admin panel. +- **Upgrade recommendation**: If you are not on the latest version, follow the [Upgrade Guide](../upgrading/upgrade-intruction) to update to the latest stable release. + +## 2. Troubleshooting Steps +If the issue still exists after upgrading, check in this order: +- **Check logs**: Review Docker container logs or server logs and locate the specific error stack. +- **Clear cache**: Clear browser cache or retry in incognito mode. +- **Environment check**: Ensure MongoDB and PostgreSQL/Milvus connections are healthy and API keys are valid. + +## 3. Contact Technical Support +If the issue still cannot be resolved, contact us through: +- **Community feedback**: Search for similar issues in GitHub Issues or community channels. +- **Provide details**: When contacting support, include: + - Full version number currently in use. + - Detailed issue description with reproduction steps. + - Related system error logs or screenshots. diff --git a/document/content/docs/faq/attention.mdx b/document/content/docs/self-host/troubleshooting/attention.mdx similarity index 92% rename from document/content/docs/faq/attention.mdx rename to document/content/docs/self-host/troubleshooting/attention.mdx index 4c9c65faee..2f727feee2 100644 --- a/document/content/docs/faq/attention.mdx +++ b/document/content/docs/self-host/troubleshooting/attention.mdx @@ -1,5 +1,5 @@ --- -title: 注意 +title: 排查注意 description: FastGPT注意事项 --- @@ -10,7 +10,7 @@ description: FastGPT注意事项 ## 1. 版本检查与升级 很多已知问题已在最新版本中得到修复。在反馈问题前，请务必确认您的版本情况： - **检查版本**：在 FastGPT 首页或管理后台查看当前运行的版本号。 -- **升级建议**：如果当前不是最新版本，建议先参考 [更新指南](../development/upgrading) 升级至最新稳定版。 +- **升级建议**：如果当前不是最新版本，建议先参考 [更新指南](../upgrading/upgrade-intruction) 升级至最新稳定版。 ## 2. 问题排查步骤 若升级后问题依然存在，请按以下顺序排查： diff --git a/document/content/docs/self-host/troubleshooting/model-errors.en.mdx b/document/content/docs/self-host/troubleshooting/model-errors.en.mdx index 7fbd2e308b..0ab3c722bb 100644 --- a/document/content/docs/self-host/troubleshooting/model-errors.en.mdx +++ b/document/content/docs/self-host/troubleshooting/model-errors.en.mdx @@ -1,6 +1,6 @@ --- -title: Model Availability Troubleshooting -description: FastGPT Self-Hosting Model Availability Troubleshooting +title: Model Troubleshooting +description: FastGPT Self-Hosting Model Troubleshooting --- @@ -98,3 +98,21 @@ Possible error issues: 1. Domestic models hit risk control. 2. Unsupported model parameters: only keep messages and necessary parameters for testing, delete other parameters for testing. + +--- + +### (3) "Current group upstream load is saturated, please try again later" + +If you encounter this error (e.g. `request id:xxx`) in the logs or response, this is typically an OneAPI channel issue. Try switching to a different model or a different relay provider. + +--- + +### (4) "Connection Error" in logs when using the API + +Most likely the API key is pointing to OpenAI's endpoint, but the server is deployed in mainland China and can't reach overseas endpoints. Use a relay service or reverse proxy to resolve the connectivity issue. + +--- + +### (5) Enable image indexing reports 400 + +You need to correctly configure the OCR model in `Admin` -> `System Configuration`. diff --git a/document/content/docs/self-host/troubleshooting/model-errors.mdx b/document/content/docs/self-host/troubleshooting/model-errors.mdx index f921d25bcb..7fd05b5d47 100644 --- a/document/content/docs/self-host/troubleshooting/model-errors.mdx +++ b/document/content/docs/self-host/troubleshooting/model-errors.mdx @@ -1,6 +1,6 @@ --- -title: 模型可用性问题排查 -description: FastGPT 私有部署模型可用性问题排查 +title: 模型问题排查 +description: FastGPT 私有部署模型问题排查 --- @@ -255,3 +255,21 @@ curl --location --request POST 'https://oneapi.xxxx/v1/chat/completions' \ ### (4)向量检索得分大于 1 由于模型没有归一化导致的。目前仅支持归一化的模型。 + +--- + +### (5) 当前分组上游负载已饱和，请稍后再试 + +如果在日志或请求中遇到此错误（如 `request id:xxx`），这通常是 OneAPI 渠道的问题，可以换个模型使用或者换一家中转站。 + +--- + +### (6) 使用API时在日志中报错 Connection Error + +大概率是 API Key 填写了 OpenAI 的地址，但是部署的服务器在国内，不能访问海外的 API。可以使用中转或者反代的手段解决访问不到的问题。 + +--- + +### (7) 开启图片索引报 400 + +需在 `Admin` -> `系统配置` 中正确配置 OCR 模型。 diff --git a/document/content/docs/toc.en.mdx b/document/content/docs/toc.en.mdx index 4a1422c7a7..e67f3c4a33 100644 --- a/document/content/docs/toc.en.mdx +++ b/document/content/docs/toc.en.mdx @@ -6,7 +6,6 @@ description: FastGPT Toc - [/en/docs/faq/app](/en/docs/faq/app) - [/en/docs/faq/chat](/en/docs/faq/chat) - [/en/docs/faq/dataset](/en/docs/faq/dataset) -- [/en/docs/faq/error](/en/docs/faq/error) - [/en/docs/faq/external_channel_integration](/en/docs/faq/external_channel_integration) - [/en/docs/faq/other](/en/docs/faq/other) - [/en/docs/faq/points_consumption](/en/docs/faq/points_consumption) @@ -101,6 +100,7 @@ description: FastGPT Toc - [/en/docs/self-host/index](/en/docs/self-host/index) - [/en/docs/self-host/migration/docker_db](/en/docs/self-host/migration/docker_db) - [/en/docs/self-host/migration/docker_mongo](/en/docs/self-host/migration/docker_mongo) +- [/en/docs/self-host/troubleshooting/attention](/en/docs/self-host/troubleshooting/attention) - [/en/docs/self-host/troubleshooting/faq](/en/docs/self-host/troubleshooting/faq) - [/en/docs/self-host/troubleshooting/methods](/en/docs/self-host/troubleshooting/methods) - [/en/docs/self-host/troubleshooting/model-errors](/en/docs/self-host/troubleshooting/model-errors) diff --git a/document/content/docs/toc.mdx b/document/content/docs/toc.mdx index 1892639d90..7b9789ee14 100644 --- a/document/content/docs/toc.mdx +++ b/document/content/docs/toc.mdx @@ -4,10 +4,8 @@ description: FastGPT 文档目录 --- - [/docs/faq/app](/docs/faq/app) -- [/docs/faq/attention](/docs/faq/attention) - [/docs/faq/chat](/docs/faq/chat) - [/docs/faq/dataset](/docs/faq/dataset) -- [/docs/faq/error](/docs/faq/error) - [/docs/faq/external_channel_integration](/docs/faq/external_channel_integration) - [/docs/faq/other](/docs/faq/other) - [/docs/faq/points_consumption](/docs/faq/points_consumption) @@ -101,6 +99,7 @@ description: FastGPT 文档目录 - [/docs/self-host/index](/docs/self-host/index) - [/docs/self-host/migration/docker_db](/docs/self-host/migration/docker_db) - [/docs/self-host/migration/docker_mongo](/docs/self-host/migration/docker_mongo) +- [/docs/self-host/troubleshooting/attention](/docs/self-host/troubleshooting/attention) - [/docs/self-host/troubleshooting/faq](/docs/self-host/troubleshooting/faq) - [/docs/self-host/troubleshooting/methods](/docs/self-host/troubleshooting/methods) - [/docs/self-host/troubleshooting/model-errors](/docs/self-host/troubleshooting/model-errors) diff --git a/document/data/doc-last-modified.json b/document/data/doc-last-modified.json index a3fd7a7b35..ed5d7c9d15 100644 --- a/document/data/doc-last-modified.json +++ b/document/data/doc-last-modified.json @@ -1,19 +1,16 @@ { "document/content/docs/faq/app.en.mdx": "2026-02-26T22:14:30+08:00", "document/content/docs/faq/app.mdx": "2025-08-02T19:38:37+08:00", - "document/content/docs/faq/attention.mdx": "2026-02-26T11:41:53+08:00", "document/content/docs/faq/chat.en.mdx": "2026-02-26T22:14:30+08:00", "document/content/docs/faq/chat.mdx": "2025-08-02T19:38:37+08:00", "document/content/docs/faq/dataset.en.mdx": "2026-02-26T22:14:30+08:00", "document/content/docs/faq/dataset.mdx": "2026-02-26T11:41:53+08:00", - "document/content/docs/faq/error.en.mdx": "2026-02-26T22:14:30+08:00", - "document/content/docs/faq/error.mdx": "2026-02-26T11:41:53+08:00", "document/content/docs/faq/external_channel_integration.en.mdx": "2026-02-26T22:14:30+08:00", "document/content/docs/faq/external_channel_integration.mdx": "2025-08-02T19:38:37+08:00", "document/content/docs/faq/index.en.mdx": "2026-02-26T22:14:30+08:00", "document/content/docs/faq/index.mdx": "2025-08-02T19:38:37+08:00", - "document/content/docs/faq/other.en.mdx": "2026-02-26T22:14:30+08:00", - "document/content/docs/faq/other.mdx": "2025-08-04T22:07:52+08:00", + "document/content/docs/faq/other.en.mdx": "2026-03-14T18:13:05+08:00", + "document/content/docs/faq/other.mdx": "2026-03-14T18:13:05+08:00", "document/content/docs/faq/points_consumption.en.mdx": "2026-02-26T22:14:30+08:00", "document/content/docs/faq/points_consumption.mdx": "2025-08-02T19:38:37+08:00", "document/content/docs/introduction/cloud/faq.en.mdx": "2026-03-03T17:39:47+08:00", @@ -197,8 +194,8 @@ "document/content/docs/self-host/migration/docker_db.mdx": "2026-03-03T17:39:47+08:00", "document/content/docs/self-host/migration/docker_mongo.en.mdx": "2026-03-03T17:39:47+08:00", "document/content/docs/self-host/migration/docker_mongo.mdx": "2026-03-03T17:39:47+08:00", - "document/content/docs/self-host/troubleshooting/faq.en.mdx": "2026-03-12T15:26:02+08:00", - "document/content/docs/self-host/troubleshooting/faq.mdx": "2026-03-12T15:26:02+08:00", + "document/content/docs/self-host/troubleshooting/faq.en.mdx": "2026-03-14T18:13:05+08:00", + "document/content/docs/self-host/troubleshooting/faq.mdx": "2026-03-14T18:13:05+08:00", "document/content/docs/self-host/troubleshooting/methods.en.mdx": "2026-03-12T15:26:02+08:00", "document/content/docs/self-host/troubleshooting/methods.mdx": "2026-03-12T15:26:02+08:00", "document/content/docs/self-host/troubleshooting/model-errors.en.mdx": "2026-03-12T15:26:02+08:00", @@ -243,7 +240,7 @@ "document/content/docs/self-host/upgrading/4-14/4148.mdx": "2026-03-09T17:39:53+08:00", "document/content/docs/self-host/upgrading/4-14/41481.en.mdx": "2026-03-09T12:02:02+08:00", "document/content/docs/self-host/upgrading/4-14/41481.mdx": "2026-03-09T17:39:53+08:00", - "document/content/docs/self-host/upgrading/4-14/4149.mdx": "2026-03-12T20:51:00+08:00", + "document/content/docs/self-host/upgrading/4-14/4149.mdx": "2026-03-16T17:09:25+08:00", "document/content/docs/self-host/upgrading/outdated/40.en.mdx": "2026-03-03T17:39:47+08:00", "document/content/docs/self-host/upgrading/outdated/40.mdx": "2026-03-03T17:39:47+08:00", "document/content/docs/self-host/upgrading/outdated/41.en.mdx": "2026-03-03T17:39:47+08:00",