You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Make sure your provider has community provider attributes and your contact details (email, website):
Done
[Ref documentation:](https://akash.network/docs/providers/audited-attributes/#attribute-auditors).
### 2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
host .ingress.
Example:
``
root@akash-1:/home/user# host aaa.ingress.akash.akashserverdaniel.nl
aaa.ingress.akash.colnetwork.com is an alias for akash.akashserverdaniel.nl.
akash.akashserverdaniel.nl has address 87.209.236.248
Provider name: provider.akashserverdaniel.nl
Provider address: akash1yv80gw479dyqkpcu65lscnav73wugsrucenu82
Provider URI: provider.akashserverdaniel.nl
Provider URI name resolution works? yes
Ingress URI name resolution works? yes
Provider status endpoint works? yes
Provider grpc status endpoint works? yes
Provider responding to orders? no
Deployment works?
SSH works?
Network functional?
Attributes OK? no
Other remarks:
The provider only has 4 VCPU available total. Highly suggested to increase the number of VCPU to at least 32.
This is probably the reason the provider is not responding to orders.
provider-services query provider get akash1yv80gw479dyqkpcu65lscnav73wugsrucenu82
attributes:
Prerequisite Steps:
1. Make sure your provider has community provider attributes and your contact details (email, website):
Done
host .ingress.
3. Please make sure your Akash provider doesn't block any Akash specific ports.
Confirmed, firewall is disabled
Leave contact information (optional)
Name: Daniel Spel
Discord: daniel_380805
Contact email address: [email protected]
The text was updated successfully, but these errors were encountered: