Issues with Provider Configuration

[Krakty]

So i'm having a problem Everything seems to work but the provider-console is reporting a DNS Configuration issue and frankly i'm at a loss i've been fiddling with this for weeks now. here's my diagnostics that i've been doing. anyone see anything that could lead me down the right path.

for clarity i'm reffering to the dns check on the console it states that provider.desktopdoktors.com is not configured and *.ingress.provider.desktopdoktors.com is not configured but they certainly are

anyway i'd love a pointer

Akash Provider Testing Summary

Provider Information

• Provider Address: akash1g5p09px5vsn6g65aqjmqpc3yqn4k2wzahq0jyl
• Provider Domain: provider.desktopdoktors.com
• Provider URI: https://provider.desktopdoktors.com:8443
• Organization: Desktop Doktors
• Location: Wisconsin, USA
• Network: 1Gbps symmetric fiber (TDS.NET)

Infrastructure Details

• Hardware: 4-node Proxmox cluster
• CPU: Intel Xeon Gold 6240 @ 2.60GHz (18 cores per node, 72 total cores)
• Memory: 2TB RAM total (512GB per node)
• Storage: 800GB SSD per node (3.2TB total)
• Kubernetes: 4-node cluster with Kubespray/Calico networking
• Available Capacity: 64,775 CPU units, 2.15TB RAM, 2.9TB storage

Test Results Summary

✅ External Connectivity Tests (PASSED)

All external endpoints are accessible and responding correctly:

Test	Status	Details
DNS Resolution	✅ PASS	provider.desktopdoktors.com → ragemachine.ddns.net → 134.215.6.38
Wildcard DNS	✅ PASS	*.ingress.desktopdoktors.com properly resolves
Port 80 (HTTP)	✅ PASS	Returns provider hostname
Port 443 (HTTPS)	✅ PASS	Returns provider hostname
Port 8443 (API)	✅ PASS	Returns provider address
Port 8444 (gRPC)	✅ PASS	gRPC endpoint responding
Port 26657 (RPC)	✅ PASS	Blockchain RPC accessible
Port 26656 (P2P)	❌ FILTERED	Expected - typically filtered by firewalls

✅ Internal Cluster Health (PASSED)

Kubernetes cluster is healthy and all services are running:

Component	Status	Details
Provider Registration	✅ REGISTERED	On-chain registration confirmed
Provider Pod	✅ RUNNING	akash-provider-0 healthy
Provider Service	✅ ACTIVE	ClusterIP service on ports 8443/8444
Provider Ingress	✅ CONFIGURED	Ingress rule for provider.desktopdoktors.com
Blockchain Node	✅ SYNCED	akash-node-1-0 synchronized
All 4 Nodes	✅ READY	All cluster nodes healthy
Hardware Discovery	✅ ACTIVE	All nodes reporting capacity

✅ Provider Configuration (PASSED)

Provider environment is correctly configured:

Setting	Value	Status
Chain ID	akashnet-2	✅ Correct
Node Endpoint	http://akash-node-1:26657	✅ Accessible
Ingress Domain	ingress.desktopdoktors.com	✅ Configured
Bid Strategy	scale	✅ Active
Provider Version	0.6.11-rc1	✅ Current

Current Problem Analysis

🟡 Provider Bidding Behavior

The provider is actively processing orders but declining most bids due to attribute requirements:

Observed Log Patterns:

I[2025-08-19|22:15:03.413] group fetched                                module=bidengine-order
D[2025-08-19|22:15:03.413] attribute signature requirements not met     module=bidengine-order
D[2025-08-19|22:15:03.413] declined to bid                              module=bidengine-order
I[2025-08-19|22:15:03.413] shutting down                                module=bidengine-order

Root Cause:
Many deployments require specific provider attributes or signed attestations that the provider doesn't currently have. Common requirements include:

• Audited provider status
• Specific geographic locations
• Hardware certifications
• Network compliance attributes

Provider Attributes Currently Set:

• host: akash
• tier: community
• organization: Desktop Doktors
• hardware-cpu: XEON Gold 6240
• hardware-memory: 512 GB
• country: USA
• location-region: Wisconsin
• network-speed-up/down: 1Gbps

✅ All Systems Operational

• Network Connectivity: All required ports accessible externally
• Kubernetes Cluster: 4-node cluster healthy and reporting capacity
• Provider Services: All pods running and responding correctly
• Blockchain Sync: Node fully synchronized with Akash network
• Resource Reporting: Provider accurately reporting 64,775 CPU units available

[StormNodeAlpha001]

Your attributes are wrong... It has to list nvidia. If not you will fail bids. Did you erase the attributes that were provided initially?

[Krakty]

I gave up after a week of learning and playing it simply wasn't worth my time. also i learned that since i have compute only it wouldn't ever get any bids so /bye good luck

…

On Sat, Sep 6, 2025 at 6:25 PM StormNodeAlpha001 ***@***.***> wrote: Your attributes are wrong... It has to list nvidia. If not you will fail bids. Did you erase the attributes that were provided initially? — Reply to this email directly, view it on GitHub <#1002 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BF7RYNPZN3LCSBYHZQMPFBL3RNUNXAVCNFSM6AAAAACEJVCZSWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZSHEZDQOI> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>