# FAQs

> Frequently asked questions about the Solo CLI tool, covering deployment options, configuration choices, resource requirements, and common usage patterns. Find quick answers to typical Solo questions.

URL: https://solo.hiero.org/docs/faqs/

## One-command deployment options and variants

### How can I set up a Solo network in a single command?

You can run one of the following commands depending on your needs:

1. **Single Node Deployment (recommended for development):**

    ```bash
    solo one-shot single deploy
    ```

    > **Prerequisite:** Install Solo first with `npm install -g @hiero-ledger/solo@latest`. See [System Readiness](https://solo.hiero.org/docs/simple-solo-setup/system-readiness) for full install instructions. Homebrew (`brew install hiero-ledger/tools/solo`) is deprecated and will stop receiving updates after August 31, 2026.

    For more information on Single Node Deployment, see [Quickstart](https://solo.hiero.org/docs/simple-solo-setup/quickstart#step-2-deploy-a-local-network-one-shot)

2. **Multiple Node Deployment (for testing consensus scenarios):**

    ```bash
    solo one-shot multi deploy --num-consensus-nodes 3
    ```

    For more information on Multiple Node Deployment, see [Quickstart](https://solo.hiero.org/docs/simple-solo-setup/quickstart#step-2-deploy-a-local-network-one-shot)

3. **Advanced Deployment (with custom configuration file):**

    ```bash
    solo one-shot falcon deploy --values-file falcon-values.yaml
    ```

    - For more information on Advanced Deployment (with custom configuration file), see the [Advanced Solo Setup](https://solo.hiero.org/docs/advanced-solo-setup)

### Can I run Solo on a remote server?

Yes. Solo can deploy to any Kubernetes cluster, not just a local Kind cluster. For remote-cluster and more advanced deployment flows, see [Advanced Solo Setup](https://solo.hiero.org/docs/advanced-solo-setup).

---

## Destroying a network and cleaning up resources

### How can I tear down a Solo network in a single command?

You can run one of the following commands depending on how you deployed:

1. **Single Node Teardown:**

    ```bash
    solo one-shot single destroy
    ```

    For more information on Single Node Teardown, see [Quickstart](https://solo.hiero.org/docs/simple-solo-setup/quickstart#step-2-deploy-a-local-network-one-shot)

2. **Multiple Node Teardown:**

    ```bash
    solo one-shot multi destroy
    ```

    For more information on Multiple Node Teardown, see [Quickstart](https://solo.hiero.org/docs/simple-solo-setup/quickstart#step-2-deploy-a-local-network-one-shot)

3. **Advanced Deployment Teardown:**

    ```bash
    solo one-shot falcon destroy
    ```

    For more information on Advanced Deployment Teardown (with custom configuration file), see the [Advanced Solo Setup](https://solo.hiero.org/docs/advanced-solo-setup)

### Why should I destroy my network before redeploying?

Running `solo one-shot single deploy` while a prior deployment still exists causes conflicts and errors. Always run destroy first:

```bash
solo one-shot single destroy
solo one-shot single deploy
```

---

## Accessing exposed services

### How do I access services after deployment?

After running `solo one-shot single deploy`, your local services are available on
localhost. For the complete endpoint reference — default ports for Solo 0.63+
and Solo 0.62 and earlier, verification commands, and port lookup — see
[**Service Endpoints**](https://solo.hiero.org/docs/using-solo/endpoints).

- If any service is unreachable, confirm that all pods are healthy first:

    ```bash
    kubectl get pods -A | grep -v kube-system
    ```

    All Solo-related pods should be in a `Running` or `Completed` state before the endpoints become available.

### How do I connect my application to the local network?

Use these endpoints with your SDK or tooling (Solo 0.63 and later):

- **Hiero SDK (gRPC)**: `localhost:35211`, node account ID `0.0.3`
- **EVM tools (JSON-RPC)**: `http://localhost:37546`
- **Mirror Node REST**: `http://localhost:38081/api/v1/`

For verification commands, legacy ports, and port lookup, see [Service Endpoints](https://solo.hiero.org/docs/using-solo/endpoints).

### What should I do if `solo one-shot single destroy` fails or my Solo state is corrupted?

> **Warning:** This is a last resort. Always try `solo one-shot single destroy` first.

- If the standard destroy command fails, perform a full reset manually:

    ```bash
    # Delete only Solo-managed Kind clusters (names starting with "solo")
    kind get clusters | grep '^solo' | while read cluster; do
      kind delete cluster -n "$cluster"
    done
    
    # Remove Solo configuration and cache
    rm -rf ~/.solo
    ```

    > **Warning:** Always use the `grep '^solo'` filter above — omitting it will delete **every** Kind cluster on your machine, including those unrelated to Solo.

  After a full reset, you can redeploy by following the [Quickstart](https://solo.hiero.org/docs/simple-solo-setup/quickstart) guide.

- If you want to reset everything and start fresh immediately, run:

    ```bash
    # Delete only Solo-managed clusters and Solo config
    kind get clusters | grep '^solo' | while read cluster; do
      kind delete cluster -n "$cluster"
    done
    rm -rf ~/.solo
    
    # Deploy fresh
    solo one-shot single deploy
    ```

---

## Common usage patterns and gotchas

### 1. How can I avoid using genesis keys?

You can run `solo ledger system init` anytime after `solo consensus node start`.

### 2. Where can I find the default account keys?

- By default, Solo leverages the Hiero Consensus Node well known ED25519 private genesis key:

    ```bash
    302e020100300506032b65700422042091132178e72057a1d7528025956fe39b0b847f200ab59b2fdd367017f3087137
    ```

- the genesis public key is:

    ```bash
    302a300506032b65700321000aa8e21064c61eab86e2a9c164565b4e7a9a4146106e0a6cd03a8c395a110e92
    ```

  - Unless changed it is the private key for the default operator account `0.0.2` of the consensus network.

  - It is defined in [Hiero source code](https://github.com/hiero-ledger/hiero-consensus-node/blob/develop/hedera-node/data/onboard/GenesisPrivKey.txt)

### 3. What is the difference between ECDSA keys and ED25519 keys?

ED25519 is Hedera's native key type, while ECDSA (secp256k1) is used for EVM/Ethereum-style tooling and compatibility.  
For a detailed explanation of both key types and how they are used on Hedera, see [core concept](https://docs.hedera.com/hedera/core-concepts/keys-and-signatures).

### 4. Where can I find the EVM compatible private key?

You will need to use ECDSA keys for EVM tooling compatibility.  If you take the `privateKeyRaw` provided by Solo and prefix it with `0x` you will have the private key used by Ethereum compatible tools.

### 5. Where are my keys stored?

Keys are stored in `~/.solo/cache/keys/`. This directory contains:

- TLS certificates (`hedera-node*.crt`, `hedera-node*.key`)
- Signing keys (`s-private-node*.pem`, `s-public-node*.pem`)

### 6. How do I get the key for an account?

- Use the following command to get account balance and private key of the account `0.0.1007`:

    ```bash
    # get account info of 0.0.1007 and also show the private key
    solo ledger account info --account-id 0.0.1007 --deployment solo-deployment  --private-key
    ```

- The output would be similar to the following:

    ```bash
    {
     "accountId": "0.0.1007",
     "privateKey": "302e020100300506032b657004220420411a561013bceabb8cb83e3dc5558d052b9bd6a8977b5a7348bf9653034a29d7",
     "privateKeyRaw": "411a561013bceabb8cb83e3dc5558d052b9bd6a8977b5a7348bf9653034a29d7",
     "publicKey": "302a300506032b65700321001d8978e647aca1195c54a4d3d5dc469b95666de14e9b6edde8ed337917b96013",
     "balance": 100
    }
    ```

### 7. How to handle error "failed to setup chart repositories"

- If during the installation of solo-charts you see the error similar to the following:

    ```text
    failed to setup chart repositories,
    repository name (hedera-json-rpc-relay) already exists
    ```

- You need to remove the old helm repo manually, first run command `helm repo list` to
see the list of helm repos, and then run `helm repo remove <repo-name>` to remove the repo.
- For example:

    ```bash
    helm repo list
    
    NAME                  URL                                                       
    haproxy-ingress       https://haproxy-ingress.github.io/charts                  
    haproxytech           https://haproxytech.github.io/helm-charts                 
    metrics-server        https://kubernetes-sigs.github.io/metrics-server/         
    metallb               https://metallb.github.io/metallb                         
    mirror                https://hashgraph.github.io/hedera-mirror-node/charts     
    hedera-json-rpc-relay https://hashgraph.github.io/hedera-json-rpc-relay/charts
    ```

- Next run the command to remove the repo:

    ```bash
    helm repo remove hedera-json-rpc-relay
    ```

### 8. Why do I see unhealthy pods after deployment?

The most common cause is insufficient memory or CPU allocated to Docker Desktop. Minimum requirements:

| Deployment type | Minimum RAM | Minimum CPU |
| --- | --- | --- |
| Single-node | 12 GB | 6 cores |
| Multi-node (3+ nodes) | 16 GB | 8 cores |

Adjust these in **Docker Desktop → Settings → Resources** and restart Docker before deploying.

### 9. How do I find my deployment name?

Most management commands (stop, start, diagnostics) require the deployment name. Retrieve it with:

```bash
solo one-shot show deployment
```

This prints your deployment details, including the deployment name — it defaults to `one-shot` for one-shot deployments, or the value you passed to `--deployment`. Use it as `<deployment-name>` in subsequent commands. See [Capture your deployment name](https://solo.hiero.org/docs/simple-solo-setup/quickstart#capture-your-deployment-name) for more detail.

### 10. How do I create test accounts after deployment?

Create funded test accounts with:

```bash
solo ledger account create --deployment <deployment-name> --hbar-amount 100
```

### 11. How do I check which version of Solo I'm running?

```bash
solo --version

# For machine-readable output:
solo --version -o json
```

### 12. Why does resource usage grow during testing?

The mirror node accumulates transaction history while the network is running. If you notice increasing memory or disk usage during extended testing sessions, destroy and redeploy the network to reset it to a clean state.

### 13. How can I monitor my cluster more easily?

- [k9s](https://k9scli.io/) provides a real-time terminal UI for inspecting pods, logs, and cluster state. Install it with:

    ```bash
    brew install k9s
    ```

- Then run `k9s` to launch. It is especially helpful for watching pod startup progress during deployment.

### 14. How do I reset the ledger to a clean genesis state without redeploying?

Run `solo ledger system reset --deployment <deployment-name>` to reset the
ledger to genesis - clearing saved state and ledger-related secrets - while
keeping the same cluster and deployment. See
[Reset the ledger to genesis](https://solo.hiero.org/docs/simple-solo-setup/managing-your-network#reset-the-ledger-to-genesis).
