-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Provider Audit] provider.v3.i-sysmation.com #768
Comments
Hi @steve21chong 👋
|
Hi Andy.. Have corrected the problem. Kindly help to verify it again. Thanks! |
@steve21chong curl -sk https://provider.v3.i-sysmation.com:8443/status | jq |
Still can't access: |
I have made some changes. Can you try it again? |
Prerequisite Steps:
1. Make sure your provider has community provider attributes and your contact details (email, website):
Ref documentation:.
2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)
Example:
3. Please make sure your Akash provider doesn't block any Akash specific ports.
https://akash.network/docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/#step-11---firewall-rule-review
Audit Steps:
1. Title the issue: " [Provider Audit]: Provider Address" (e.g. "[Provider Audit]: provider.europlots.com")
2. Wait for response via comments. If no issues during provider Audit, process will be complete, provider should start bidding on leases, and Audit ticket will be closed.
3. If there are issues during the provider Audit, debug those issues, and Audit will be complete.
4. Audit Issue will be closed by core team member.
Leave contact information (optional)
The text was updated successfully, but these errors were encountered: