Bitaxe Troubleshooting Guide: Every Common Issue & How to Fix It

Bitaxe Troubleshooting Guide

Something is wrong with your Bitaxe. Maybe it is not hashing. Maybe it dropped off the network. Maybe the hashrate tanked overnight and you woke up to a blinking LED and a zero on your dashboard. You are not alone — and in most cases, the fix is straightforward.

This guide covers every common issue across the entire Bitaxe family: Supra, Ultra, Gamma, Hex, and GT (see our Bitaxe Hub for model details). From power problems and WiFi dropouts to firmware recovery and ASIC chip diagnostics, we have documented the real-world solutions that work. Not theory. Not forum speculation. Tested fixes from a team that has been building, selling, repairing, and modifying Bitaxe devices since the beginning of the ecosystem.

D-Central Technologies was a pioneer in the Bitaxe ecosystem — we created the original Bitaxe Mesh Stand, developed custom heatsinks for both standard Bitaxe and Hex models, and we stock every variant alongside the full open-source miner lineup. When we write troubleshooting instructions, it comes from hands-on experience with hundreds of units across every revision.

Most Bitaxe problems fall into a handful of categories. Work through the relevant section methodically. If you exhaust every step here and your device still is not cooperating, we have your back — see the When to Contact D-Central Support section at the end.

Quick Reference — Bitaxe Models at a Glance

Before diving into troubleshooting, make sure you know which model you have. Refer to the setup guide for your specific model: Supra, Ultra, Gamma, Hex, or GT. The power connector, voltage, expected hashrate, and chip type all vary — and using the wrong power supply will damage your device.

Quick Diagnostic Checklist

Before you dive into the detailed sections, run through this checklist. These five checks solve the majority of Bitaxe problems.

1. Power supply voltage and amperage — Is your PSU the correct voltage for your model? Does it supply enough current? Standard Bitaxe: 5V / 4A minimum (5A+ recommended). Hex/GT: 12V / 8A minimum.
2. Barrel jack / XT30 connection — Is the connector fully seated? Wiggle it gently. A loose connection causes intermittent power cycling.
3. WiFi network — Is your router broadcasting a 2.4 GHz network? The Bitaxe ESP32 does not support 5 GHz WiFi. Period.
4. Pool settings — Is your Stratum URL correct? Is the port right? Did you enter a valid on-chain Bitcoin address (not a Lightning address)?
5. Temperature — Is the heatsink properly attached with thermal paste/pad? Is the device in a ventilated location? Temperatures above 75°C on the ASIC chip will trigger throttling or shutdown.

If all five check out and you still have a problem, read on.

Power Issues

Power is the number one cause of Bitaxe problems. The ESP32 and ASIC chip are sensitive to voltage quality — they need clean, stable power within a tight range. Cheap power supplies, loose connectors, and wrong voltages cause more headaches than all other issues combined.

Bitaxe Will Not Turn On

You plug it in and nothing happens — no LED, no display, no WiFi hotspot. Here is a systematic walkthrough.

1. Verify PSU voltage — Check the label on your power supply. Standard Bitaxe models (Supra, Ultra, Gamma) require 5V DC. Hex and GT require 12V DC. If the label says anything other than the correct voltage, stop — you have the wrong supply.
2. Check the connector type — Standard Bitaxe uses a 5.5×2.1mm barrel jack, center-positive. The barrel jack looks like a small round plug with a hole in the center. Hex/GT uses an XT30 connector (small yellow 2-pin). Make sure the connector physically matches your device’s port.
3. Test the PSU independently — Use a multimeter on the barrel jack tip. Set your multimeter to DC voltage. The center pin should read positive voltage (5V or 12V depending on model). If you get 0V, the PSU is dead. If the polarity is reversed (negative on center), the PSU has wrong polarity and will not work.
4. Inspect the connector and port — Look inside the barrel jack port on the Bitaxe PCB with a flashlight. Bent or corroded pins prevent contact. Push the barrel jack in firmly — it should click and seat snugly.
5. Try a different PSU — If you have another 5V (or 12V for Hex/GT) power supply with the right connector, try it. This eliminates PSU failure from the equation immediately.
6. Check the USB-C port — The USB-C port on the Bitaxe is for data and firmware flashing only — it does not supply enough power to run the ASIC. However, connecting USB-C should at least power the ESP32 enough to see it in your computer’s Device Manager. If USB-C does not register either, the board may have sustained damage.

Intermittent Power / Random Restarts

The Bitaxe turns on but keeps restarting, flickering, or losing power. This is almost always a power delivery problem.

