01
Port 8443 or TLS failure
The provider endpoint may be unreachable, use an invalid certificate, resolve to the wrong address, or return an unexpected response. Read the dedicated port 8443 and TLS troubleshooting guide.
Akash provider troubleshooting
Your Akash provider is online - but not winning leases.
A provider can appear healthy while still declining every usable order. Connectivity, certificates, attributes, audits, inventory, storage, hardware requirements, capacity and pricing can all prevent a bid from becoming a lease.
Run the free provider checkCommon failure points
Why an Akash provider may not win leases
Winning leases requires more than keeping the provider process running. The workload must match what your provider advertises, and tenants must be able to reach the required public services.
02
Port 8444 connectivity
A firewall, upstream network rule, router, host listener, or forwarding problem can prevent required provider traffic from reaching the machine. Read the dedicated port 8444 connectivity troubleshooting guide.
03
Incompatible attributes
Orders may require a region, organization, storage class, CPU feature, GPU vendor, or hardware model that the provider does not advertise. Read the dedicated incompatible attributes troubleshooting guide. Read the dedicated GPU requirement troubleshooting guide.
04
signed_by or audit requirement
Some deployments accept only providers signed or audited by specified authorities. An otherwise healthy provider can still be rejected. Read the dedicated signed_by and provider audit troubleshooting guide.
05
Storage or inventory mismatch
Available resources may not match requested persistent storage, ephemeral storage, RAM, CPU, or specialized hardware. Read the dedicated storage class and inventory troubleshooting guide.
06
Pricing or available capacity
The bid may be uncompetitive, or current workloads and reserved resources may leave too little capacity to fulfill new orders. Read the dedicated provider pricing troubleshooting guide. Read the dedicated insufficient-capacity troubleshooting guide.
Free diagnosis
What the Campione readiness check reviews
The free checker gives you a fast first-pass review before you spend hours changing Kubernetes, provider, DNS or firewall settings.
+Provider DNS
Confirms that the supplied provider hostname resolves.
Confirms that the supplied provider hostname resolves.
+HTTPS and port 8443
Checks the public provider endpoint and reports connection or certificate failures.
Checks the public provider endpoint and reports connection or certificate failures.
+TCP port 8444
Tests whether the required public port accepts a connection.
Tests whether the required public port accepts a connection.
+Wildcard ingress
Reviews the hostname pattern commonly used for deployed services.
Reviews the hostname pattern commonly used for deployed services.
+Provider issue summary
Lets you submit failed checks, bid symptoms and provider details for a Campione Infrastructure review.
Lets you submit failed checks, bid symptoms and provider details for a Campione Infrastructure review.
Start with evidence
Find the blocker before changing your provider
Run the free check, review the results and submit the failed items when you need help diagnosing lease declines or provider readiness.
Run the free Akash provider check