Data for This Category: Overview
Data for this category comes from customer on-premises data center environments, equipment inventories, software packages, and network topologies. Updates occur per order or phase. Daily documentation includes deployment manuals, installation records, configuration inventories, and on-site check-in sheets. Data fields cover device IP addresses, software version numbers, configuration parameters, network connectivity status, and on-site operation timestamps. No unified standardized format exists. Real-time updates are required alongside on-site deployment progress.
Constraints Imposed on Database and Operations Workflows
Since data comes from non-standardized on-site customer environments, database and operations configurations cannot directly reuse general templates. Configurations must be adjusted individually for each customer’s network topology and device resources. The per-order or per-phase update frequency requires configurations to support rapid adjustments, enabling iteration alongside on-site deployment progress. Daily configuration inventories must align strictly with database parameters to ensure traceability of on-site operations. Errors in this workflow will directly cause system unavailability, so fault tolerance and recovery plans must be prepared in advance.
How to Configure Settings
This configuration applies to FastGPT v4.17.0. Specific parameters are listed below:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
MONGODB_URI | Format: mongodb://[username]:[password]@[IP]:27017/[database_name]?authSource=admin, fully match the access address and authentication information of the customer’s on-site MongoDB instance | Ensure database read/write connectivity across data center networks, comply with the access rules of the customer’s own database |
PG_URL | Format: postgresql://[username]:[password]@[IP]:5432/[database_name]?sslmode=disable, adapt to the security policy of the customer’s on-premises PostgreSQL instance | Meet the authentication and encryption requirements of the customer’s database, ensure data storage security |
DB_MAX_LINK | 100–200 connections | Match the concurrent connection limit of the on-site deployment server, avoid exceeding the network and database resource thresholds of the customer’s data center |
REDIS_URL | Format: redis://[password]@[IP]:6379/0–15, match the address, password, and database index of the customer’s on-site Redis service | Ensure normal operation of the cache service, support FastGPT session storage and plugin invocation functions |
Three Common Configuration Mistakes
- Symptom: A database connection error occurs when starting the project, but the MongoDB visualization tool can connect normally. Cause: The
MONGODB_URIdoes not have the correct authentication source parameter configured, or the FastGPT deployment node is not granted access permission by the customer’s data center firewall. - Symptom: FastGPT cannot start after a power outage, manifested as PostgreSQL failing to start and MongoDB rejecting connections. Cause: No persistent mounting and automatic restart strategy configured for the database. The power outage leaves lock files from improperly shut down database processes, blocking service startup.
- Symptom: Workflow verification fails when using the database connection plugin to connect to PostgreSQL. Cause: The
PG_URLparameter has an incorrect format, or the inbound and outbound network rules for the corresponding port are not opened in the customer’s data center.
How to Confirm Proper Configuration
- Run the database connectivity detection script included with FastGPT to verify the connectivity status of
MONGODB_URI,PG_URL, andREDIS_URL. - Cross-reference the on-site deployment configuration inventory and installation records to check whether each database parameter matches the content in the configuration files.
- Simulate a power outage and restart scenario to verify that the database service can automatically recover and start without remaining lock file issues.
- Run a test workflow to verify that the database connection plugin can normally read or write specified data.
The values provided here are common starting points and should be measured against the reader's own samples.
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.