dFlow
Troubleshooting

Compute and worker node issues

Resolve SSH key problems, unreachable Worker Nodes, Dokku preparation, disk or capacity limits, and managed compute eligibility.

An Environment runs Services on compute: your Worker Nodes (self-hosted servers) or provider-backed managed compute where your plan supports it. If compute is unhealthy, many Deployments fail at once.

SSH or key errors when adding a server

  1. Confirm the public key in dFlow matches the user dFlow should use on the server (SSH keys under Security and Team Management in the sidebar).
  2. Verify host, port, and firewall rules allow SSH from dFlow’s perspective (Security groups under Security and Team Management in the sidebar for cloud nodes).
  3. Re-run the add-server flow after fixing keys; stale fingerprints or host keys may need operator attention on the machine.

Task guide: Add a self-hosted server under Worker Nodes and Compute in the sidebar.

Node shows offline, unreachable, or not eligible

  1. Read the dashboard message on the Worker Node or Environment compute tab; it usually states SSH, agent, or version checks.
  2. Confirm the server is powered on, has disk space, and reachable network paths (no IP change without updating dFlow).
  3. For cloud-backed nodes, check provider status and security groups.

Dokku or prerequisite failures

Self-hosted Worker Nodes rely on a prepared host. Follow the wizard requirements in Add a self-hosted server under Worker Nodes and Compute in the sidebar. If Dokku plugins or base packages fail, inspect server logs (Logs and debugging).

“No compute” or cannot attach to Environment

  1. Complete Attach compute to an environment under Environments in the sidebar (or the Create New Application compute step).
  2. On dFlow Cloud, confirm you selected a supported compute path (Worker Nodes overview under Worker Nodes and Compute in the sidebar).

Disk full or deploy fails with resource errors

  1. Free space on the Worker Node hosting the Service.
  2. Review scaling and replica settings (Scaling under Deployments and Operations in the sidebar) if RAM or CPU limits are tight.

Managed compute specific problems

If only managed compute Environments fail while self-hosted nodes work, compare plan limits (Feature access and limits under Billing and Account in the sidebar) and billing state (Billing issues).

Environment variable issues

Fix variables that do not apply after save, wrong references, secrets handling, and confusion between Services and databases.

Integration issues

Fix Git provider auth, Docker registry pulls, backup storage uploads, and cloud account linking failures that block builds and deploys.

On this page

SSH or key errors when adding a serverNode shows offline, unreachable, or not eligibleDokku or prerequisite failures“No compute” or cannot attach to EnvironmentDisk full or deploy fails with resource errorsManaged compute specific problemsRelated