Integration troubleshooting

Fix common Git, registry, and AWS integration failures: reconnect, scopes, keys, and where to read logs.

Written By Zoro

Last updated 9 days ago

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.

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: verify the repo appears in Repository access for the installed app.

  3. Token providers: generate a new token with read scopes and reconnect.

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.

Backup storage: test fails, unverified, or external backup errors

  1. Open Integrations → Backup Storage and confirm bucket, region, and endpoint.

  2. Click Test connection with current keys; rotate keys if the test fails.

Azure: connection or provisioning errors

  1. Open Integrations → Azure and confirm the account shows Connected. If not, click Connect account and sign in with Microsoft again.

  2. Verify the signed-in identity still has access to the subscription and resource group you select in the worker form.

  3. If lists load but VM creation fails, check Azure quotas, VM size availability in the region, and whether the image is offered there.

  4. For Advanced network security group mode, confirm your existing NSG allows inbound SSH (22), Tailscale (41641 UDP), monitoring (45876), HTTP (80), and HTTPS (443). Basic mode creates these rules for you.

  5. If the worker is created in Azure but never shows Connected in dFlow, wait a few minutes, then open Compute troubleshooting under Worker Nodes and Compute in the sidebar.

Guides: Azure integration and Add an Azure server under Worker Nodes and Compute in the sidebar.

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.

Mixed-up layers (Git vs SSH vs cloud)

Problem

Wrong fix

Right layer

API AccessDenied in AWS

Changing Docker registry or Backup Storage

IAM policy and Cloud provider accounts

Azure provision or list errors

Rotating Git token

Azure integration and Azure RBAC on the signed-in identity