Set up a Bitaxe step by step: Wi-Fi, AxeOS and pool
A Bitaxe takes about ten minutes to set up, with nothing to install: a Wi-Fi network to join, a page to fill in, four pool fields. Here are the six steps, every field explained, the settings of the main solo pools and what to check if nothing is hashing. The menu names are those of AxeOS 2.15.4, the latest release as of 28 October 2026.
Published 23 September 2026, updated 14 November 2026 · by Pixel · 10 min read
6:25
Plug the Bitaxe in, join its open Wi-Fi network (Bitaxe_ plus four characters) from your phone and give it your 2.4 GHz Wi-Fi at 192.168.4.1. Then, on your own network, open AxeOS at the IP address shown on its screen, Pool menu: server, port, Bitcoin address plus a dot and a name, password x (AxeOS 2.15.4).
Contents 9 parts and a FAQ · 10 min read
1. What you need
- The Bitaxe and the power supply meant for your model: 5 V and 6 A for a Gamma 601 (other models are in the table further down). A supply that is too weak can drag the hashrate Computing power: the number of attempts per second of a machine or of the whole network. The higher it is, the more tickets you play in each draw. down or cause crashes.
- 2.4 GHz Wi-Fi: the Bitaxe connects through an ESP32-S3 A microcontroller worth a few euros, the kind in smart plugs. It can compute SHA-256, but millions of times slower than an ASIC chip: an ESP32 miner has no real chance. The lottery miner trap chip, which only does 2.4 GHz Wi-Fi. The Gamma has no Ethernet port.
- A Bitcoin address from a wallet you hold the keys to, not an exchange address: which wallet to choose.
- A phone or a computer with a browser. Nothing to install.
These steps apply to every Bitaxe running AxeOS The open-source Bitaxe software, set from a browser: pool, frequency, voltage, fan. Update it, the project’s open-source software (ESP-Miner), including the Gamma 601 in the video: my Bitaxe Gamma review. On an AxeOS version older than 2.15, some menus have another name, but the fields stay the same.
2. The 6 steps, from power-up to the first share
- Plug in the Bitaxe. The screen lights up. As long as it is not on your Wi-Fi, it creates its own open network, with no password, called “Bitaxe_” followed by four characters (for example Bitaxe_3F2A), and shows that name on the screen. Since AxeOS 2.11, the screen also shows a small QR code: scan it with your phone to join that network.
- Join that network from your phone or computer. The setup page opens by itself; if not, type
http://192.168.4.1in the browser. This network has no internet access: if your phone offers to leave it, stay connected while you set it up. - Give it your Wi-Fi. The page only shows the network part, which is normal. In Wi-Fi SSID, pick your 2.4 GHz network (the scan button lists the ones the Bitaxe can see), enter its password in Wi-Fi Password, then click Save, then Restart. The Bitaxe restarts, joins your router and shows the IP address the router gave it.
- Open AxeOS. Back on your usual Wi-Fi, type that address in the browser, for example
http://192.168.1.42: this is the Bitaxe dashboard. Since AxeOS 2.15,http://bitaxe.localalso works on many devices. - Set the pool A server that machines connect to. A regular pool shares the earnings, a solo pool does not. Solo or pool?. Pool menu: fill in Stratum The language machines and pools speak. Host, Stratum Port, User and Password with the values in the next part, click Save, then Restart. Before version 2.9, these fields were under Pool Settings, or under Settings.
- Check. After a minute or two, the hashrate shows up (about 1.2 TH/s rated for a Gamma 601) and the Shares An attempt good enough to be counted by the pool. It proves your machine is working, even if it is not enough to find a block. counter climbs. On findmyblock.xyz, search for your address: your machine shows up under its name.
When mining solo, one last check is worth it: on the AxeOS 2.15 dashboard, the Block Header panel lists, on the Outputs line, the addresses the block would pay. Yours should be there, marked with a star. And do not wait for the block: at 1.2 TH/s, it is about 1 chance in 15,300 per year (network as of 14 November 2026). The math for your own machine: the solo mining calculator.
3. Pool settings, field by field
eu.findmyblock.xyz3335your-bitcoin-address.bitaxe1xThese are the settings for FindMyBlock, the solo pool I built and mine on myself: 0% fee, and if your machine finds a block, the reward goes straight to your address, without passing through me. Each field, in the order of the Pool page:
- Stratum Host: the server name, on its own. Since AxeOS 2.11, you can paste the full address,
stratum+tcp://eu.findmyblock.xyz:3335: AxeOS strips the prefix and moves the port into its own box. On an older version, type onlyeu.findmyblock.xyz. - Stratum Port: the server’s door number. On FindMyBlock, 3335 for every machine you own (Bitaxe, NerdQAxe or ASIC A chip built for a single task. Bitcoin mining chips can only compute hashes, but extremely fast.), 3336 only for rented hashrate: that port keeps a fixed high difficulty How many attempts it takes on average to find a block. It adjusts itself about every two weeks. Difficulty explained, and a Bitaxe pointed at it would take a very long time to send a single share.
- Stratum Protocol, if your version shows it: keep Stratum V1. AxeOS itself warns that not all pools support V2.
- User: your Bitcoin address, a dot, then a name for the machine, with no spaces. The name tells your machines apart on the pool; the reward goes to the address.
- Password:
x, the usual value. CKPool even states that it ignores this field. - Advanced options (Show Advanced Options): leave them as they are. Connection Security must stay on No TLS for a stratum+tcp address; AxeOS 2.15 sets it by itself when you paste the full address.
Watch out for the factory address. The Gamma 601 factory configuration file, published by the project, points the machine at Public Pool, with CKPool as the fallback, and a default address that is not yours, in both. As long as one pool keeps it, AxeOS shows a yellow warning at the top of the Pool page: You are using the default factory Bitcoin address. It should be gone when you are done.
4. Settings for the main solo pools
A Bitaxe mines on any pool: you only change these fields. Here is what four well-known solo pools publish, taken from their own pages. FindMyBlock is my pool: I list it first, it is up to you to compare. To choose in detail: which solo pool to choose.
| Pool | Stratum Host | Port | User | Fee |
|---|---|---|---|---|
| FindMyBlock (my pool) | eu.findmyblock.xyz | 3335 (3336 for rentals) | address.name | 0% |
| Solo CK | stratum.ckpool.org | 3333 | address, name optional | 2% |
| Public Pool | public-pool.io | 3333 | address.name | 0% |
| Braiins Solo | solo.stratum.braiins.com | 3333 (or 443, or 25) | address, name optional | 0.5% |
CKPool also runs regional servers, including eusolo.ckpool.org in Germany; its main address picks the fastest server to reach by itself. Public Pool funds its 0% with affiliate links, and Braiins passes its 0.5% to the authors of CKPool, the software it runs. On all four pools, in solo mode, a block reward goes straight to the miner’s address.
5. A fallback pool, just in case
If the main pool stops answering, AxeOS can switch to a second pool on its own. On AxeOS 2.15, the Pool page shows two cards: Pool 1, tagged Primary, and Pool 2, tagged Fallback. Click Pool 2, fill it in like the first one with another solo pool and your address, then Save and Restart. On versions 2.9 to 2.14, it is the Fallback Pool Configuration block, below the main pool.
According to the AxeOS 2.15.4 code, the machine moves to the fallback after three failed connection attempts, checks the main pool again every minute and returns as soon as it answers. Check the fallback’s address: if you never changed it, it is still the factory one. The details, and which pool to use as a fallback: the Bitaxe fallback pool.
6. Finding the Bitaxe’s IP address
- On its screen: once connected, it cycles through its pages, one of which shows IP Address.
- By name: since AxeOS 2.15,
http://bitaxe.local. If that name is already taken on the network, the machine adds a suffix taken from its hardware address, such as bitaxe-12ab. You can change it under Network, Hostname field. - In your router: its list of connected devices usually shows the same name, bitaxe by default.
- From another Bitaxe: in AxeOS 2.15, the Swarm page has an Auto Scan button that looks for the other machines on the local network.
- If it lost your Wi-Fi: as soon as the connection drops, it turns its Bitaxe_ network back on and tries to reconnect every five seconds. Join that network and fix the Wi-Fi at
http://192.168.4.1.
If the IP address changes at every restart, reserve it in your router settings (a fixed DHCP lease): you will always find it in the same place.
7. Not hashing? The quick checks
- Nothing goes out (0 shares): reread Stratum Host, the port and User, character by character, with no space before or after the address.
- TLS: for a stratum+tcp address, like every one in the table above, Connection Security must be on No TLS. If it is on TLS, set it back to No TLS.
- The yellow warning on the Pool page: one of the pools, main or fallback, still carries the factory address.
- The router: the AxeOS documentation says some routers block mining, for example from ASUS and TP-Link; turn off AiProtection and the IoT settings.
- Power: for a 5 V Bitaxe, the OSMU wiki gives 4.8 to 5.3 V as the safe input range. The dashboard shows Input Voltage, and Danger: Low Voltage when it drops too low.
- Heat: the same wiki sets the limits at a chip under 70 °C and a voltage regulator under 90 °C.
- Really unplug it: cut the power and plug it back in, rather than just restarting from the interface, as the OSMU wiki also advises.
- As a last resort, reinstall the software over USB with the official Bitaxe Web Flasher, from Chrome, Edge or Brave on a computer. Without the Keep configuration box, unticked by default, the machine comes back with factory settings: then redo steps 1 to 5. If the computer does not see it on a USB-C port, the AxeOS documentation suggests a USB-A adapter.
The full diagnosis, symptom by symptom: Bitaxe not hashing. For Wi-Fi alone: Bitaxe will not connect to Wi-Fi.
8. Depending on your model: what changes
The steps are the same across the whole AxeOS family. What changes from one machine to the next, according to my reviews:
| Machine | Power supply | First boot | Hashrate to expect | Good to know |
|---|---|---|---|---|
| Bitaxe Gamma 601 | 5 V, 6 A, barrel jack | its own Wi-Fi network, name shown on screen | about 1.2 TH/s, rated | 2.4 GHz Wi-Fi only |
| Bitaxe Gamma GT Turbo | XT30 connector instead of the jack | same as other Bitaxes | 2.08 to 2.28 TH/s, from the interface (stock fan, then Noctua) | Reset and Boot buttons, USB-C port; some units ship with a test address |
| NerdQAxe++ Hydro | 12 V, 10 A (120 W), included | network whose name starts with NerdAxe | about 4.8 TH/s, rated | AxeOS; its updates come from the NerdQAxe project page |
| NerdOctaxe | 12 V, high-current connector, included | its own Wi-Fi network | 9.6 to 9.7 TH/s, measured in my review | modified AxeOS, Wi-Fi only |
On the Gamma GT, the Boot button forces reinstall mode if the machine no longer starts at all. And on all these machines, the first thing to check stays the same: the address in User, on the main pool and on the fallback.
9. Good habits
- Keep the factory settings at first. Raising frequency or voltage gains a little hashrate but runs hotter and wears the chip. The day you want to try: overclocking a Bitaxe.
- Let it breathe. Clear fan, no closed case. The heatsink is hot to the touch: that is normal. If the chip gets close to 70 °C, see miner running hot.
- Update it from the Update menu when a new version comes out, after writing down your settings: updating AxeOS.
- Give each machine a different name (bitaxe1, bitaxe2 and so on), in User to tell them apart on the pool, and in Hostname to tell them apart on the router.
Frequently asked questions
What is the IP address of a Bitaxe?
The 192.168.4.1 address only works on its own Bitaxe_ network, to set up the Wi-Fi. On your network, the router gives it an address: it shows on its screen and in the router’s device list. Since AxeOS 2.15, http://bitaxe.local also leads to it.
Does the Bitaxe work on 5 GHz Wi-Fi?
No. It connects through an ESP32-S3 chip, which only does 2.4 GHz. If your router broadcasts both bands under one name, create a separate 2.4 GHz network: the Wi-Fi fixes.
What goes in the User field of a Bitaxe?
Your Bitcoin address, a dot, then a machine name, with no spaces: for example your-address.bitaxe1. The password is x, and the name only tells the machine apart on the pool.
Should I type stratum+tcp:// in Stratum Host?
No: the field expects the server name alone, and the port goes in its own box. Since AxeOS 2.11, if you paste the full address, AxeOS strips the prefix and moves the port by itself.
Do these steps work for a NerdQAxe or a NerdOctaxe?
Yes: they run AxeOS, with their own power supply (12 V on the NerdQAxe++ Hydro and the NerdOctaxe I reviewed) and their own setup network, whose name starts with NerdAxe on the NerdQAxe++ Hydro. The pool fields are the same.
Sources
- ESP-Miner (AxeOS) release notes, including 2.15.4 of 21 October 2026
- ESP-Miner official documentation (bitaxe.local, routers that block mining, USB)
- AxeOS 2.15.4 Wi-Fi code: open Bitaxe_ network, a new attempt every 5 seconds
- Bitaxe Web Flasher, the official USB reinstall tool
- OSMU wiki FAQ (input voltage, temperatures, troubleshooting)
- Solo CK: servers, username and fee
- Public Pool: connection addresses and fee
- Braiins: solo mining address, username and fee
A question about this guide? Ask it on the Discord, several of us answer there.
Other guides
-
Bitaxe not connecting to Wi-Fi: the fixes, in order
2.4 GHz first, then your router, the error messages and a clean reset.
12 min read · updated 28 Oct 2026 -
Update AxeOS step by step
Get the right version, install it safely, and what to do if it gets stuck.
5 min read · updated 2 Nov 2026 -
Bitaxe not hashing: hashrate at 0, pool unreachable, reboots, the fixes in order
Hashrate at 0, rejected shares, power fault: every AxeOS message and its fix.
15 min read · updated 14 Nov 2026 · new -
Fallback pool and dual pool on a Bitaxe or a NerdQAxe
Switch to a second pool when one fails, or split your hashrate between two pools.
13 min read · updated 14 Nov 2026 · new