Labels: support

Describe the bug
Provider crashes immediately after startup with nil pointer dereference at certs.go:365 when processing certificates for closed leases.

• Provider address: akash1nj6ygd4ggz589ldtt4e7yklazxm9zpp8cf7yh7
• Provider URI: https://provider.cerebro.host:8443
• Version: provider-services v0.10.5
• Closed lease owner: akash19knltmlgaq73grmddc3cz0fen097lel57nh0e9
• Closed lease DSEQ: 24897148 (and others)

To Reproduce

1. Provider starts successfully (init container completes)
2. Provider fetches attributes from chain
3. Provider starts gRPC listener on port 8444
4. Provider crashes at certs.go:365 when processing closed lease certificates
5. Pod enters CrashLoopBackOff state

Error Log

panic: runtime error: invalid memory address or nil pointer dereference [recovered, repanicked]
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x6dd35d2]

goroutine 510 [running]:
github.com/akash-network/provider/cmd/provider-services/cmd.(*accountQuerier).run.func1()
	github.com/akash-network/provider/cmd/provider-services/cmd/certs.go:355 +0x32
panic({0x75729e0?, 0xbff1d10?})
	runtime/panic.go:783 +0x132
github.com/akash-network/provider/cmd/provider-services/cmd.(*accountQuerier).run(0xc00219a8c0)
	github.com/akash-network/provider/cmd/provider-services/cmd/certs.go:365 +0x1bd

Expected behavior
Provider should start successfully and remain running, handling closed leases gracefully without crashing.

Additional context

• Provider was working before proxy configuration change
• Issue persists with both public RPC and local RPC node
• Closed leases are properly closed on-chain (state: closed, reason: lease_closed_invalid)
• Provider has 5 closed leases total
• Attempted fixes (none resolved):
  • Reduced valid certificates from 3 to 1
  • Switched to local RPC node
  • Adjusted balance-checker settings
  • Verified proxy/tunnel configuration

Request
Is there a known issue with certs.go:365 when processing closed leases? Is there a workaround or fix available?

Previous Issue: #1148 (console sync issues - resolved)