Common Issues & Solutions

CloudNexus DNS records typically propagate within 60 seconds, but local ISP caches or browser caching may cause delays. If your changes aren't reflecting:

• Clear your local DNS cache: ipconfig /flushdns (Windows) or sudo systemd-resolve --flush-caches (Linux)
• Verify propagation using dig @8.8.8.8 yourdomain.com
• Check TTL settings in the CloudNexus DNS dashboard. Lower TTL before making changes to speed up future updates.
• Ensure your local machine isn't using a restrictive DNS server that ignores standard propagation.

SSH timeouts usually stem from firewall rules, incorrect keys, or service status. Follow these steps to restore access:

• Verify your instance's security group allows inbound traffic on port 22
• Ensure you're using the correct private key and permissions: chmod 600 your-key.pem
• Check if SSHD is running: sudo systemctl status sshd
• If locked out, use the CloudNexus Console Access (VNC) to troubleshoot directly from the dashboard

Pod scheduling or runtime failures are common in K8s. Use the following diagnostic approach:

• Run kubectl describe pod <pod-name> to check Events for resource limits or image pull errors
• Verify node availability and cluster autoscaler status in the CloudNexus K8s dashboard
• Check container logs: kubectl logs <pod-name> --previous
• Ensure resource requests/limits match your cluster's node capacity

Managed databases enforce connection limits based on your plan tier. Sudden spikes can trigger this:

• Implement connection pooling (PgBouncer for PostgreSQL, ProxySQL for MySQL)
• Review application code for unclosed connections or missing timeouts
• Scale your database instance to a higher tier for increased connection limits
• Use CloudNexus's connection limit alerts to set proactive thresholds

CloudNexus CDN caches assets by default for performance. To force fresh content delivery:

• Use the "Purge Cache" button in the CDN dashboard for instant propagation
• Implement cache-busting via file versioning: style.v2.css
• Set shorter Cache-Control headers for dynamic content in your origin server
• For selective purging, use our API: POST /cdn/purge?files=path/to/file

Bandwidth is metered per region. Overage usually occurs from unoptimized asset delivery or DDoS traffic:

• Enable CDN caching to reduce origin bandwidth consumption
• Review traffic analytics in the Billing Dashboard to identify spikes
• Set up budget alerts and bandwidth caps in Account Settings
• If traffic appears malicious, enable DDoS Shield or contact security support immediately

Kernel updates or service conflicts can occasionally cause boot failures:

• Try a hard reboot from the CloudNexus console
• Boot into recovery mode or previous kernel version via GRUB
• Check system logs: journalctl -b -1 for the last boot cycle
• Ensure you have a snapshot/backup before running major OS updates in production

502 errors from CloudNexus load balancers typically indicate backend health check failures:

• Verify all target pods are in Running and Ready state
• Check that your service port matches the container port exactly
• Review health check endpoints to ensure they return HTTP 200/2xx
• Inspect LB logs in the dashboard for connection timeout patterns