Help setting up my Node

[JiminyPickIt]

Help Needed: Akash Provider "unsupported encrypted PEM" Error

Summary

I'm setting up an Akash provider and have successfully resolved the pricing configuration issues, but I'm stuck on a persistent "unsupported encrypted PEM" error that occurs regardless of how I generate certificates.

Environment

• Server: Hetzner VPS (2 CPU, 8GB RAM, Ubuntu 24.04.2 LTS)
• Kubernetes: K3s cluster (v1.32.6+k3s1) - working properly
• Provider Services: v0.6.10
• Wallet: Funded with 51 AKT, properly configured in both akash and provider-services keyrings

What's Working ✅

• Kubernetes cluster is healthy (kubectl get nodes works)
• Wallet is properly set up (myprovider key exists in both keyrings)
• Pricing configuration resolved (using command-line flags instead of YAML)
• Provider starts and reads Kubernetes config successfully

The Problem ❌

Every attempt to run the provider results in:

I[2025-07-05|22:00:54.186] using kube config file    cmp=provider path=/root/.kube/config
Error: unsupported encrypted PEM

Command Used

provider-services run \
  --from myprovider \
  --chain-id akashnet-2 \
  --keyring-backend test \
  --node https://rpc.akashnet.net:443 \
  --provider-config /root/.akash/provider.yaml \
  --bid-price-strategy scale \
  --bid-price-cpu-scale 0.001 \
  --bid-price-memory-scale 0.001 \
  --bid-price-storage-scale 0.001 \
  --cluster-k8s

Provider Configuration

host: https://178.156.189.220:8443
attributes:
  - key: region
    value: us-west
  - key: host
    value: calvin
  - key: organization
    value: hetzner
  - key: tier
    value: community

Certificate Attempts Tried

1. Original certificates: Created via blockchain, resulted in encrypted PEM error
2. OpenSSL with -nodes: openssl req -x509 -newkey rsa:2048 -keyout file.key -out file.crt -days 365 -nodes
3. Separate key generation: openssl genrsa -out file.key 2048 then certificate creation
4. No certificates: Removing all certificates results in "certificate not found" error

All approaches result in the same "unsupported encrypted PEM" error, even when explicitly creating unencrypted certificates.

Files in .akash Directory

• provider.yaml (configuration)
• akash17gsq8snkt06feqxgm50xlax4u4fql7hd7zjswd.pem (combined key + cert)
• akash17gsq8snkt06feqxgm50xlax4u4fql7hd7zjswd.key (private key)
• akash17gsq8snkt06feqxgm50xlax4u4fql7hd7zjswd.crt (certificate)
• Various keyring and config files

Questions

1. Is there a specific certificate format or generation method required for provider-services v0.6.10?
2. Could this be related to Go's crypto/tls library version or PEM parsing?
3. Are there any additional flags or configuration options to specify certificate handling?
4. Is there a way to run the provider with auto-generated certificates?

Any guidance would be greatly appreciated! I'm very close to getting this provider online.

Contact

Happy to provide additional logs, configuration files, or test any suggested solutions.

[nick134-bit]

Hey @JiminyPickIt please join us in our Discord and ask again in the Provider Channel: https://discord.com/invite/akash