document/content/self-host/upgrading/4-15/4151.en.mdx
Starting from v4.15.1, the FastGPT main app no longer uses rootkey when calling Pro/Admin internal APIs. These internal service-to-service calls now use a dedicated PRO_TOKEN. FE_DOMAIN is also required. If you deploy the Pro edition, configure the same PRO_TOKEN in both the FastGPT main app and the Pro/Admin service:
PRO_TOKEN=your_pro_token_at_least_32_chars
FE_DOMAIN=fastgpt_domain
Notes:
PRO_TOKEN must be at least 32 characters long, and the value must be identical in the FastGPT main app and Pro/Admin.PRO_URL, PRO_TOKEN is also required. Otherwise, the service fails to start.PRO_TOKEN; otherwise, internal API authentication fails.rootkey is no longer used as the credential for FastGPT main app calls to Pro/Admin internal APIs. It is only the admin secret for the current system and is used to call /api/admin/** APIs, such as the initialization script below.PRO_TOKEN. For Pro deployments, add it manually in your private deployment environment variables.To keep older API keys compatible and make it easier to find keys previously associated with apps, v4.15.1 adds global API Key tag management and an appName display snapshot for historical app-level API Keys. After upgrading, run the initialization script once to backfill app names for existing API Keys whose appId field is still present.
From any terminal, send an HTTP request. Replace {{rootkey}} with the rootkey from your environment variables, and {{host}} with your FastGPT domain.
curl -X POST "{{host}}/api/admin/initv4151" \
-H "rootkey: {{rootkey}}"
The script only fills missing appName values. It does not overwrite existing values, does not change the appId field, and does not create or bind tags. It is safe to run multiple times.
appName display snapshot for historical app-level API Keys, making older API keys compatible and easier to find when they were previously associated with apps.