Integration issues

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

Written By Zoro

Last updated 9 days ago

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

  1. Reconnect the integration from organisation or account settings and accept any new provider permissions.

  2. Confirm the token or GitHub App installation still has access to the organisation or repo.

  3. Check branch name and default branch settings on the Service match the repo.

Docker registry: pull denied or manifest unknown

  1. Re-enter or rotate registry credentials.

  2. Confirm image name, tag, and registry host match what the Docker Service expects.

Backup storage: external database backup fails

  1. Confirm the provider is verified under Integrations → Backup Storage.

  2. On the database Backups tab, confirm External storage and the correct provider are saved.

AWS or Azure cloud account errors

  1. 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.

  2. AWS: Review AWS integration and Cloud provider accounts for linking steps.

  3. Check IAM (AWS) or Azure RBAC against Integration permissions and prerequisites.

  4. If provisioning fails after a healthy connection, see Add an Azure server or Compute troubleshooting under Worker Nodes and Compute in the sidebar.