• Undersized PSU — A power supply rated at 5V/2A will not cut it. The ASIC chip alone can draw 3–5A at peak, and the ESP32 needs additional headroom. Use a PSU rated for at least 5V / 4A (20W), ideally 5V / 6A (30W). For Hex/GT models: 12V / 8A (96W) minimum.
• Voltage droop under load — Some cheap PSUs advertise 5V but sag to 4.5V or lower under load. The Bitaxe’s TPS546 voltage regulator has a narrow input range: it expects 4.8V–5.3V. Below 4.5V, the regulator trips and the device faults. Measure your PSU under load with a multimeter — measure while the Bitaxe is running, not with no load.
• Loose barrel jack — The 5.5×2.1mm barrel jack can work itself loose over time, especially if the cable puts lateral stress on the port. If you can wiggle the connector and the device flickers, you have a loose connection. Try a different cable or add strain relief.
• Extension cords and power strips — Low-quality power strips can introduce enough voltage drop to destabilize the Bitaxe. Plug the PSU directly into a wall outlet to test.
• Multiple devices on one PSU — If you are daisy-chaining or using a multi-output PSU, each Bitaxe needs its own dedicated output capable of full current delivery.

“Power Fault Detected” Error

The AxeOS dashboard shows “Power Fault Detected — Check your Power Supply”. This is the TPS546 voltage regulator reporting that output voltage is outside the regulation window.

This issue is most common on the Bitaxe Gamma (BM1370) due to its tighter voltage tolerance, but can affect any model.

1. Cold power cycle — Fully disconnect the barrel jack. Wait 10 seconds. Reconnect. A soft restart through the web UI or API does not clear the fault in all cases — a physical power disconnect is required.
2. Upgrade your PSU — Use a dedicated, quality 5V power supply rated for at least 5A. Avoid generic phone chargers and universal adapters. A PSU with active voltage regulation (not just a transformer) handles load transients better.
3. Check input voltage under load — Measure the voltage at the barrel jack while the device is mining. If it drops below 4.8V, the voltage regulator will fault. Anything between 4.9V–5.2V is ideal.
4. API restart workaround — In some cases, hitting the restart endpoint can clear the fault. Open your browser and navigate to: http://<bitaxe-ip>/api/system/restart

Power LED Behaviors

WiFi and Network Issues

The Bitaxe uses an ESP32-S3 microcontroller for all network communication. WiFi is the only way to connect — there is no Ethernet port. The ESP32 WiFi radio has quirks you need to understand.

Cannot Find Bitaxe on the Network

Your Bitaxe is powered on but you cannot access it from your browser or find it in your router’s device list.

1. Check for the setup hotspot — When a Bitaxe cannot connect to a saved WiFi network (or has never been configured), it creates its own WiFi access point named Bitaxe_XXXX (where XXXX is a hex code). Look for this in your phone or laptop’s WiFi list. Connect to it, then navigate to http://192.168.4.1 to access the setup page and enter your WiFi credentials.
2. Verify 2.4 GHz — The ESP32 only supports 2.4 GHz WiFi. If your router uses a combined SSID for both 2.4 GHz and 5 GHz, the Bitaxe may fail to connect. Solution: create a dedicated 2.4 GHz-only SSID in your router settings for your mining devices.
3. Check the SSID and password — WiFi credentials are case-sensitive. MyWiFi is not the same as mywifi or MYWIFI. Re-enter them carefully. Avoid special characters in the password if possible — some characters can cause encoding issues on the ESP32.
4. Check your router’s client list — Log into your router admin panel and look at connected devices. The Bitaxe may have connected under a hostname like bitaxe or ESP_XXXXXX. Note its IP address and try accessing it directly in your browser.
5. Try the IP address directly — If mDNS is not working (common on Windows and some Android devices), type the IP address directly into your browser: http://192.168.1.XXX (replace with the actual IP from your router’s client list).
6. Disable AP isolation — Some routers have “AP Isolation” or “Client Isolation” enabled, which prevents devices on the same WiFi network from communicating. Disable this in your router settings. Also check for “AI Protection” features (common on ASUS routers) that may block the Bitaxe from connecting to external pools.
7. Press the Boot button — On most Bitaxe models, pressing the Boot button will re-activate the WiFi access point, allowing you to reconnect and reconfigure credentials.

WiFi Keeps Disconnecting

The Bitaxe connects initially but drops off the network after minutes or hours, then reconnects. This cycle repeats.

• WiFi signal strength — The ESP32 has a small onboard antenna with limited range. Move the Bitaxe closer to your router, or add a WiFi extender or mesh node nearby. Thick walls, metal surfaces, and microwave ovens degrade 2.4 GHz signals significantly.
• Channel congestion — 2.4 GHz is crowded. If you have many neighbors with WiFi networks, channels 1, 6, and 11 get saturated. Use a WiFi analyzer app (available for phones) to find the least congested channel, then set your router to that channel manually instead of “Auto.”
• DHCP lease expiration — Some routers reclaim IP addresses aggressively. Assign a static DHCP reservation for your Bitaxe’s MAC address in your router settings to ensure it always gets the same IP.
• Router firmware — Outdated router firmware can cause compatibility issues with ESP32 devices. Update your router to the latest firmware.
• Power-saving modes — Some routers have power-saving features that put inactive clients to sleep. Disable any “WiFi power saving” or “green mode” settings on your router.

Cannot Access the AxeOS Web Interface

The Bitaxe is on your network (you can see it in your router’s client list) but typing the IP into your browser shows nothing.

• Use HTTP, not HTTPS — The AxeOS web server runs on plain HTTP. Your browser may auto-redirect to HTTPS. Type http:// explicitly: http://192.168.1.XXX
• Check the port — AxeOS serves on port 80 by default. If you have a firewall, VPN, or proxy running on your computer, it may block port 80 connections to local IPs.
• Try a different browser — Some browser extensions (ad blockers, privacy tools) can interfere with local HTTP connections. Try a clean browser or incognito mode.
• iOS / Apple devices and 401 errors — iOS Safari can throw authentication errors when connecting to ESP32 web servers. If you get a 401 error on an Apple device, switch to a non-iOS device to configure the Bitaxe, or try updating the firmware first.
• Web UI freeze — On some firmware versions (notably v2.11.0 beta), the web UI can become unresponsive after extended mining sessions even though the miner continues working. Power cycle the device to restore the UI.

mDNS / Hostname Resolution

Some users try to access their Bitaxe via hostname (e.g., http://bitaxe.local) instead of IP address. mDNS support depends on your operating system.

• macOS — mDNS (Bonjour) works natively. http://bitaxe.local should resolve.
• Windows — mDNS support is hit-or-miss. Install Bonjour Print Services (from Apple) for better mDNS support, or just use the IP address directly.
• Linux — Install avahi-daemon if mDNS is not working: sudo apt install avahi-daemon
• Android — Most Android devices do not support mDNS. Use the IP address.

Setting a Static IP

AxeOS does not have a built-in static IP configuration. The best approach is to assign a DHCP reservation in your router:

1. Log into your router’s admin panel.
2. Find the DHCP settings or “Address Reservation” section.
3. Find your Bitaxe’s MAC address (shown in AxeOS under System Info, or in your router’s connected devices list).
4. Create a reservation mapping that MAC address to your desired IP (e.g., 192.168.1.100).
5. Restart the Bitaxe so it picks up the reserved address on its next DHCP request.

Hashrate Issues

If you are overclocking and experiencing issues, review our Bitaxe Overclocking Manual first to verify your settings are within safe ranges.

Your Bitaxe is running but the numbers are wrong — either zero, too low, or bouncing around unpredictably. This section covers all hashrate-related problems.

Zero Hashrate / Not Hashing

The AxeOS dashboard shows 0 GH/s even though the device appears to be running. This is one of the most common issues, especially on BM1370 (Gamma/GT) devices.

1. Cold power cycle — Disconnect the power cable completely. Wait 10 seconds. Reconnect. On BM1370-based devices, a soft restart (UI button or API call) often does not recover from a zero-hashrate state — you need a full cold boot (power off, power on).
2. Check pool connection — In the AxeOS dashboard, verify the pool status shows “Connected.” If the pool is disconnected, the ASIC has no work to do and hashrate will read zero. See Pool Connection Issues.
3. Verify ASIC detection — The AxeOS System Info page shows the detected ASIC model. If it says “None” or shows an error, the ASIC chip may not be initializing properly. Cold power cycle again. If the ASIC remains undetected after multiple cold boots, the chip or its solder connections may be damaged.
4. Check the frequency and voltage settings — Navigate to http://<bitaxe-ip>/#/settings?oc and verify the frequency and voltage are set to sane defaults. If someone (or a firmware update) set the frequency too high or voltage too low, the ASIC will fail to hash. Reset to stock values:
   • BM1366 (Ultra): 485 MHz / 1200 mV
   • BM1368 (Supra): 490 MHz / 1200 mV
   • BM1370 (Gamma): 525 MHz / 1150 mV
5. Look at power draw — If the dashboard shows only ~5W when it should be 15–25W, the voltage regulator may be in a fault state. See Power Fault Detected.
6. Update firmware — Older firmware versions have known zero-hashrate bugs, particularly on BM1370. Update to the latest stable AxeOS release from the ESP-Miner releases page.

Low Hashrate (Below Expected)

The Bitaxe is hashing, but the reported hashrate is significantly below the expected values for your model.

Common causes of low hashrate:

• Thermal throttling — If the ASIC temperature exceeds 75°C, AxeOS automatically reduces frequency and voltage to prevent damage. This is the most common cause of unexpectedly low hashrate. See Temperature Issues.
• Frequency set too low — Check your overclocking settings. If frequency was reduced intentionally or during a previous troubleshooting session and never restored, your hashrate will be proportionally lower.
• Insufficient power — An undersized PSU that cannot maintain voltage under load causes the voltage regulator to throttle. The device may hash, but at reduced performance.
• Firmware regression — Some firmware updates (notably v2.11.0) changed fan/heat curves, resulting in higher temperatures and throttled hashrate at previously stable settings. If your hashrate dropped after a firmware update, check the release notes and consider rolling back to the previous version.
• Ambient temperature — Running a Bitaxe in a hot room (above 30°C / 86°F) means the heatsink starts at a disadvantage. Move the device to a cooler location or add supplemental airflow (a desk fan pointed at the heatsink makes a significant difference).

Hashrate Fluctuations

Some fluctuation in reported hashrate is completely normal. Mining is a probabilistic process — the reported hashrate in AxeOS is calculated from the number of shares found over a rolling time window, not from direct hardware measurement. Expect swings of +/- 15–20% around the average, especially over short time periods.

Fluctuations become a problem when:

• Hashrate drops to zero periodically then recovers — this suggests thermal throttling (check temps), power instability (check PSU), or pool disconnections (check pool status).
• The average hashrate over 24 hours is significantly below expected — this indicates a persistent underlying issue rather than normal variance.
• The hashrate graph shows sudden cliffs — this usually points to WiFi disconnections causing the pool connection to drop and the work queue to empty.

ASIC Chip Not Detected

If the AxeOS System Info page shows no ASIC chip detected, or shows “ASIC: Unknown,” the ESP32 cannot communicate with the mining chip.

• Cold power cycle — Always try this first. Disconnect power for 10 seconds, then reconnect.
• Inspect the board — Look for visible damage: cracked solder joints, burnt components, bent pins, or debris bridging contacts. Use a magnifying glass if available.
• Check firmware compatibility — Make sure your firmware version supports your ASIC chip. Flashing Supra firmware onto an Ultra (or vice versa) will result in the chip not being detected. Re-flash with the correct firmware for your model.
• Thermal paste squeeze-out — If thermal paste was applied too generously and squeezed out onto the PCB traces around the ASIC, it can cause shorts or communication failures. Clean any excess paste with isopropyl alcohol (99%) and a lint-free cloth.
• Hardware failure — If the ASIC chip remains undetected after all software troubleshooting, the chip itself or its connections may have failed. This requires board-level repair. Contact D-Central’s repair team.

Pool Connection Issues

If your Bitaxe is powered on and connected to WiFi but not mining, the problem is usually in the pool configuration. Getting the Stratum URL, port, and worker name right is critical.

Cannot Connect to Pool

1. Verify the Stratum URL — In AxeOS settings, the Stratum URL should not include the protocol prefix. Enter just the hostname:
   • Correct: public-pool.io
   • Wrong: stratum+tcp://public-pool.io
2. Verify the port — Each pool uses specific ports. Common configurations:

3. Check the Stratum User field — For solo pools, this must be a valid on-chain Bitcoin address. Not a Lightning address. Not an email. Not a username. A standard Bitcoin address starting with 1, 3, or bc1. You can optionally append a worker name with a dot: bc1qYourAddress.mybitaxe
4. Check your internet connection — The Bitaxe needs outbound internet access on the pool’s port. Some corporate networks, hotel WiFi, or ISPs block non-standard ports. Try a different network or use a pool that operates on port 443 (HTTPS port, rarely blocked).
5. Router firewall / AI protection — ASUS routers with AiProtection, or routers with “smart” firewall features, may block the Bitaxe’s outbound connections to mining pools. Disable these features or whitelist the Bitaxe’s IP address.
6. DNS resolution — The ESP32 relies on your router’s DNS server to resolve pool hostnames. If DNS is failing, the device cannot connect. Try setting your router’s DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) as a test.

Frequent Pool Disconnections

The pool connects initially but drops out periodically. The AxeOS log may show repeated “Stratum disconnected” or “Connection timeout” messages.

• WiFi instability — A flaky WiFi connection will manifest as pool disconnections. See WiFi Keeps Disconnecting.
• Internet stability — Run a long ping test from another device on the same network to check for packet loss: ping -t pool-hostname
• Fallback pool — Configure a fallback pool in AxeOS settings. If the primary pool goes down, the Bitaxe will automatically switch to the fallback. This keeps your ASIC hashing during pool outages.
• Pool server issues — Sometimes the pool itself has problems. Check the pool’s status page or social media. If the pool is down, switch to your fallback or a different pool temporarily.

Solo Mining vs. Pool Mining Settings

Make sure you understand the difference and have configured accordingly:

• Solo mining (e.g., Public Pool, Solo CKPool): You mine independently. If your Bitaxe finds a valid block, you get the entire 3.125 BTC block reward. No account creation needed — just your Bitcoin address.
• Pooled mining (e.g., Braiins, OCEAN): You combine hashrate with other miners and share rewards proportionally. Some pools require account creation. Check the pool’s documentation for Stratum settings.

If you intended to solo mine but joined a pooled mining service (or vice versa), you will still hash — but your reward structure will be different than expected.

Temperature Issues

ASIC chips generate significant heat relative to their size. On a Bitaxe, you are running the same chip technology found in a 3,000W industrial miner — condensed into a board the size of a playing card, cooled by a small heatsink and a tiny fan. Thermal management is everything.

Overheating — ASIC Temperature Too High

AxeOS will report the ASIC temperature on the dashboard. Safe operating range and thermal limits:

Additionally, the TPS546 voltage regulator has its own temperature limit at 105°C — if this component overheats, the device will throttle or shut down even if the ASIC temp looks fine.

How to reduce temperature:

1. Check heatsink contact — Remove the heatsink and inspect the thermal interface. The thermal pad or paste should have a visible imprint showing full contact with the ASIC die. If coverage is partial or the paste has dried out, clean both surfaces with isopropyl alcohol (99%) and reapply fresh thermal compound.
2. Reapply thermal paste — Use a quality thermal paste like Thermal Grizzly Kryonaut or similar. Apply a thin, even layer covering the ASIC die. More is not better — excess paste acts as an insulator. Replace thermal paste every 12–18 months under normal use, or every 6 months if overclocking.
3. Ensure airflow — The heatsink needs unobstructed airflow. Do not enclose the Bitaxe in a sealed box, stack things on top of it, or place it in a drawer. Use the Bitaxe Mesh Stand to position the device vertically for natural convection.
4. Add supplemental cooling — A small USB desk fan pointed at the heatsink can drop temperatures by 10–15°C. For serious overclockers, upgraded heatsinks (like D-Central’s custom Bitaxe heatsinks) with larger surface area make a significant difference.
5. Reduce ambient temperature — Ideal room temperature for a Bitaxe is 18–24°C (64–75°F). Every degree of ambient temperature directly adds to the chip temperature.
6. Lower overclock — If you are running above stock frequency, reduce it. Higher frequency = more heat. Find the sweet spot between hashrate and temperature for your cooling setup.

Fan Not Spinning (Hex / GT / Gamma Models)

On models with active fan cooling, a non-spinning fan will cause rapid overheating.

• Check fan settings in AxeOS — Navigate to Settings and verify the fan is not set to 0% or disabled. If Auto Fan Speed is on, the fan should ramp up as temperature increases. If it does not, try setting a manual fan speed (e.g., 75%) to test.
• Listen and look — Put your ear close to the device. A humming fan that does not spin may be mechanically jammed by dust or debris. A silent fan with no hum at all may have a dead motor or disconnected cable.
• Check the fan connector — The fan plugs into a small 2-pin or 3-pin header on the PCB. Make sure it is firmly seated. On the Hex and GT, the fan connector may be recessed — push it in until you feel it click.
• Dust the fan — Compressed air (from a can) can dislodge dust buildup. Hold the fan blade still with a toothpick while blowing air to prevent overspinning the motor.
• Replace the fan — If the fan motor is dead, replacement fans are available. Note the fan size and voltage before ordering.

Temperature Sensor Readings Seem Wrong

The dashboard shows temperatures that seem impossibly low (e.g., 10°C in a warm room) or impossibly high (e.g., 120°C with no performance issues).

• Firmware bug — Some firmware versions have had temperature reporting bugs, especially on multi-chip models. Update to the latest stable firmware.
• Sensor misread — The temperature sensor is built into the ASIC die. If the ASIC communication is glitchy (due to power issues or a loose connection), temperature readings can be erratic. A cold power cycle usually fixes transient sensor issues.
• VRM temperature vs. ASIC temperature — AxeOS reports both the ASIC chip temperature and the voltage regulator (VRM) temperature. Make sure you are reading the right one. The VRM typically runs 10–20°C hotter than the ASIC.

Firmware Issues

AxeOS (ESP-Miner) firmware controls everything: ASIC communication, WiFi connectivity, the web dashboard, pool connections, and thermal management. Firmware updates can fix bugs and add features (see our Bitaxe Firmware Update Guide for the update process) — but they can also introduce new issues or brick the device if something goes wrong mid-flash.

OTA (Over-The-Air) Update Failed

You started a firmware update from the AxeOS web interface and it did not complete successfully.

1. Wait — OTA updates can take 60–120 seconds. If the progress bar stalled, wait at least 3 minutes before assuming failure. The ESP32 may still be writing firmware.
2. Do not power off — Cutting power during a firmware write is the most common cause of bricking. Let the device complete the process, even if the UI seems frozen.
3. Check the device status — After 3 minutes, try accessing the AxeOS dashboard. If it loads, the update may have succeeded but the UI did not refresh. Check the firmware version under System Info.
4. If the device does not respond — See Device Bricked / Boot Loop below for recovery procedures.

Device Bricked / Boot Loop

The Bitaxe will not boot normally — no WiFi, no web interface, possibly a rapidly cycling LED. This usually results from a failed firmware update but can also be caused by corrupted settings in flash memory.

The fix: USB serial flashing. This bypasses the normal boot process entirely and writes a fresh firmware image directly to the ESP32’s flash memory.

Method 1: Bitaxe Web Flasher (Easiest)

1. Open the Bitaxe Web Flasher in Google Chrome (other browsers may not support WebSerial).
2. Connect a USB-C cable between your Bitaxe and your computer.
3. Keep the barrel jack power connected as well — the Bitaxe needs both USB (for data) and barrel jack (for full power).
4. Enter bootloader mode:
   • Press and hold the Boot button (located on the left side near the fan/heatsink).
   • While still holding Boot, press and release the Reset button (located above Boot).
   • Release the Boot button after 2 seconds.
5. In the Web Flasher, click “Connect” and select the COM port that appears (e.g., COM3 on Windows, /dev/ttyACM0 on Linux).
6. Select the correct firmware image for your model and click “Flash”.
7. Wait for the process to complete. The console will show progress and eventually say “Leaving…” when done.
8. Power cycle the Bitaxe. It should boot with fresh firmware and create the setup WiFi hotspot.

Method 2: esptool.py (Advanced)

If the Web Flasher cannot detect your device, use the command-line esptool.py tool.

# Install esptool (requires Python)
pip install esptool

# Erase flash memory completely (enter bootloader mode first)
esptool.py --port COM3 erase_flash

# Flash the factory firmware image
esptool.py --port COM3 --baud 460800 write_flash 0x0 esp-miner-factory.bin

Replace COM3 with your actual COM port (check Device Manager on Windows, ls /dev/tty* on macOS/Linux). Replace esp-miner-factory.bin with the filename of the factory image you downloaded from the ESP-Miner releases page.

Settings Lost After Firmware Update

After a firmware update, your WiFi credentials, pool settings, or overclock values may be reset to defaults. This happens when:

• The update changes the NVS (Non-Volatile Storage) key format — new firmware may use different configuration keys.
• Flash memory was erased during recovery — the erase_flash command wipes everything including saved settings.

Prevention: Before any firmware update, take a screenshot of your AxeOS settings page. Note your pool URL, port, Bitcoin address, frequency, voltage, and fan settings. After the update, re-enter any settings that were cleared.

After the fact: If you lost settings, simply reconfigure through the AxeOS web interface. All settings are available in the Settings tab. Your pool-side statistics (shares, hashrate history) are stored by the pool, not the device — they are not affected by firmware changes.

Recovery Mode

When a Bitaxe boots after a firmware flash, it may enter a self-test mode. The screen will show “PASS” or “FAIL” for hardware diagnostics. This is usually informational:

• PASS — All hardware checks passed. The device proceeds to normal operation automatically, or press Reset to continue.
• FAIL — A hardware check did not pass. This does not necessarily mean something is broken — the self-test can be overly sensitive. Press the Boot or Reset button to bypass the test and enter configuration mode. If the device operates normally after bypassing, the failure was likely a false positive.

Hardware-Specific Troubleshooting

While most troubleshooting applies across all Bitaxe models, each variant has unique characteristics that create model-specific issues.

Bitaxe Supra / Ultra / Gamma (Single-Chip, 5V)

These are the standard single-ASIC-chip Bitaxe models, all powered by a 5V barrel jack.

• BM1366 (Ultra) — Mature and stable. The BM1366 is the most battle-tested Bitaxe chip. It recovers from soft restarts reliably and has the fewest firmware compatibility issues. If you have persistent problems on an Ultra, the issue is almost certainly power delivery, WiFi, or pool configuration — not the chip itself.
• BM1368 (Supra) — Slightly higher performance, same reliability. The BM1368 behaves similarly to the BM1366 but at higher efficiency. Same troubleshooting applies. The Supra draws slightly more power at stock settings — make sure your PSU has adequate headroom.
• BM1370 (Gamma) — Highest performance, tightest tolerances. The BM1370 is the most powerful single-chip Bitaxe, but it is also the most demanding:
  • Power sensitivity — The Gamma’s VIN range is extremely narrow (4.8V–5.3V). PSUs that work fine with the Ultra or Supra may trigger power faults on the Gamma. Invest in a quality, regulated 5V PSU.
  • Warm boot issues — The BM1370 can sometimes fail to start hashing after a warm restart (Reset button or software restart). If hashrate stays at zero after a reset, do a cold boot: unplug the barrel jack, wait 10 seconds, plug back in.
  • Higher thermal output — The Gamma generates more heat per chip. The stock heatsink and fan are adequate at stock frequencies in a cool room, but overclocking demands a heatsink upgrade.
  • Voltage regulator faults — The TPS546 regulator on some Gamma boards can enter a fault state that persists through soft restarts. Only a full power disconnect clears it.

Bitaxe Hex (Multi-Chip, 12V)

The Hex uses six ASIC chips on a single board, running at 12V via XT30 connector. This creates unique challenges.

• 12V power supply requirements — The Hex draws significantly more power than single-chip models (60–90W depending on variant and overclock). Use a quality 12V PSU rated for at least 8A (96W). ATX power supplies work but watch for voltage stability under load.
• XT30 connector — The XT30 is a friction-fit connector. Make sure it is fully seated. A half-inserted XT30 can cause arcing, intermittent power, and damaged connectors. Push it in until you feel it click firmly.
• Multi-chip coordination — If one of the six ASIC chips fails to initialize, it can affect the reported hashrate of the entire board. Check AxeOS System Info for per-chip status if available in your firmware version. One dead chip means roughly 1/6 hashrate loss.
• Thermal challenges — Six chips generate six times the heat. The Hex requires proper fan cooling and should not be operated without active airflow. If temperatures are spiking, ensure the fan is spinning at an adequate speed and consider a custom heatsink solution.
• Firmware compatibility — Some Hex variants (e.g., Supra Hex by TCH) use specialized firmware that is incompatible with standard AxeOS/OSMU builds. Flashing the wrong firmware onto a Hex can cause system failures or hardware damage. Always verify you are using the firmware build specifically designed for your Hex variant.

Bitaxe GT (Dual-Chip, 12V)

The GT runs two BM1370 chips at 12V, delivering approximately 2.0–2.4 TH/s. It sits between the single-chip models and the Hex in terms of complexity.

• Higher thermal load — Two BM1370 chips produce substantial heat. The GT’s cooling solution must handle double the thermal output of a Gamma. Ensure the fan is working and at adequate speed. Upgrading the heatsink is recommended for overclocking.
• Power stability — The GT needs a stable 12V supply. Voltage fluctuations that a single-chip device might tolerate can cause both chips to fault simultaneously on the GT. Use a quality 12V regulated PSU.
• XT30 connector — Same as the Hex: push the connector in firmly until it clicks. A loose XT30 under load is a fire risk.
• Dual-chip initialization — If one chip initializes but the other does not, you will see approximately half the expected hashrate. Check AxeOS for per-chip diagnostics. A cold boot usually resolves initialization failures.

LED Status Codes

The LED on your Bitaxe communicates device status at a glance. The exact LED behavior can vary slightly between hardware revisions and firmware versions, but the general patterns are consistent.

On models with an OLED/LCD display, the screen provides much more detailed status information than the LED alone. If your display is working, the information shown there supersedes LED pattern interpretation.

Serial Console Debugging (Advanced)

When the web interface is inaccessible and LED patterns are inconclusive, the serial console gives you raw boot logs and error messages directly from the ESP32. This is the most powerful diagnostic tool available.

What You Need

• A USB-C cable (data-capable — some cheap cables are charge-only and will not work)
• A computer with a serial terminal program:
  • Windows: PuTTY, Tera Term, or the built-in Serial Monitor in Arduino IDE
  • macOS: screen command or CoolTerm
  • Linux: minicom, screen, or picocom
• USB-to-serial drivers (usually auto-installed, but may need manual installation on older Windows versions)

Connecting to the Serial Console

1. Connect USB-C — Plug the USB-C cable into the Bitaxe and your computer. The barrel jack should remain connected for full power.
2. Identify the COM port — On Windows, open Device Manager and look under “Ports (COM & LPT)” for a new entry (e.g., “USB Serial Device (COM3)”). On macOS/Linux, run ls /dev/tty* and look for a new device (e.g., /dev/ttyACM0).
3. Open your serial terminal — Connect to the identified port with these settings:
   • Baud rate: 115200
   • Data bits: 8
   • Stop bits: 1
   • Parity: None
   • Flow control: None
4. Power cycle the Bitaxe — Disconnect and reconnect the barrel jack to trigger a fresh boot. The serial console will display the full boot sequence including hardware initialization, WiFi connection attempts, ASIC detection, and any errors.

# Linux — connect to serial console
sudo minicom -D /dev/ttyACM0 -b 115200

# macOS — connect to serial console
screen /dev/tty.usbmodem* 115200

What to Look For in Serial Output

• ASIC init failed — The ESP32 cannot communicate with the ASIC chip. Check for physical damage, wrong firmware, or power delivery issues.
• WiFi: disconnected or No AP found — WiFi credentials are wrong or the network is not in range. Reconfigure via the setup hotspot.
• Stratum connection failed — Cannot reach the pool. Check internet connectivity, pool URL, and port.
• Power fault — Voltage regulator issue. See Power Fault Detected.
• Guru Meditation Error or panic — Firmware crash. Note the error details and report them if filing a bug. Recovery requires reflashing.
• i2c_master_transmit_receive: handle not initialized — I2C bus communication error, often related to the TPS546 voltage regulator or display. Usually resolved by a cold power cycle or firmware update.

When seeking help on GitHub or community forums, copy the full serial output from boot to the point of failure. This log is the single most useful diagnostic artifact for any troubleshooting discussion.

AxeOS Built-In Diagnostic Tools

The AxeOS web dashboard provides several diagnostic features. Knowing where to find them saves time.

Dashboard Monitoring

The main AxeOS dashboard (accessible at http://<bitaxe-ip>/) shows real-time data:

• Hashrate — Current and average, with a historical graph
• Temperature — ASIC chip temperature and VRM temperature
• Fan speed — Current RPM or percentage
• Pool status — Connected/disconnected, shares accepted/rejected
• Power draw — Input voltage and wattage
• Best difficulty — The highest difficulty share your device has found (persisted across reboots)
• Uptime — How long since last reboot

API Endpoints for Diagnostics

AxeOS exposes a REST API for programmatic access. Useful diagnostic endpoints:

# Get full system info (JSON)
curl http://<bitaxe-ip>/api/system/info

# Restart the device
curl http://<bitaxe-ip>/api/system/restart

# Get current settings
curl http://<bitaxe-ip>/api/system/settings

The /api/system/info endpoint returns a JSON payload with ASIC model, firmware version, WiFi RSSI (signal strength), temperatures, hashrate, power consumption, and more. This is useful for monitoring multiple Bitaxe devices from a script or dashboard.

When to Contact D-Central Support

You have worked through every troubleshooting step in this guide. You have power cycled. You have reflashed firmware. You have checked your PSU with a multimeter. The device still is not cooperating. That is when you call in the team that helped build this ecosystem.

Contact D-Central if:

• The ASIC chip is not detected after firmware reflash and hardware inspection
• You see visible damage: burnt components, cracked solder joints, damaged connectors
• The voltage regulator fault persists across multiple quality PSUs
• The device was exposed to wrong voltage (12V on a 5V device) and no longer functions
• Temperature readings are erratic and power cycling does not resolve them
• The PCB shows signs of physical stress: bent board, loose components, corrosion

You can also reach us at 1-855-753-9997 or through our contact page. For fastest response, include:

• Your Bitaxe model and hardware revision
• The firmware version (shown in AxeOS System Info)
• A description of the problem and what troubleshooting steps you have already tried
• Serial console output if available (see Serial Console Debugging)
• Photos of any visible damage

Frequently Asked Questions

Why D-Central

D-Central Technologies has been building, hacking, and repairing Bitcoin mining hardware since 2016. We were among the first to recognize the Bitaxe for what it truly represents: the decentralization of mining hardware itself. Open-source silicon. Open-source firmware. Mining power in the hands of individuals, not institutions — the core philosophy behind solo Bitcoin mining.

We created the original Bitaxe Mesh Stand — the first commercially manufactured accessory for the Bitaxe ecosystem. We developed custom heatsinks optimized for both standard Bitaxe and Hex models. We stock every Bitaxe variant alongside the full open-source miner lineup: NerdAxe, NerdNOS, Nerdminer, NerdQAxe, and more. Our team has hands-on experience with every revision of every model, and we bring that knowledge to every repair, every support ticket, and every guide we publish.

When you buy a Bitaxe from D-Central, you are not buying from a faceless dropshipper. You are buying from a team of Bitcoin Mining Hackers who understand this hardware at the component level — because we helped shape this ecosystem from day one.

Every hash counts.