Setting up an open-source Bitcoin miner like the Bitaxe for solo mining is only half the battle. Once you save your pool configurations, you need to confirm that your hardware is actually communicating with the network and submitting shares. If you don't verify the connection correctly, you might leave your device running for weeks without ever being entered into the block lottery.
Verifying your Bitaxe solo pool connection requires checking two distinct places: the local AxeOS dashboard and the pool-side interface. Let's break down how to check both, spot connection errors instantly, and ensure your hash power is counted.
1. Checking the Local AxeOS Dashboard
Your first line of verification is the built-in web interface running directly on the device.
- Open a web browser on a device connected to the same local network as your miner.
- Type the local IP address of your Bitaxe (which is displayed on its onboard OLED screen) into the address bar.
- Locate the primary mining statistics panel on the main overview screen.
A healthy, active solo connection displays specific live metrics. Look for a stable hashrate matching your specific Bitaxe model (for example, around 1.2 TH/s for newer iterations), an active session time, and a climbing count of accepted shares alongside zero or very low rejected shares.
If your hashrate reads zero or hovers indefinitely, the miner isn't pushing work to the network. This local check tells you whether the hardware itself is functional and generating hashes.
2. Confirming Live Status on the Solo Pool
Because solo mining pools like Solo CKPool don't require traditional user accounts or registration passwords, they identify your miner using the payout address you provided during setup.
- Navigate to your chosen solo pool's public web dashboard.
- Locate the search or stats lookup bar, which is usually positioned right on the homepage.
- Paste your exact Bitcoin wallet address into the search field and submit.
If the connection is successful, the pool page will load a dedicated worker profile matching your address. You should see your active worker identifier, a recent "last share submitted" timestamp, and your rolling average hashrate over the last hour.
Note: Solo mining luck means blocks are found infrequently, so don't panic if your balance remains at zero. You are verifying network connectivity and share submission, not immediate payouts.
Common Connection Pitfalls and Fixes
If your local dashboard looks active, but the pool interface shows nothing, or if both are blank, the issue usually stems from a minor configuration typo.
- Incorrect Stratum URL syntax: Make sure you didn't paste prefixes like
stratum+tcp://into fields that only require the clean hostname. - Wallet address errors: A single misplaced character in your Bitcoin address means hashes go toward an invalid destination, or the pool API fails to recognize your lookup.
- Port blocking: If your router or ISP restricts port 3333, try switching your pool port configuration to port 443, which handles standard secure web traffic.
- Difficulty mismatch: Some pools feature a high minimum difficulty floor that can stall low-power standalone devices, making it look like the miner is disconnected. Ensure you are paired with a miner-friendly solo endpoint.
Frequently Asked Questions
How long does it take for my miner to appear on the pool page?
It typically takes between 5 to 10 minutes after a successful boot and connection for the pool's statistics engine to register a new worker and display your live hashrate.
What should I do if my accepted share count climbs, but the pool shows offline?
Double-check that the Bitcoin address entered in your AxeOS pool settings matches the exact address you are typing into the pool's search lookup bar. Even a tiny discrepancy will cause the dashboard to look for the wrong identifier.
Does a dropped Wi-Fi connection require a full reconfiguration?
No. AxeOS saves your settings in onboard non-volatile memory. If your home network drops briefly, the Bitaxe will automatically attempt to reconnect using your saved credentials once the router comes back online.
Can I run a backup pool in case my primary solo pool goes down?
Yes. Modern Bitaxe firmware supports a secondary fallback pool entry. You can input an alternative solo endpoint so that if your primary connection drops, the device immediately shifts its hash power over without manual intervention.
