Take a breath: a Bitaxe that “won’t connect” is almost never a dead Bitaxe. Nine times out of ten the chip is healthy, the firmware booted fine, and the only thing standing between you and your first share is a WiFi setting. Before you box it up as broken, work through this guide. It is written for sovereign Bitcoiners who know their way around hardware but may be meeting AxeOS — the open-source firmware that runs your Bitaxe — for the first time. We will hand-hold every step.

The #1 cause: AxeOS only speaks 2.4 GHz WiFi

The Bitaxe is built around an ESP32-S3 microcontroller. That radio supports 2.4 GHz WiFi only — it physically cannot see or join a 5 GHz network. This is true of every Bitaxe (Supra, Gamma, Ultra, Hex) because they all share the same ESP32 networking core. It is a design constraint of the open-source hardware, not a defect.

So the most common failure looks exactly like a broken miner: you enter your WiFi name and password, AxeOS tries to connect, and it never comes back online. The culprit is usually that you handed it a 5 GHz SSID — or a single “combined” SSID where your router quietly steers the device onto the 5 GHz band. Fix the band, and the “dead” Bitaxe springs to life.

Step 1 — Find or split off a 2.4 GHz band

Many modern routers broadcast 2.4 GHz and 5 GHz under one name (often called Smart Connect, Band Steering, or OneMesh). That is convenient for phones but poison for a 2.4 GHz-only device. You want a 2.4 GHz network with its own name so you can point the Bitaxe straight at it. Router menus vary, but here is where to look:

Router / gateway	How to expose a 2.4 GHz network
ASUS	Wireless > General: turn off Smart Connect, then give the 2.4 GHz band its own SSID. Temporarily disable AiProtection while onboarding.
TP-Link	Wireless settings: disable Smart Connect, set a distinct 2.4 GHz SSID.
ISP gateway (Bell, Telus, Videotron, etc.)	Log into the gateway admin page; separate the bands, or create a 2.4 GHz guest network just for mining gear.
Mesh systems (eero, Orbi, Google/Nest)	Many hide band selection. Easiest path: enable a 2.4 GHz-only guest network, or briefly set a phone hotspot to 2.4 GHz to onboard the Bitaxe.

A clean trick that works on any setup: turn on your phone’s hotspot, force it to 2.4 GHz, and use that to get the Bitaxe configured and hashing once. It proves the miner is fine, then you can move it to your real 2.4 GHz network. Two more settings worth a glance: use WPA2 (or WPA2/WPA3-mixed) security rather than WPA3-only or legacy WEP, and temporarily disable AP isolation / client isolation so your phone or laptop can reach the miner.

Step 2 — Join the “Bitaxe_XXXX” setup network (AP mode)

On its very first boot — or any time it cannot reach a saved network — AxeOS broadcasts its own WiFi access point so you can configure it. This is called AP (access point) mode. Here is the full walkthrough:

1. Power the Bitaxe with a quality USB-C supply and wait about 30 seconds for it to boot.
2. On your phone or laptop, open WiFi settings and look for a network named Bitaxe_XXXX, where XXXX is a four-character hex code derived from the device’s MAC address (so every unit is unique). Recent AxeOS builds also show a QR code and a “Setup Wi-Fi:” prompt with that name on the OLED screen.
3. Connect to that Bitaxe_XXXX network. There is no password.
4. Open a browser and go to http://192.168.4.1. This is the AxeOS setup portal. (Type http:// explicitly — AxeOS runs over plain HTTP, not HTTPS.)
5. Pick your 2.4 GHz network from the list, enter the password, and save. The Bitaxe will reboot and join your network.

Step 3 — Enter the SSID and password carefully

This is where most “I typed it right!” failures hide. AxeOS is strict, so slow down here:

• Case matters. MyWiFi is not mywifi. The SSID and password are both case-sensitive.
• Watch special characters. Some symbols in a WiFi password can trip up the ESP32’s text encoding. If your password is full of unusual characters, temporarily set a simple WPA2 password to get connected, then test the original.
• No emoji or non-ASCII SSIDs. A network name with emoji or accented characters often will not match. Keep the mining SSID plain ASCII.
• Length limit. A WiFi SSID maxes out at 32 characters. Anything longer will not save cleanly.
• Hidden networks. If your SSID is hidden, it will not appear in the list — you may need to type it in manually exactly as named.

If the “Bitaxe_XXXX” network never appears

If you don’t see the setup access point at all, work down this list in order:

• Power first. An underpowered or flaky USB-C cable causes brownouts and odd boot behaviour. Use a known-good 5V supply and cable, ideally one rated for the Bitaxe’s draw.
• Give it time and refresh. Wait a full minute, then re-scan the WiFi list on your phone and laptop both — sometimes one device caches an old scan.
• Already connected once? If the Bitaxe successfully joined a network before, it stays in station mode and won’t broadcast the AP. The OLED’s connection screen shows Wi-Fi: with your network name; check your router’s connected-devices list for its IP instead.
• Re-flash AxeOS as a last resort. A corrupted firmware image can stop the AP from broadcasting. The Bitaxe re-flashes over USB-C from a Chromium-based browser (Chrome or Edge). Our D-Central flash hub covers the preparation checklist, browser requirements, and recovery steps before you write anything to the device.

Confirm you’re actually connected

Once AxeOS reboots onto your network, you have two ways to verify:

• OLED screen: the display cycles to a connection screen showing Wi-Fi: with your SSID and a status line. “Connected!” means you’re in; an error reason means it bounced back to AP mode — re-check your band and password.
• AxeOS dashboard: find the device’s IP on your router (or via the OLED’s URLs screen), then open http://<that-ip> in a browser. You should see live hashrate, temperature, and your pool settings. That dashboard is your command centre for tuning from here on.

Our full Bitaxe troubleshooting guide goes deeper on router-side gremlins — mDNS, AP isolation, static DHCP reservations, and weak-antenna range fixes — if the connection is flaky rather than absent.

Still nothing? When it might genuinely be DOA

If you’ve confirmed a real 2.4 GHz network, ruled out power and cable, double-checked the password, and a fresh re-flash still won’t bring up either the setup AP or a connection, then — and only then — you may have a true defect. We build and bench-test in our in-house BGA lab in Laval, and we stand behind what we ship: see our return and refund policy for DOA handling. We’re not Amazon; reach out and a human who actually understands these boards will help you sort it out.

Need the hardware itself, or want to compare boards first? Visit the Bitaxe product page, browse options on Buy Bitaxe in Canada, or dig into setup and tuning resources at the Bitaxe Hub. Credit where it’s due — none of this exists without the open-source Bitaxe community, whose work D-Central is proud to build on and support. Get the band right, and your little solo miner will be hashing in minutes.