Setting up an open-source ASIC miner like the Bitaxe for lottery-style solo mining is straightforward, but confirming that your unit is actively communicating with a solo pool requires checking both local hardware indicators and remote dashboard metrics. If you're staring at a freshly flashed device and aren't sure whether your shares are actually reaching a solo stratum server, you need a precise diagnostic routine to verify the link.
When a Bitaxe fails to talk to a solo pool, it usually keeps hashing locally or sits idle, wasting power while missing out on block rewards. This guide walks you through checking your local AxeOS web interface, diagnosing stratum handshake errors, confirming activity on pool-side dashboards, and fixing configuration mismatches.
Checking Local Status on the AxeOS Dashboard
The first place to verify your connection is the local web dashboard hosted on your Bitaxe. Once your miner joins your home Wi-Fi network, locate its local IP address on the built-in OLED or LCD screen. Type that IP address into a browser on a device connected to the same network.
Look closely at the main status screen for the following indicators:
- Hashrate output: A stable hashrate matching your specific model (such as ~500 GH/s for an Ultra or higher for newer Gamma variants) indicates the ASIC chip is running and submitting work.
- Pool connection status: AxeOS will display whether the stratum connection is active or retrying. If it says disconnected, your miner isn't reaching the server.
- Accepted versus rejected shares: A healthy miner steadily accumulates accepted shares with zero or near-zero rejected shares. If rejected shares climb rapidly, your connection is unstable or your stratum credentials contain errors.
Verifying Pool-Side Activity
Local metrics can sometimes look normal even if the stratum server is rejecting your authentication. To confirm your Bitaxe is truly handshaking with a solo pool like CKPool or Public Pool, check the pool's web interface.
Paste your Bitcoin wallet address—the exact address entered into your Bitaxe user field—into the search bar of your chosen solo pool's frontend. Most solo pools allow you to view active workers by entering your payout address.
Within one to two minutes of a successful boot, your worker should appear on the pool dashboard. You should see active workers reporting matching hashrates, current difficulty targets, and recent share submissions. If the pool search yields no results or shows an offline status while your local dashboard claims it's connected, your stratum user string has a mismatch.
Common Configuration Mistakes That Break Stratum Links
Most connection failures stem from minor syntax errors in the AxeOS pool settings page. Review your configuration against these common pitfalls:
- Incorrect wallet address: For solo mining, the stratum user field must be your raw Bitcoin address. Typing an extra character, missing a checksum digit, or pasting an exchange deposit address that lacks proper routing will cause the pool to reject your blocks. Some firmware versions require your address followed by a worker suffix (e.g.,
bc1q... .bitaxe1), while others take just the clean address. - Wrong stratum URL or port: Ensure you are using the correct protocol prefix, such as
stratum+tcp://, followed by the exact domain and port number specified by your solo provider. A stray space at the end of the URL string will break TCP socket creation. - Password field left blank: While account-based pools need specific worker passwords, solo pools typically ignore the password field. However, leaving it completely empty can trigger validation errors on certain AxeOS builds. Enter a simple placeholder character like
xto ensure the field satisfies the parser.
Fixing Network and Firewall Obstacles
If your Bitaxe still refuses to establish a stable pool connection, the issue may lie within your local network environment.
Many modern mesh routers and enterprise-grade access points isolate IoT devices or block unfamiliar outbound ports. Solo mining pools communicate over non-standard TCP ports (such as 3333 or custom ports designated by the pool operator). Check your router settings to ensure outbound traffic on these ports isn't blocked by a strict firewall or automated intrusion prevention system.
Another frequent culprit is Wi-Fi band steering. If your router combines 2.4 GHz and 5 GHz bands under a single SSID, the Bitaxe—which typically relies on 2.4 GHz Wi-Fi radios—may struggle to maintain a stable handshake. Assigning your miner to a dedicated 2.4 GHz guest network or locking your router's band allocation often resolves intermittent packet drops.
Frequently Asked Questions
What should I do if my Bitaxe shows a local hashrate but the solo pool shows zero workers?
This usually means your miner is powered and hashing internally, but your stratum username (your Bitcoin address) contains a typo, or you are pointing to the wrong pool port. Double-check the user field character by character against your wallet.
Why does my Bitaxe keep looping between connected and disconnected states?
Frequent reconnections point to weak Wi-Fi signal strength or an overloaded power supply causing voltage drops during heavy ASIC loads. Move the miner closer to your wireless access point or test it with a dedicated, high-amperage power brick.
Do I need to keep a web browser open to continue solo mining?
No. Once saved, your Wi-Fi credentials and pool settings are written to the Bitaxe's onboard flash memory. The device operates independently and will continue hashing as long as it has power and internet access.
How long does it take for my Bitaxe to appear on public solo pool leaderboards?
Most solo pools register incoming workers within 60 to 120 seconds of receiving valid stratum shares. If your worker doesn't appear after five minutes of continuous uptime, reboot the device and review your network logs.
