Deployment and upgradesOfficial documentation5 min readDeployment and upgrades

Verify FastGPT Remote Debug Suite Setup

Gateway Health Verification First, validate the operational status of the connection gateway service using the official health check endpoint.

Gateway Health Verification

First, validate the operational status of the connection gateway service using the official health check endpoint. Execute the following curl command in a shell environment with network access to the gateway:

curl http://connection-gateway:3000/health

This command targets the default gateway port 3000 and returns a success response if the gateway service is running and reachable.

Debug Channel Status Validation

Within the FastGPT administrative interface, enable the remote debug channel. Track the debug channel status indicator; it will transition from the enabled state to connected state once the platform has established a pending connection to the remote plugin service. This status change confirms the FastGPT platform is configured to accept remote plugin connections.

Local Plugin Development Environment Validation

Launch the local FastGPT plugin development server using the provided dev command:

fastgpt-plugin dev

Monitor the CLI output generated by this command for a confirmation message indicating an active WebSocket connection. This confirms the local plugin service is listening for incoming connection requests from the FastGPT platform.

End-to-End Functional Validation

To confirm the full remote debug suite workflow is operational, navigate to the FastGPT interface and select a tool categorized under the debug source. Perform a single invocation of the selected tool. Verify that the response returned to the FastGPT platform originates from the locally running plugin instance, confirming that remote debugging is active.

Source: FastGPT official source

Applicability and version scope

Use this page for the documented Deployment and upgrades scenario. Confirm the FastGPT, dependency, API, and deployment versions in the official source before applying a change.

Safety guardrails

Use [REDACTED_CREDENTIAL] for credentials and private data. Confirm the documented environment and version before review.

Rollback guidance

Restore the prior technical-content authority snapshot. Restore saved configuration and data snapshots, then repeat the smallest verification scenario.