mirror of
https://github.com/labring/FastGPT.git
synced 2026-04-27 02:08:10 +08:00
zjj-225
765ec526cc
* docs(faq): 更新常见问题文档并新增注意事项页面 - 在 error.mdx 中调整问题序号并新增 OCR 配置问题 - 新增 attention.mdx 页面，提供问题排查步骤和技术支持指引 - 重构 dataset.mdx 内容结构，使用数字序号并补充知识库闪烁问题 * docs: 重构私有部署故障排查文档结构并新增详细指南 将原有的 FAQ 文档拆分为多个专题文档，包括通用问题排查、S3问题、OneAPI错误、模型可用性问题和排查方法。更新了导航菜单和目录结构，使文档组织更清晰，便于用户快速定位和解决特定问题。 新增了详细的故障排查步骤、CURL测试示例和具体错误解决方案，特别是针对对象存储连接、签名错误和模型调用失败等常见问题提供了更全面的指导。 * docs: 移除已弃用的 OneAPI 错误排查文档 移除 `oneapi-errors` 相关文档文件，因其内容已过时或合并至其他章节。同步更新中英文文档目录和元数据文件中的引用。 * docs: 更新文档FAQ内容，移除过时条目并重新编号 - 删除关于OneAPI官网的过时FAQ条目 - 重新编号故障排除FAQ章节，使序号连续 - 同步更新中英文文档内容保持一致 * docs: 重构FAQ和自托管文档结构，合并错误排查内容 将原FAQ中的“报错”和“注意”章节迁移至自托管文档的“故障排查”目录下 在model-errors.mdx中整合常见错误解决方案，如“上游负载饱和”和“Connection Error” 更新meta.json和toc.mdx文件以反映新的文档结构 --------- Co-authored-by: Archer <545436317@qq.com>
28 lines
1.3 KiB
Plaintext
28 lines
1.3 KiB
Plaintext
---
|
|
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.
|