Connection Problems

Troubleshooting database connection issues with Gold Digger's enhanced error handling.

Gold Digger Connection Error Codes

Gold Digger provides structured exit codes for different connection failures:

• Exit Code 2: Configuration errors (invalid URL format, missing parameters)
• Exit Code 3: Connection/authentication failures (network, credentials, TLS)

Common Connection Errors

Connection Refused (Exit Code 3)

Error Message:

Database connection failed: Connection refused. Check server availability and network connectivity

Causes & Solutions:

• Database server not running: Start MySQL/MariaDB service
• Wrong port: Verify port number (default: 3306)
• Firewall blocking: Check firewall rules on both client and server
• Network issues: Test basic network connectivity

Diagnostic Steps:

# Test network connectivity
telnet hostname 3306

# Check if service is running
systemctl status mysql  # Linux
brew services list | grep mysql  # macOS

Access Denied (Exit Code 3)

Error Message:

Database authentication failed: Access denied for user 'username'@'host'. Check username and password

Causes & Solutions:

• Invalid credentials: Verify username and password
• Insufficient permissions: Grant appropriate database permissions
• Host restrictions: Check MySQL user host permissions
• Account locked/expired: Verify account status

Diagnostic Steps:

# Test credentials manually
mysql -h hostname -P port -u username -p database

# Check user permissions
SHOW GRANTS FOR 'username'@'host';

Unknown Database (Exit Code 3)

Error Message:

Database connection failed: Unknown database 'dbname'

Causes & Solutions:

• Database doesn't exist: Create database or verify name
• Typo in database name: Check spelling and case sensitivity
• No access to database: Grant permissions to the database

Diagnostic Steps:

# List available databases
SHOW DATABASES;

# Create database if needed
CREATE DATABASE dbname;

Invalid URL Format (Exit Code 2)

Error Message:

Invalid database URL format: Invalid URL scheme. URL: ***REDACTED***

Causes & Solutions:

• Wrong URL scheme: Use mysql:// not http:// or others
• Missing components: Ensure format is mysql://user:pass@host:port/db
• Special characters: URL-encode special characters in passwords

Correct Format:

mysql://username:password@hostname:port/database

TLS Connection Issues (rustls-only implementation)

Gold Digger uses rustls for all TLS connections with enhanced security controls and better error messages.

TLS Handshake and Connection Issues (Exit Code 3)

Common Error Messages:

TLS handshake failed: protocol version mismatch
Certificate validation failed: unable to get local issuer certificate
Certificate validation failed: self signed certificate in certificate chain
Hostname verification failed for 192.168.1.100: certificate is for db.company.com

Causes & Solutions:

• Certificate validation failures:
  • Self-signed certificates: Use --allow-invalid-certificate (testing only) or --tls-ca-file /path/to/ca.pem
  • Expired certificates: Use --allow-invalid-certificate (testing only)
  • Internal CA certificates: Use --tls-ca-file /path/to/internal-ca.pem
  • Missing CA certificates: Install system CA certificates or use custom CA file
• Hostname verification failures:
  • IP address connections: Use --insecure-skip-hostname-verify for development
  • Certificate hostname mismatch: Use --insecure-skip-hostname-verify or fix certificate
• TLS version/cipher issues: Ensure server supports TLS 1.2+ with compatible cipher suites

Gold Digger TLS CLI Flags:

# Use custom CA certificate (recommended for internal infrastructure)
gold_digger --tls-ca-file /etc/ssl/certs/internal-ca.pem --db-url "mysql://..." --query "..." --output results.json

# Skip hostname verification (development environments)
gold_digger --insecure-skip-hostname-verify --db-url "mysql://user:pass@192.168.1.100:3306/db" --query "..." --output results.json

# Accept invalid certificates (testing only - DANGEROUS)
gold_digger --allow-invalid-certificate --db-url "mysql://..." --query "..." --output results.json

Diagnostic Steps:

# Check server TLS configuration
SHOW VARIABLES LIKE 'tls_version';
SHOW VARIABLES LIKE 'ssl_cipher';

# Verify certificate chain
openssl s_client -connect hostname:3306 -servername hostname

# Test with Gold Digger verbose mode
gold_digger -v --db-url "mysql://..." --query "SELECT 1" --output test.json

Network Troubleshooting

Firewall Issues

Symptoms:

• Connection timeouts
• "Connection refused" errors
• Intermittent connectivity

Solutions:

# Check if port is open (Linux/macOS)
nmap -p 3306 hostname

# Test connectivity
telnet hostname 3306

# Check local firewall (Linux)
sudo ufw status
sudo iptables -L

# Check local firewall (macOS)
sudo pfctl -sr

DNS Resolution Issues

Symptoms:

• "Host not found" errors
• Connection works with IP but not hostname

Solutions:

# Test DNS resolution
nslookup hostname
dig hostname

# Try IP address directly
gold_digger --db-url "mysql://user:pass@192.168.1.100:3306/db" --query "SELECT 1" --output test.json

Debugging Connection Issues

Enable Verbose Logging

gold_digger -v \
  --db-url "mysql://user:pass@host:3306/db" \
  --query "SELECT 1" \
  --output debug.json

Verbose Output Example:

Connecting to database...
Database connection failed: Connection refused

Configuration Debugging

# Check resolved configuration (credentials redacted)
gold_digger \
  --db-url "mysql://user:pass@host:3306/db" \
  --query "SELECT 1" \
  --output test.json \
  --dump-config

Test with Minimal Query

# Use simple test query
gold_digger \
  --db-url "mysql://user:pass@host:3306/db" \
  --query "SELECT 1 as test" \
  --output connection_test.json

Advanced Diagnostics

MySQL Error Code Mapping

Gold Digger maps specific MySQL error codes to contextual messages:

Connection Pool Issues

Symptoms:

• Intermittent connection failures
• "Too many connections" errors

Solutions:

• Check MySQL max_connections setting
• Monitor active connection count
• Verify connection pool configuration

Performance-Related Connection Issues

Symptoms:

• Slow connection establishment
• Timeouts on large queries

Solutions:

# Test with smaller query first
gold_digger \
  --db-url "mysql://user:pass@host:3306/db" \
  --query "SELECT COUNT(*) FROM table LIMIT 1" \
  --output count_test.json

# Check server performance
SHOW PROCESSLIST;
SHOW STATUS LIKE 'Threads_connected';

Getting Help

When reporting connection issues, include:

1. Complete error message (credentials will be automatically redacted)
2. Gold Digger version: gold_digger --version
3. Database server version: SELECT VERSION();
4. Connection string format (without credentials)
5. Network environment (local, remote, cloud, etc.)
6. TLS requirements and certificate setup

Example Issue Report:

Gold Digger Version: 0.2.6
Database: MySQL 8.0.35
Error: Certificate validation failed: self signed certificate
Connection: mysql://user:***@remote-db.example.com:3306/production
Environment: Connecting from local machine to cloud database
TLS: Required, using self-signed certificates