CPH Core
Independent chain operations, public explorer access, and bootstrap-era network visibility.
Troubleshooting + Support
This page is the public support surface for the most common CPH setup issues: waiting for blocks, missing .cookie auth, wallet loading, immature rewards, and blocks that never show up in the explorer.
Current Mining State
Public Mining Open
The node has public peers and the shared public chain has advanced beyond genesis. The public node bundle now carries bootstrap-mining support so normal users can start mining directly from the download package even if the early-chain freshness window still reports initial sync.
Most Common Issues
These are the exact issues new users hit most often on Windows.
`probe-gbt` says “waiting for blocks”
Your node is connected, but the shared public chain is still syncing or has not advanced enough for public mining on that machine. Keep the node online and rerun .\probe-gbt.cmd until the waiting message disappears.
No `.cookie` or RPC auth error
The miner and the node must be started from the same folder so they use the same .cookie file. If you moved the bundle or have two copies of it open, restart from one folder only.
Wallet exists, but balance fails
If createwallet miner says the wallet already exists, load it with .\cli.cmd loadwallet miner. Then use .\cli.cmd -rpcwallet=miner getbalances.
Rewards show as `immature`
That is normal. Coinbase rewards mature only after more blocks are added to the chain. Until then they are visible in the wallet, but not yet spendable.
Blocks do not appear in the explorer
The explorer shows only the shared public chain. If you mine on an isolated local branch, those blocks stay local and never appear publicly. Always mine only after your node has peers and the probe command is clean.
Port `39332` is already in use
If a second node tries to use the same RPC port, the bundle will fail silently or the CLI will talk to the wrong node. Stop old CPH nodes before starting a new bundle on the same PC.
Quick Health Checks
Wallet Checks
Useful Commands
Run these from the same folder as your current node bundle.
Check RPC cookie
Get-ChildItem -Force .\.cookie
Use this if the miner or CLI says it cannot locate RPC credentials.
Check node health
.\cli.cmd getblockchaininfo
Make sure the node is on the expected chain and see whether it is still in initial sync.
Check public readiness
.\probe-gbt.cmd
This is the fastest way to know if public mining is open on your current node.
Start the miner
.\start-solo-miner.cmd <your_cph_address>
Only run this after the probe command stops saying the node is waiting for blocks.
Load existing wallet
.\cli.cmd loadwallet miner
Use this if the wallet exists on disk but does not appear in listwallets.
Read your balances
.\cli.cmd -rpcwallet=miner getbalances
Look for immature, trusted, and pending balance states.
Support Model
Most support questions come down to one of these two cases.
Local machine issue
If .cookie is missing, the wallet is not loaded, or port 39332 is busy, the problem is on your PC and can be fixed locally.
Shared network issue
If the probe says the node is waiting for blocks, or the explorer still shows a lower height than expected, the issue is usually on the shared public chain rather than your PC.
Explorer mismatch
The explorer only shows blocks on the shared public chain. Local-only forks and isolated test mining do not appear there.
Need Human Help?
Send screenshots of your commands, node logs, and the exact message from probe-gbt or the miner window.