Start with the symptom below, then open Logs and debugging under Troubleshooting in the sidebar and copy build or deploy output before you contact support. The Troubleshooting overview under Troubleshooting in the sidebar links every major area.

For a shorter symptom list that also points here, see Integration issues under Troubleshooting in the sidebar.

Git: cannot see repositories

1. Open Integrations and confirm the provider shows Connected.

2. GitHub: open the GitHub Settings for the installed app and verify the repo appears in Repository access. Add it if you use Only select repositories.

3. Token providers (GitLab, Bitbucket, Gitea, Azure DevOps): generate a new token with read scopes and reconnect. See Git source integrations.

4. Confirm you are in the right Organisation in dFlow. Integration visibility follows Tenant access model under Security and Team Management in the sidebar.

Git: clone or build fails with permission denied

1. Re-run connect or re-authorize the GitHub App if the org recently enabled SSO or third-party restrictions.

2. Confirm the branch exists and is spelled exactly as in the remote.

3. For private submodules or monorepos, ensure the same credentials can reach every URL the build touches (provider dependent).

If you suspect a dFlow role blocked an action another user performed, compare Roles and permissions under Security and Team Management in the sidebar.

Git: push does not trigger a new deploy

1. Check whether the Service uses manual deploy; push alone would not roll out.

2. GitHub App: confirm webhooks on the installation are healthy in GitHub Settings (delivery logs).

3. Confirm automatic deploy is supported for your provider and configuration (App services under Services in the sidebar).

Docker registry: pull denied or manifest unknown

1. Open Integrations and edit the registry: re-enter the token, save, Redeploy the Docker Service.

2. Compare image:tag to the registry UI; typo or wrong digest causes manifest unknown.

3. For rate limits, authenticate with a user or token that has pull rights, then retry.

Guide: Docker registry integration.

AWS: connection or provisioning errors

1. Verify Access key ID and Secret access key are current in IAM and in dFlow.

2. Open AWS integration and confirm the IAM policy includes the API actions the UI needs.

3. If EC2 starts but the server never registers, check Security groups, SSH, and Compute and worker node issues under Troubleshooting in the sidebar. Security groups under Security and Team Management in the sidebar explains network rules.

Mixed-up layers (Git vs SSH vs AWS)

Still stuck

1. Gather build log, deploy log, and a screenshot of the Integration status.

2. Read When to contact support under Troubleshooting in the sidebar.

3. Security-specific auth questions: Security troubleshooting under Security and Team Management in the sidebar.

Related

• Integration permissions and prerequisites

• Deployment issues