Troubleshooting

Solutions for common DNS connection issues.

Connection Status: Invalid

Your connection shows Invalid status after validation.

Cause 1: Invalid Credentials

The API token, key, or credentials are incorrect or expired.

Solution:

1. Verify credentials in your provider's dashboard
2. Check if credentials have expired
3. Generate new credentials if needed
4. Update credentials in Orkestia connection settings
5. Validate the connection again

Cause 2: Insufficient Permissions

The credentials don't have required permissions.

Solution by Provider:

Cause 3: Provider API Issues

The DNS provider's API is experiencing issues.

Solution:

1. Check provider status pages:
   • Cloudflare Status
   • AWS Service Health
   • Google Cloud Status
   • Vercel Status
2. Wait for provider to resolve issues
3. Try validating again later

Cloudflare-Specific Issues

API Token Not Working

Symptoms: Validation fails with authentication error

Solutions:

1. Verify Token Permissions - Token must have Zone:Read and DNS:Edit (the Edit zone DNS template)
2. Check Token Scope - Ensure token includes all zones or specific zones you need
3. Regenerate Token - Create a new API token in Cloudflare and update the connection credentials

No Zones Found

Symptoms: Connection validates but shows 0 zones

Solutions:

1. Verify Zones Exist - Check Cloudflare dashboard for zones
2. Check Token Permissions - Token must have access to zones
3. Refresh Zones - Click "Refresh Zones" in connection details

Route 53-Specific Issues

No AWS Connection Available

Symptoms: Can't select AWS connection in Route 53 setup

Solutions:

1. Create AWS Connection First - Go to Connections > AWS
2. Check AWS Connection Status - AWS connection must be Active
3. Verify Route 53 Permissions - AWS connection must have Route 53 permissions

Zone IDs Not Working

Symptoms: "Invalid zone ID" error

Solutions:

1. Verify Zone ID Format - Zone IDs must start with 'Z' (format: Z1234567890ABC)
2. Verify Zone Exists - Check Route 53 console
3. Check AWS Connection Access - AWS connection must have access to the zones

Zones Not Syncing

Symptoms: Connection validates but zones don't appear

Solutions:

1. Check Zone Mode - If using "Specific Zones", verify zone IDs are correct
2. Verify Route 53 Permissions - AWS connection needs route53:ListHostedZones
3. Check AWS Region - Try different region (default: us-east-1)
4. Refresh Zones - Click "Refresh Zones" in connection details

Google Cloud DNS-Specific Issues

Service Account Key Invalid

Symptoms: Validation fails with authentication error

Solutions:

1. Verify JSON Format - Ensure key is valid JSON with entire content copied
2. Check Service Account Permissions - Must have roles/dns.admin
3. Verify Project ID - Project ID must match the service account's project
4. Regenerate Key - Create new service account key

Project ID Not Found

Symptoms: "Project not found" error

Solutions:

1. Verify Project ID - Use project ID (not project name), format: my-project-123456
2. Check Project Status - Ensure project is active
3. Verify Service Account - Service account must be in the same project

Vercel DNS-Specific Issues

API Token Invalid

Symptoms: Validation fails with authentication error

Solutions:

1. Verify Token - Check token in Vercel dashboard
2. Check Token Permissions - Token must have DNS management permissions
3. Regenerate Token - Create new API token in Vercel

Zone Synchronization Issues

Zones Not Appearing

Symptoms: Connection validates but no zones shown

Solutions:

1. Wait for Sync - Zones sync after connection creation
2. Manual Refresh - Click "Refresh Zones" in connection details
3. Verify Zones Exist - Check provider console for zones
4. Check Connection Status - Connection must be Active

Zones Out of Sync

Symptoms: Zones list doesn't match provider

Solutions:

1. Refresh Zones - Click "Refresh Zones"
2. Validate Connection - Zones refresh automatically after validation
3. Check Provider - Verify zones exist in provider console

Credential Update Issues

Validation Fails After Update

Symptoms: Credentials updated but validation fails

Solutions:

1. Verify New Credentials - Double-check credentials are correct
2. Check Provider - Verify provider API is accessible
3. Try Different Credentials - Generate new credentials

Quick Reference

Getting More Help

If you've tried the solutions above and still have issues:

1. Check Provider Status - Verify provider APIs are operational
2. Review Error Messages - Check connection details for specific errors
3. Validate Connection - Try validating the connection again
4. Contact Support - Reach out to Orkestia support with:
   • Connection UUID
   • Provider name
   • Error messages
   • Steps you've already tried

Provider Status Pages

• Cloudflare: https://www.cloudflarestatus.com/
• AWS: https://status.aws.amazon.com/
• Google Cloud: https://status.cloud.google.com/
• Vercel: https://www.vercel-status.com/