Skip to content
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

Open
steve21chong opened this issue Jan 4, 2025 · 7 comments
Open

[Provider Audit] provider.v3.i-sysmation.com #768

steve21chong opened this issue Jan 4, 2025 · 7 comments
Assignees

Comments

@steve21chong
Copy link

Prerequisite Steps:

1. Make sure your provider has community provider attributes and your contact details (email, website):

  Example:
  $ provider-services query provider get akash1<REDACTED> -o text
  ...
  attributes:
  ...
  - key: host
  value: akash
  - key: tier
  value: community
  info:
    email: "<your email>"
    website: "<your website>"

Ref documentation:.

2. Make sure your provider *.ingress resolves to your provider IP (ideally worker node IP)

host <anything>.ingress.<yourdomain>

Example:

$ host anything.ingress.akash.pro
anything.ingress.akash.pro is an alias for nodes.akash.pro.
nodes.akash.pro has address 65.108.6.185

3. Please make sure your Akash provider doesn't block any Akash specific ports.

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)

  1. Name
  2. Discord handle or Telegram handle
  3. Contact email address
@andy108369
Copy link
Contributor

Hi @steve21chong 👋
It looks like your provider is either offline or its 8443 tcp port is blocked:

user@laptop:~$ nc -vz provider.v3.i-sysmation.com 8443
<no reply>

@steve21chong
Copy link
Author

Hi Andy.. Have corrected the problem. Kindly help to verify it again. Thanks!

@shimpa1
Copy link

shimpa1 commented Jan 10, 2025

@steve21chong
The provider is still unreachable

curl -sk https://provider.v3.i-sysmation.com:8443/status | jq
^C
nc -vz provider.v3.i-sysmation.com 8443
^C

@steve21chong
Copy link
Author

Im able to reach my host without issue

image

@steve21chong
Copy link
Author

Have tested via Windows Powershell

image

@shimpa1
Copy link

shimpa1 commented Jan 11, 2025

Still can't access:
curl -sk https://provider.v3.i-sysmation.com:8443/status | jq ^C
The grpc status endpoint is also not reachable.
grpcurl -insecure provider.v3.i-sysmation.com:8444 akash.provider.v1.ProviderRPC.GetStatus | head -n 60 Failed to dial target host "provider.v3.i-sysmation.com:8444": context deadline exceeded

@steve21chong
Copy link
Author

I have made some changes. Can you try it again?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants