Troubleshooting¶
Checks for the Langflow 0.2.1 failures named in the listing and the published getting-started page.
The editor does not open¶
Cause: first boot is still running, or port 7860 is not forwarded.
Langflow listens on 127.0.0.1:7860.
Fix: wait several minutes, then:
Forward port 7860 and open http://127.0.0.1:7860 on the workstation. Leave
the forward running. See Sign in.
Sign-in fails¶
Cause: the password in the browser does not match
/etc/langflow/admin.json on this instance.
Fix: as ubuntu, read that file in the session and type those values.
Do not replace /etc/langflow to get a new login. That directory also holds
the encryption material. See Backups.
The no-argument demo does not print success¶
Cause: bash /opt/sushi/docs/demo.sh waits for Langflow, then saves and
runs a local Chat Input to Chat Output flow. It does not call a provider.
Success prints SUSHI_CUSTOMER_DEMO_PASSED.
Fix: wait until sushi-langflow status shows the application is up, then
run the script again with no arguments. Do not add a provider key to this
command.
The provider demo fails¶
Cause: the endpoint, model, or key file does not match an OpenAI-compatible account, or the key was passed on the command line. A provider failure does not produce a substitute answer. Each model execution can add a provider charge.
Fix: create ~/.langflow-provider-key as mode 0600 with only the key,
then pass --endpoint, --model, and --api-key-file. See
Use your own provider. If the
provider hostname is not on the public internet, add that exact hostname to
the allowlist. The default allowlist is empty.
Flows are missing after a restore¶
Cause: /var/lib/langflow was restored without /etc/langflow, or the
encryption material was replaced. A missing initialized database fails
visibly.
Fix: restore both directories from the same backup, including
langflow.db, admin.json, and initialized.json. Keep the original
encryption and administrator configuration.
Last updated November 1, 2026 · Suggest an improvement