Closed spyder403 closed 8 months ago
Jrgbuilding.online
provider based on the blockchain data;Found only these two:
"https://provider.jrgbuilding.net:8443","akash190h2dkfeue3us46kt6yak5a0v48mxkvs9azw30"
"https://provider.jrgbuilding.org:8443","akash1js2a3tt8r7tuwavnpv04wdurthyx4vjwdppeld"
:warning: provider.jrgbuilding.net
- isn't responding over 8443/tcp
provider.jrgbuilding.org
- is responding over 8443/tcp
:warning: provider.jrgbuilding.org
provider is missing the host: akash
attribute which is a necessary attribute for the community provider as per https://docs.akash.network/providers/akash-audited-attributes#attribute-auditors
$ provider-services query provider get akash1js2a3tt8r7tuwavnpv04wdurthyx4vjwdppeld -o text
attributes:
- key: organization
value: Spyder
- key: capabilities/gpu/vendor/nvidia/model/4090
value: "true"
- key: arch
value: amd64
host_uri: https://provider.jrgbuilding.org:8443
info:
email: ""
website: ""
owner: akash1js2a3tt8r7tuwavnpv04wdurthyx4vjwdppeld
provider.jrgbuilding.org
provider$ provider_info.sh provider.jrgbuilding.org
type cpu gpu ram ephemeral persistent
used 6.2 13 8.15625 34.01171875 0
pending 0 0 0 0 0
available 25.3 0 243.02471542358398 855.9364657104015 0
node 25.3 0 243.02471542358398 855.9364657104015 N/A
Ingress address name resolution is not working. Missing a wildcard DNS record for the *.ingress.<provider>
address:
$ ping uugvvsaic9e2v8bd8qm3ci5vc4.ingress.jrgbuilding.org
ping: uugvvsaic9e2v8bd8qm3ci5vc4.ingress.jrgbuilding.org: Name or service not known
*Otherwise the ingress forwarding is working:
$ curl --connect-to uugvvsaic9e2v8bd8qm3ci5vc4.ingress.jrgbuilding.org:80:ingress.jrgbuilding.org:80 uugvvsaic9e2v8bd8qm3ci5vc4.ingress.jrgbuilding.org
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
...
I'm sorry hiw do I add wildcard dns
I'm sorry hiw do I add wildcard dns
That's just *
record (either of A
, or CNAME
kind) that you need to add.
It looks like you are using namecheap.com
You need to point the wildcard record *.ingress
to the IP via DNS A
record, or to the hostname via DNS CNAME
record of your worker node address (IP or host)
Additionally - here is an example from the official Akash doc => https://docs.akash.network/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/step-5-domain-name-review
@spyder403 any updates / help needed?
both providers are down, owner hasn't responded. Closing.
Requesting audit for my nodes Jrgbuilding.org Jrgbuilding.online