Troubleshooting
Integration issues
Fix Git provider auth, Docker registry pulls, backup storage uploads, and cloud account linking failures that block builds and deploys.
Integrations let Services read repositories and images, and (on dFlow Cloud) connect provider accounts for infrastructure. Symptoms usually appear as build or pull errors; always capture Logs and debugging output.
Git: cannot list repos, clone fails, or webhook never fires
- Reconnect the integration from organisation or account settings and accept any new provider permissions.
- Confirm the token or GitHub App installation still has access to the organisation or repo (GitHub integration under Integrations in the sidebar, Git source integrations under Integrations in the sidebar).
- Check branch name and default branch settings on the Service match the repo.
- Automatic deploy on push depends on provider setup; verify webhooks in the Git host if pushes do not start builds.
Task guide: Integrations overview under Integrations in the sidebar.
Docker registry: pull denied or manifest unknown
- Re-enter or rotate registry credentials (Docker registry integration under Integrations in the sidebar).
- Confirm image name, tag, and registry host match what the Docker Service expects (Docker services under Services in the sidebar).
- For rate limits, retry later or authenticate (provider dependent).
Backup storage: external database backup fails
- Confirm the provider is verified under Integrations → Backup Storage (test or verify again after key rotation).
- On the database Backups tab, confirm External storage and the correct provider are saved.
- See Backup storage integration under Integrations in the sidebar and Backups and restore under Databases in the sidebar.
AWS or Azure cloud account errors
- Azure: Open Azure integration under Integrations in the sidebar. Reconnect if the account is Disconnected. Confirm the Microsoft identity can access the subscription and resource group.
- AWS: Review AWS integration under Integrations in the sidebar and Cloud provider accounts for linking steps.
- Check IAM (AWS) or Azure RBAC against Integration permissions and prerequisites under Integrations in the sidebar.
- If provisioning fails after a healthy connection, see Add an Azure server under Worker Nodes and Compute in the sidebar or Compute troubleshooting under Worker Nodes and Compute in the sidebar.
Narrow vs platform integration docs
This page is the customer troubleshooting entry. Deeper walkthroughs live under Integrations overview under Integrations in the sidebar and Integration troubleshooting under Integrations in the sidebar as those guides are expanded.