Next.js troubleshooting
The connection fails
Check that:
- the Site address in Flowpane is the exact HTTPS address that serves the application;
/api/flowpaneis deployed, runs on Node.js and is reached directly, without a login, redirect or CDN cache;FLOWPANE_NEXT_IDENTITYis set in the server-only settings of the deployment that serves the Site; if your host refused the value as too long, use the server-only.env.productionfile described in Installation;- you used a fresh connection token; get a new one if it expired.
Opening /api/flowpane in a browser shows only a short unavailable message. That is expected: it answers only Flowpane's signed requests.
Connection health needs attention
After connecting, both FLOWPANE_NEXT_IDENTITY and FLOWPANE_NEXT_CONNECTION must be set in every instance that serves the Site; restart or redeploy after changing them. An unavailable status alone does not mean the Site was disconnected; check again after the next scheduled health check.
Source evidence looks out of date
Evidence is created when the application is built. Rebuild and redeploy after changing robots, sitemap, redirects, rewrites or headers. During a rolling deployment, different instances can briefly report different evidence; read the result after the deployment completes.
Disconnecting
Choose Disconnect on the Site's Integrations page in Flowpane, then Confirm disconnect; Cancel leaves the connection as it is. Once confirmed, the connection ends at once. Then remove both values from your host settings (or your server-only .env.production file) and redeploy. To replace the identity, disconnect first, create a new identity, deploy it and connect again. Do not overwrite the identity to repair a connection you are unsure about.
Keep both values private. Never send them to support or include them in screenshots.