Self-hosting troubleshooting

During the install

• "This install command has expired, was already used, or was replaced": create a new command in Settings → Self-hosting and run that one.
• "There is no terminal to ask the three questions in": run it from an SSH session, or pass --host, --tls and --storage.
• It stops at the name check: the DNS record must point at this server's address. Changes can take up to an hour.
• Ports 80 or 443 are busy: another web server is running. Stop it, or use a clean server.
• Pulling the images failed three times: check outbound HTTPS from the server, then run the same command again.
• The certificate fails: ports 80 and 443 must be reachable from the internet, or choose your own certificate or the internal-network option.

Signing in

• "Sign-in could not be completed": the server could not reach FlowX. Check outbound HTTPS to license.flowx.ninja and that time sync (NTP) is on, then try again.
• "This workspace doesn't exist" on your server's own address, or a jump to an address like your-workspace.yourcompany.com after sign-in: the server runs a version older than 0.1.22. Run sudo flowx upgrade.
• Someone can't sign in at all: check they are still a member of the workspace in your FlowX account, and that their account is active.

Running and updating

• The Self-hosting page says the server has not been heard from recently: check the server is on and can reach license.flowx.ninja, then run sudo flowx doctor.
• An upgrade failed: it has already rolled back to the previous version. Read sudo flowx logs api --tail 200, fix the cause, and run the upgrade again.
• Signature or time errors: switch on time sync (NTP) on the server.
• Emails don't arrive: finish Email sending (SMTP) in Settings → Server and use its Test button.

Getting help

Use the Support button in FlowX to open a ticket. Run sudo flowx support-bundle on the server and attach the file: it holds redacted logs and checks, never your workspace content, and it shows you what it collected before writing anything.