What this category of data looks like
The core unit of community report handling data is individual report tickets. It includes report submission information, reported content details, reporter information, audit rule matching results, and other related content. Daily documents include report tickets, processing records, appeal forms, and user notification templates. Data sources include the report system, content detail library, user history library, and audit rule library. Update rhythms are mostly real-time or daily. Fields include report ID, content ID, reporter, reported content snippet, disposal status, processing time limit, and other items. There are no quantitative indicators with fixed statistical calibers.
What constraints these characteristics impose on deployment and upgrade
This category of data primarily consists of real-time or daily updated ticket-style structured data. It relies on PostgreSQL and MongoDB to store core business information. Deployment must include high-availability configuration for database services, to prevent service failure to automatically recover after outages or other exceptions. During the upgrade process, read and write operations for ticket data must not be interrupted. Database connection parameters must also be verified for correctness, to avoid service startup failure caused by configuration changes. Additionally, daily processing involves multiple types of documents and notification templates. Storage and domain parameters must be configured in advance, to prevent resource access errors after upgrade that disrupt normal report handling workflows.
How to set configurations
These configurations apply to FastGPT v4.17.0.
| Config Item | Recommended Value | Rationale |
|---|---|---|
PG_URL | postgresql://username:password@pg-host:5432/fastgpt?sslmode=disable | Stores structured business data such as report tickets and processing records. Must specify correct database address, authentication information, and database name. Port is fixed to the default PostgreSQL port 5432. |
MONGODB_URI | mongodb://mongo-host:27017/fastgpt?authSource=admin | Stores unstructured data such as reported content snippets and user history records. Must configure correct cluster address and authentication parameters. Port is fixed to the default MongoDB port 27017. |
DB_MAX_LINK | 20–30 connections | Adapts to concurrent read/write requirements for community report handling, prevents service lag caused by exhausted connection pools. Can be adjusted based on actual concurrent volume and measured benchmarks. |
REDIS_URL | redis://redis-host:6379/0 | Caches temporary status of report processing and audit rules to reduce database read/write pressure. Port is fixed to the default Redis port 6379. |
FE_DOMAIN | https://your-community-domain.com | Used to generate jump links in user notification templates. Must match the frontend deployment domain to ensure normal navigation in notifications. |
STORAGE_S3_ENDPOINT | https://s3-cn-beijing.aliyuncs.com (or local storage address) | Stores file resources such as report attachments and audit screenshots. Must match the actual storage service endpoint in use. |
Three common mistakes
- Symptom: After Docker deployment and power restart, FastGPT fails to start. Logs show PostgreSQL failed to start and MongoDB rejected the connection. Troubleshooting: Check if the database service has an automatic restart policy configured, and if the database data directory is mounted to persistent storage.
- Symptom: When executing the upgrade initialization script interface, the returned HTML DOM does not display a success prompt. Troubleshooting: Check if the
FE_DOMAINenvironment variable matches the frontend deployment domain. - Symptom: The report validity judgment function is unresponsive, and logs show AI call failure. Troubleshooting: Check if
AIPROXY_API_TOKENis an AI Proxy admin token that matches the AI Proxy server configuration and is not empty. Do not use model vendor keys, application API keys, or other non-AI Proxy admin token credentials. Check ifAIPROXY_API_ENDPOINTis the AI Proxy service root address, not a single model address.
How to confirm configurations are correct
- Run
docker logs fastgpt-appto view startup logs, confirm there are no error messages about failed database connections or missing environment variables. - Submit a test report ticket, check if the system can normally generate processing records and push notifications, confirm storage and domain configurations are effective.
- Call the AI Proxy health check interface, confirm the AI Proxy service is running normally, and the configured
AIPROXY_API_TOKENmatches the AI Proxy server configuration and is not empty. - Check the database connection pool status, confirm the current number of connections does not exceed the
DB_MAX_LINKconfiguration value, and there are no connection exhaustion issues.
The values provided are common starting points, and should be evaluated against local samples and use cases.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.