Files
FastGPT/document/content/docs/self-host/troubleshooting/methods.en.mdx
T
zjj-225 f057a2ae19 docs(faq): 更新常见问题文档并新增注意事项页面 (#6465)
* docs(faq): 更新常见问题文档并新增注意事项页面

- 在 error.mdx 中调整问题序号并新增 OCR 配置问题
- 新增 attention.mdx 页面,提供问题排查步骤和技术支持指引
- 重构 dataset.mdx 内容结构,使用数字序号并补充知识库闪烁问题

* docs: 重构私有部署故障排查文档结构并新增详细指南

将原有的 FAQ 文档拆分为多个专题文档,包括通用问题排查、S3问题、OneAPI错误、模型可用性问题和排查方法。更新了导航菜单和目录结构,使文档组织更清晰,便于用户快速定位和解决特定问题。

新增了详细的故障排查步骤、CURL测试示例和具体错误解决方案,特别是针对对象存储连接、签名错误和模型调用失败等常见问题提供了更全面的指导。

* docs: 移除已弃用的 OneAPI 错误排查文档

移除 `oneapi-errors` 相关文档文件,因其内容已过时或合并至其他章节。同步更新中英文文档目录和元数据文件中的引用。

* docs: 更新文档FAQ内容,移除过时条目并重新编号

- 删除关于OneAPI官网的过时FAQ条目
- 重新编号故障排除FAQ章节,使序号连续
- 同步更新中英文文档内容保持一致

---------

Co-authored-by: Archer <545436317@qq.com>
2026-03-17 14:44:54 +08:00

28 lines
1.2 KiB
Plaintext

---
title: Troubleshooting Methods
description: FastGPT Self-Hosting Common Troubleshooting Methods
---
## 1. Troubleshooting Methods
You can first look for [Issue](https://github.com/labring/FastGPT/issues), or raise a new Issue. For private deployment errors, be sure to provide detailed operation steps, logs, and screenshots, otherwise it is difficult to troubleshoot.
### (1) Get Backend Errors
1. `docker ps -a` View the running status of all containers, check if they are all running. If there is an abnormality, try `docker logs container_name` to view the corresponding log.
2. If the containers are running normally, `docker logs container_name` to view the error log.
---
### (2) Frontend Errors
When a frontend error occurs, the page will crash and prompt to check the console log. You can open the browser console and view the log in `console`. You can also click the hyperlink of the corresponding log, which will prompt to the specific error file. You can provide these detailed error information to facilitate troubleshooting.
---
### (3) OneAPI Errors
Those with `requestId` are OneAPI prompts errors, mostly due to model interface errors. You can refer to [OneAPI Common Errors](/docs/self-host/faq/#三常见的-oneapi-错误)
---