Verify Bitaxe Is Connected To Solo Pool: A Step-by-Step Guide for Miners
Verify Bitaxe Is Connected To Solo Pool: A Step-by-Step Guide for Miners
For Bitcoin miners leveraging the Bitaxe ASIC, confirming a successful connection to a solo mining pool is the critical first step before any hashrate contribution translates into revenue. This guide provides a technical and operational walkthrough of how to verify the connection status, interpret the data, and troubleshoot common issues. Understanding these steps ensures that your mining hardware is not just active, but actively earning.
The Bitaxe, renowned for its open-source philosophy and efficiency, requires a specific configuration to operate outside of Stratum V2 pools and connect directly to a traditional solo pool. Because the device runs its own lightweight backend, verification moves beyond simple web interface checks and requires interaction with its local API or polling of backend logs. This article details the precise methods to confirm your Bitaxe is actively communicating with your chosen solo mining pool.
Understanding the Solo Pool Architecture
Before diving into verification, it is essential to understand what "solo mining" means in the context of the Bitaxe. Unlike pooled mining where hashrate is combined with thousands of other miners, solo mining means your specific Bitaxe is attempting to find valid blocks independently. The "pool" in this scenario is less a collective of miners and more a coordination server.
The solo pool software—often Stratum-merged or similar—acts as an intermediary. It receives work from the Bitcoin network, distributes it to your miner, and receives valid shares back. The pool also tracks your submitted shares and calculates any potential rewards. Therefore, verifying the connection is about ensuring the communication channel between the Bitaxe hardware and this coordination server is open and functional.
Method 1: The Web Interface Status Check
The most user-friendly method to verify connection status is through the Bitaxe's local web interface. This interface provides a real-time dashboard of the miner's activity, including network connection and pool communication.
To access this, you need to know the IP address of your Bitaxe on your local network. You can find this via your router's DHCP client list or by using a network scanning tool.
1. Open a web browser and enter `http://
2. Log in using the default credentials, which are usually `root` for the username and `root` for the password, unless you have customized them.
3. Once logged in, navigate to the "Status" or "Miner Stats" page. This is typically located in the main navigation menu.
On this status page, look for specific indicators related to pool communication. You should see fields labeled similarly to:
* **Pool URL:** This confirms the address of the pool server the Bitaxe is configured to use (e.g., `stratum+tcp://pool.example.com:3333`).
* **Pool Status:** This will explicitly state "Connected," "Disconnected," or "Connecting."
* **User/Worker Hashrate:** If the connection is successful, you will see active hashrate reported here, even if no shares have been accepted yet.
If the status shows "Disconnected," the first step is to verify the Pool URL is correct and that the pool server is online and reachable from your internet connection.
Method 2: Accessing the Backend API
For a more granular and technical verification, the Bitaxe provides a local API that can be queried directly. This method is particularly useful for scripting automated checks or when the web interface is slow to update.
The Bitaxe runs a local backend service that exposes endpoints for status and configuration. The most relevant endpoint for verification is the summary or status endpoint.
You will need to use a tool like `curl` from a computer on the same local network. Open a terminal or command prompt and execute the following command, replacing `
`curl http://
A successful command will return a JSON (JavaScript Object Notation) payload containing a wealth of information about the miner's current state. Within this JSON data, you need to look for keys related to the "server" or "pool" connection.
Key data points to parse from the output include:
* `"server": {"connected": true}`: This boolean value is the primary indicator. A value of `true` confirms a TCP connection to the pool server is established.
* `"server": {"url": "stratum+tcp://pool.example.com:3333"}`: This echoes the configured pool URL, confirming the target.
* `"miner": {"hardware": "bitaxe", "sha": 1000000000}`: This confirms the miner is actively hashing. A hashrate of zero while connected could indicate a configuration issue with your worker credentials.
If the `"connected":` value is `false`, the API will often provide an error message in another field, such as `"error": "failed to connect"`, which can guide your troubleshooting.
Method 3: Reviewing System Logs
When the web interface and API are not providing clear answers, the system logs offer a detailed, chronological account of what the Bitaxe has been doing since it last booted. These logs capture the handshake process with the pool server, including acceptance or rejection of connection attempts.
To access the logs, you must use SSH to connect to the Bitaxe's Linux operating system. You will need the IP address and root credentials mentioned earlier.
1. Open a terminal or an SSH client like PuTTY (on Windows).
2. Connect using the command: `ssh root@
3. Once logged in, enter the command to view the live log output: `logread`.
This command streams the system logs in real-time. You should look for entries containing the word "stratum" or the name of your pool software. A successful connection sequence will look something like this:
1. `Feb 23 10:00:01 Bitaxe stratum[123]: Connecting to stratum+tcp://pool.example.com:3333...`
2. `Feb 23 10:00:02 Bitaxe stratum[123]: Connected to stratum+tcp://pool.example.com:3333`
3. `Feb 23 10:00:03 Bitaxe stratum[123]: Subscribed to server`
4. `Feb 23 10:00:04 Bitaxe stratum[123]: Authentication for worker 'myworker' successful.`
The final line is the definitive confirmation. It indicates that not only is the TCP connection open, but the pool has also accepted your worker credentials. If you see an "Authentication failed" message, the problem lies with your worker name or password, not the network connection itself.
Common Pitfalls and Troubleshooting
Even after following the verification steps, a miner might still not be properly connected. Here are the most frequent issues and their solutions:
* **Firewall Restrictions:** Many home routers and networks block outbound connections on non-standard ports. Ensure that port `3333` (or the port your pool uses) is allowed outbound from your Bitaxe.
* **Incorrect Pool URL:** Double-check the pool URL for typos. It must be exactly `stratum+tcp://` followed by the domain and `:port`. A missing `s` in `stratum+tcp` is a common mistake.
* **Outdated Firmware:** An old Bitaxe firmware version might have bugs or compatibility issues with newer pool protocols. Always ensure your firmware is up to date via the web interface.
* **Pool Server Issues:** The pool server itself might be down or overloaded. Check the pool's official status page or social media for announcements.
* **Worker Credentials:** Even if the pool connection is established, mining will not proceed without valid worker credentials. Verify that the worker name and password are correctly entered in the Bitaxe's configuration.
By systematically applying these verification methods—checking the web interface, querying the API, and parsing the logs—you can move from uncertainty to confidence. You will know with certainty that your Bitaxe is not just on, but is correctly integrated into the Bitcoin network via your solo pool, ready to contribute hashpower and earn rewards.
