01
Deployment specifies signed_by
The workload may accept bids only from providers signed by one or more listed Akash addresses.
Akash provider troubleshooting
Your Akash provider does not satisfy the deployment's signed_by requirement.
An Akash deployment can restrict bidding to providers signed or audited by specific addresses. A healthy provider remains ineligible until it satisfies that requirement.
Run the free provider checkProvider audit eligibility
Why an Akash signed_by requirement blocks bids
The provider must have a valid audit or signature from one of the addresses accepted by the deployment. Connectivity and lower pricing do not bypass signed_by restrictions.
02
Provider lacks the required audit
Your provider may be operational but have no valid audit record from an accepted auditor.
03
Wrong auditor or signer
An existing provider audit does not help when the deployment accepts a different signing authority.
04
Expired or outdated audit data
The provider's current attributes or ownership information may no longer match the audit record being evaluated.
05
Owner-address mismatch
The audited provider owner address must match the provider attempting to bid on the deployment.
06
Pricing cannot bypass signed_by
Lowering your bid price cannot make an unsigned or unapproved provider eligible for a restricted deployment.
Free diagnosis
What to check when signed_by blocks a provider
Compare the deployment's accepted signer addresses with the provider's current audit records, ownership address and published attributes.
+Read the deployment signed_by list
Identify every accepted signer or auditor address in the workload requirements.
Identify every accepted signer or auditor address in the workload requirements.
+Confirm the provider owner address
Verify the exact Akash address registered as the provider owner.
Verify the exact Akash address registered as the provider owner.
+Review provider audit records
Check which auditor signed the provider and which attributes were approved.
Check which auditor signed the provider and which attributes were approved.
+Compare accepted and actual signers
The provider must be signed by at least one authority accepted by the deployment.
The provider must be signed by at least one authority accepted by the deployment.
+Verify audited attributes remain accurate
Region, organization, hardware and ownership details should match the current provider configuration.
Region, organization, hardware and ownership details should match the current provider configuration.
+Submit the decline evidence
Use the free checker and include the signed_by requirement and provider decline message.
Use the free checker and include the signed_by requirement and provider decline message.
Start with evidence
Find the exact signing requirement first
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