Support

We’re here to help you get the most out of Air Cloud

Ask our docs

Ask our AI assistant that’s been trained on our documentation.

Email Us for Support

If you have any questions, email us at

[e-mail].

Email Us for Development

If you have any questions, email us at

[e-mail].

Frequently Asked Questions

Below are common issues and how to resolve them based on real user deployments and our internal diagnostics:

401 Unauthorized

Authentication failed. Please verify that your API key or access credentials are correct.

404 Not Found

The requested container ID or endpoint path is invalid. Double-check the container ID or route.

500 Internal Server Error

An internal server error has occurred. Try again later or contact the Air Cloud support team.

Below are common issues and how to resolve them based on real user deployments and our internal diagnostics:

API Key Authentication Failure

• Symptom: Fails to authenticate API request
• Cause: Expired or incorrect API key
• Fix:
  • Ensure your key is still valid (check expiration)
  • Generate a new API key from the Air Cloud dashboard

GPU Assignment Errors

• Symptom: No GPU detected on container startup
• Cause: Node instability or driver mismatch
• Fix:
  • Re-deploy to a new instance
  • Check compatibility of driver with your container runtime

Network Connectivity Failures

• Symptom: Container cannot reach external endpoints
• Cause: Port configuration, DNS issues, or firewall blocks
• Fix:
  • Verify container exposes correct port and service is listening
  • Use curl inside container to test outbound connectivity
  • Ensure no security group restrictions block egress traffic

Health Check Failures / Stuck in Initializing

• Symptom: Deployment hangs on health check
• Cause: Container is not returning 200 OK on /health
• Fix:
  • Confirm that the correct health check path and port are exposed
  • Check logs for stack traces or model loading delays

Autoscaling Not Triggering

• Symptom: No scaling despite high load
• Cause: Scaling threshold too high, or unhealthy replicas
• Fix:
  • Tune autoscaling parameters (e.g., CPU threshold, latency window)
  • Verify all replicas pass health checks

502/503 Gateway Errors

• Symptom: API responds with server error
• Cause: App not bound to expected port or crashed during startup
• Fix:
  • Verify service listens on 0.0.0.0:<PORT>
  • Increase health check timeout if model loading takes long

We do our best to respond to all requests within 24 hours but delays may occur during busy times.