Connection Test Failing in UI

When setting up a new data source through the DataHub UI, the connection test fails even though credentials appear correct. This can be caused by network connectivity issues, firewall rules blocking DataHub from reaching the source, or incorrect connection parameters.

Common Error Messages:

• Connection test failed: Unable to reach host
• Timeout connecting to data source
• Network unreachable
• SSL handshake failed

You Might Be Asking:

• Why is my connection test failing in the DataHub UI?
• How do I debug connection issues?
• What network access does DataHub need?

1. (this step for OSS DataHub only) Verify network connectivity from DataHub pod:

# DataHub Open Source Only
# Get shell access to DataHub executor pod
kubectl exec -it deployment/datahub-gms -- /bin/bash

# Test connectivity
nc -zv your-database-host 5432
ping your-database-host

2. Check firewall rules and security groups:

   • Ensure DataHub's IP/CIDR is whitelisted in source system
   • Verify security group allows outbound traffic on required ports
   • Check if VPN or private link is required

3. For SSL/TLS issues, configure certificates:

source:
  config:
    # For databases requiring SSL
    ssl:
      enabled: true
      ca_cert: "/path/to/ca-cert.pem"
      # Or disable SSL verification (not recommended for production)
      verify_ssl: false

4. Test connection using CLI recipe first:

Example for Postgres. This can be adapted for other data sources/connectors.

# Create test-connection.yml
source:
  type: postgres
  config:
    host_port: "postgres.example.com:5432"
    database: "your_database"
    username: "${DB_USER}"
    password: "${DB_PASSWORD}"

# Run test
datahub ingest -c test-connection.yml --dry-run

5. Check DataHub executor logs for detailed errors:

kubectl logs -f deployment/datahub-actions | grep -A 10 "connection test"

For cloud-managed databases (RDS, Cloud SQL, etc.), ensure the database allows connections from external IPs or configure private networking. Some sources require IP whitelisting which must be done before connection tests will succeed.

• Networking Requirements
• Managed Ingestion