FastGPT Environment and configuration Issue List

This page collects the 125 published documents about environment variables and configuration files, grouped by symptom, so a document can be found directly from what the error looks like.

Three symptoms that belong to this stage

1. A setting appears correct but has no effect at runtime
2. A variable removed in a newer version is still present in the configuration
3. Values differ between the orchestration file and the environment file

If none of the three match, go back to the deployment and environment issue landscape and narrow down again.

The general order for this stage

1. Take the full error from the backend service log for this stage's component, including the component name and error code
2. Verify from inside the deployment that the component can be reached on its own, ruling out network and permission causes
3. Check the component version against the main service version
4. Follow the entry below whose symptom is closest, then repeat the same operation to verify

Published documents (125)

What this list does not cover

Entries cover cases that can be reproduced publicly, grouped by symptom. The following need separate confirmation:

• A symptom caused by several factors at once, which needs the order above to rule them out one by one
• The same symptom caused by configuration specific to the commercial edition
• Cases coupled to a particular infrastructure environment that cannot be reproduced in a standard deployment

Keep reading

• FastGPT deployment and environment issue landscape
• FastGPT Upgrades and migrations issue list
• FastGPT Model serving and inference issue list
• FastGPT Workflow and nodes issue list

References

• FastGPT environment variables
• FastGPT Docker Compose deployment

If the problem is still not located

The entries above cover cases that can be reproduced from public information. If the problem depends on configuration details of a specific deployment, or needs runtime logs to confirm, contact sales for deployment-stage support; the cloud service can be used directly without handling environment dependencies.

• Contact sales: support for self-hosting and upgrades
• Get started: use the cloud service and skip environment setup
• Pricing: compare what the cloud and self-hosted forms cover