Security troubleshooting

Fix SSH, security group, permission, and team invite problems in dFlow.

Written By Zoro

Last updated 3 days ago

SSH or Worker Node connection failures

Symptoms: Add server fails, health checks fail, or logs mention SSH authentication.

  1. Confirm the SSH key in Security → SSH Keys is the one attached to the Worker Node and that the public half is in the server’s authorized_keys (for manual setups).
  2. Verify security groups (or host firewall) allow SSH from dFlow’s expected source (often your IP or a narrow CIDR, not accidentally closed).
  3. See Compute and Worker Node issues under Troubleshooting in the sidebar for the full checklist (Dokku prep, disk, DNS).

Security group or AWS errors

Symptoms: Cannot save a group, EC2 flow fails, or AWS API errors in the UI.

  1. Confirm the cloud provider account is still valid and keys are not expired or disabled.
  2. Check IAM allows the operations dFlow needs for your flow (see AWS integration under Integrations in the sidebar).
  3. Ensure inbound rules include the ports your services need (HTTP / HTTPS / SSH as appropriate).

“Access denied” or missing pages

Symptoms: Empty states, redirects, or errors when opening Security, Team, Applications, or server actions.

  1. Ask an Admin which role you have; compare with Roles and permissions.
  2. You may have Read but not Update (for example on servers or services), which blocks specific buttons while still showing lists.
  3. For legacy Projects vs Applications, some permissions still reference projects; you may need applications access for new flows. See Legacy Projects vs Applications under Core Concepts in the sidebar.

Invites and team members

Symptoms: Invite email not received, copy-link disabled, or “limit reached”.

  1. Check spam and verify the email address; use Copy invitation link as a fallback (Workspace → Team).
  2. If the UI mentions plan or seat limits, an Admin or tenant owner may need to upgrade or free a seat on dFlow Cloud.
  3. Confirm your account has team.update if you expect to invite; viewers without that permission cannot generate links.

Still stuck

Collect the Organisation slug, rough time of the failure, and any error text from the UI, then use When to contact support under Troubleshooting in the sidebar.

Related