Service Endpoints

Overview

After a successful solo one-shot single deploy, Solo sets up port-forwards to the following local services. Use these endpoints to connect your application, SDK, or tooling to the running network.

Note: The ports below are Solo’s default targets. If a port is already in use on your machine, Solo automatically selects the next available port and logs Using available port <port>. See Port availability for how to look up the ports your deployment is actually using.

Solo 0.63 and later (current defaults)

Verify the endpoints

• Bash
• PowerShell

# Consensus node (gRPC)
nc -zv localhost 35211

# Mirror node REST API
curl http://localhost:38081/api/v1/transactions

# JSON-RPC relay
curl -X POST http://localhost:37546 \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

# Consensus node (gRPC)
Test-NetConnection localhost -Port 35211

# Mirror node REST API
Invoke-RestMethod http://localhost:38081/api/v1/transactions

# JSON-RPC relay
Invoke-RestMethod -Method Post -Uri 'http://localhost:37546' `
  -ContentType 'application/json' `
  -Body '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

macOS note: Running nc -zv localhost 35211 may print two lines:

nc: connectx to localhost port 35211 (tcp) failed: Connection refused
Connection to localhost port 35211 [tcp/*] succeeded!

The first line is a failed IPv6 attempt — this is expected on macOS. The second line confirms the IPv4 connection succeeded. The port is reachable.

Note: In PowerShell, curl is an alias for Invoke-WebRequest, so bash curl flags will not work. Use curl.exe explicitly if you prefer the bash-style syntax.

Solo 0.62 and earlier

If you are using Solo 0.62 or earlier, the default port-forward targets differ:

Note: localhost:5551 is the direct Mirror Node REST service, accessible only via manual kubectl port-forward, and is being phased out. Always use the ingress-based port (8081 for Solo 0.62 and earlier, 38081 for Solo 0.63+).

Connecting your application

Quick reference for SDK and tooling configuration (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 SDK-specific connection examples, see:

• Using Solo with Hiero SDKs
• Using Solo with EVM Tools
• Accessing Solo Services

Port availability

Solo uses kubectl port-forward to tunnel traffic from your machine to services running inside Kubernetes. Before opening each tunnel, Solo tries the configured port:

• If the port is free, Solo logs: Using requested port <port>.
• If the port is already occupied (by another process, or by a previous Solo session that did not clean up its port-forwards), Solo finds the next available port and logs: Using available port <port>.

The actual ports used are printed at the end of solo one-shot single deploy. You can also look them up at any time with the Solo CLI, using your deployment name (see Capture your deployment name).

To view the active port assignments:

solo deployment config ports --deployment <deployment-name>

The output directory is one-shot-<deployment-name>, and the default deployment name is one-shot. So the default output directory is ~/.solo/one-shot-one-shot/.

• Bash
• PowerShell

cat ~/.solo/one-shot-one-shot/forwards

Get-Content "$env:USERPROFILE\.solo\one-shot-one-shot\forwards"

 *** Consensus node gRPC ***
-------------------------------------------------------------------------------
 - component 1: localhost:35211 -> pod:50211

solo deployment config info --deployment one-shot

To restore port-forwards after a system restart without redeploying:

solo deployment port-forwards refresh --deployment one-shot

Note: solo deployment refresh port-forwards still works but is deprecated in favor of solo deployment port-forwards refresh and will be removed in a future release.

To stop all port-forwards for a deployment (for example, before shutting down your machine):

solo deployment port-forwards stop --deployment one-shot

This closes the underlying kubectl port-forward processes and removes them from the deployment’s remote config, so they are not restored automatically. Run solo deployment port-forwards refresh --deployment one-shot afterward to re-establish them.