Resolve Issues Connecting to the Miner and Finding its IP Address

Your miner is plugged in, powered up, and the fans are screaming — but your browser just stares back at you with a blank page where the web interface should be. You cannot find the miner on your network, you have no idea what IP address it grabbed, and every minute offline is hashing power wasted. Sound familiar?

This is one of the most common frustrations in Bitcoin mining, and it hits everyone from first-time home miners unboxing a Bitaxe to operators running racks of Antminers. The good news: almost every connectivity and IP detection problem has a straightforward fix once you understand what is actually happening at the network level.

This guide walks you through every method for finding your miner’s IP address, diagnosing why you cannot connect, and hardening your network so the problem never comes back. No fluff, no filler — just the technical playbook we use in our own repair lab every single day.

Why Connectivity Is Non-Negotiable in Mining

A Bitcoin miner that cannot reach the network is just an expensive space heater without the upside. With the global hashrate now exceeding 800 EH/s and the block reward sitting at 3.125 BTC post-halving, every second your machine spends offline is a second someone else is earning shares you are not.

What Happens When Your Miner Loses Connection

When your miner drops off the network, the consequences cascade fast:

• Pool shares stop submitting. Your ASIC keeps hashing locally, but those shares never reach the pool. For solo miners, a disconnected machine cannot submit a valid block even if it finds one.
• Stale shares accumulate. If the connection is intermittent rather than fully down, shares arrive late and get rejected. Your effective hashrate plummets while your power bill stays the same.
• Monitoring goes blind. Tools like Foreman, Hive OS, or your pool dashboard report the miner as offline. You lose visibility into temperatures, fan speeds, and error rates — the exact data you need to prevent hardware failures.
• Firmware updates stall. Remote firmware updates require a stable connection. An interrupted flash can leave your miner in an unrecoverable state.

The takeaway is simple: a reliable network connection is as critical as your power supply. Treat it accordingly.

The Role of IP Addresses in Mining Operations

Every device on your local network — your laptop, your phone, your ASIC miner — receives an IP address. This address is how you access the miner’s web interface to configure pools, adjust fan curves, flash firmware, and monitor performance.

For a single miner at home, IP management is straightforward. For a setup with five, ten, or fifty machines, it becomes an operational discipline. Lose track of which IP belongs to which miner and you are flying blind.

There are two ways a miner gets its IP address:

• DHCP (Dynamic): Your router assigns an IP automatically. The miner requests an address on boot, and the router hands one out from its available pool. This is the default on virtually every miner and router.
• Static IP: You manually assign a fixed address either in the miner’s web interface or via a DHCP reservation on your router. The address never changes, making it predictable and reliable.

Most connectivity headaches trace back to DHCP — the miner’s IP changed after a reboot, the lease expired, or two devices got the same address. We will cover how to prevent all of these scenarios below.

Finding Your Miner’s IP Address: Five Proven Methods

Before you can fix a connection problem, you need to find your miner on the network. Here are five methods, ordered from simplest to most powerful.

Method 1: Check Your Router’s DHCP Client List

This is the fastest approach and works for any miner brand.

1. Open a browser and navigate to your router’s admin page. Common addresses are 192.168.1.1, 192.168.0.1, or 10.0.0.1. Check the label on your router if you are unsure.
2. Log in with your admin credentials. If you never changed them, the defaults are usually printed on the router itself.
3. Look for a section labeled Connected Devices, DHCP Client List, LAN Clients, or Attached Devices.
4. Scan the list for your miner. Antminers typically show up as “Antminer” or their MAC address prefix (Bitmain uses C4:XX and D4:XX prefixes). Bitaxe devices appear as “ESP-XXXXXX” or “bitaxe” depending on firmware version. Whatsminers show as “WhatsMiner” or “MicroBT.”
5. Note the IP address listed next to the device.

Pro tip: If your miner does not appear in the list, it either failed to get a DHCP lease (network cable issue, wrong VLAN) or it is not powered on properly. Check the physical layer first.

Method 2: Use a Network Scanner Tool

Network scanners probe every IP on your subnet and report what is alive. They are indispensable when your router interface is clunky or when you are managing multiple miners.

Recommended tools:

• Advanced IP Scanner (Windows) — Free, fast, shows hostnames and MAC addresses.
• Angry IP Scanner (Windows, Mac, Linux) — Open-source, cross-platform, lightweight.
• Fing (iOS, Android) — Scan from your phone. Great for quick checks on the workshop floor.
• nmap (command line) — The gold standard for network discovery. Run nmap -sn 192.168.1.0/24 to ping-sweep your entire subnet in seconds.

When scanning, look for devices with open port 80 (HTTP) or 443 (HTTPS) — those are your miners’ web interfaces. Antminers also open port 4028 for the cgminer API.

Method 3: Manufacturer-Specific Discovery Tools

Most ASIC manufacturers provide their own tools because they know this is a pain point:

• Bitmain IP Reporter: Download from Bitmain’s support page. Hold the IP Report button on your Antminer (the small button near the Ethernet port) for 5 seconds until you hear a beep, then release. The IP Reporter software on your PC will display the miner’s IP address. This works even if the miner’s web interface is inaccessible.
• WhatsMiner Tool: MicroBT provides a dedicated Windows tool that auto-discovers all Whatsminer devices on the LAN. It also supports batch configuration — useful for operations with multiple units.
• Bitaxe / AxeOS: Bitaxe devices running AxeOS broadcast via mDNS. On most networks, you can access your Bitaxe at http://bitaxe.local directly in your browser. If mDNS is not working, use one of the scanner tools above. For deeper AxeOS configuration, see our AxeOS Complete Guide.

Method 4: Command-Line Discovery (ARP Table)

If you prefer the terminal — and if you are reading D-Central content, you probably do — your operating system already knows which devices are on the network.

Windows (PowerShell or CMD):

arp -a

Linux / macOS:

arp -a
# or for a cleaner view:
ip neigh show

This dumps every MAC-to-IP mapping your machine has cached. Cross-reference the MAC address prefixes mentioned above to identify your miners. If the ARP table is stale, ping the broadcast address first to refresh it:

# Linux/macOS
ping -c 3 192.168.1.255

# Windows
ping 192.168.1.255

Method 5: Serial Console / Direct Connection

When nothing else works — the miner has no IP, it will not respond on the network, and the LEDs are doing something suspicious — go direct.

1. Connect your PC directly to the miner with an Ethernet cable (no router in between). Set your PC’s IP to a static address in the 192.168.1.x range (e.g., 192.168.1.100) and then try the miner’s default IP. For Antminers, this is typically 192.168.1.99 after a factory reset.
2. Serial console (advanced): Some miners expose a UART serial port on their control board. Connect with a USB-to-UART adapter, open a terminal at 115200 baud, and you can access the Linux shell directly. This bypasses the network entirely and is the last resort for bricked or badly misconfigured devices.

If none of these methods reveal your miner, the issue is likely hardware — a dead Ethernet port, a failed control board, or a corrupt firmware image. That is where professional ASIC repair comes in.

Common Connectivity Problems and How to Fix Them

Now that you can find your miner, let us tackle the most frequent issues that break the connection in the first place.

Problem 1: Miner Gets a Different IP After Every Reboot

Cause: Your router’s DHCP server assigns IPs dynamically. When the miner reboots, it may get a different address.

Fix — DHCP Reservation: Log into your router, find the DHCP reservation or “address reservation” setting, and bind your miner’s MAC address to a specific IP. The miner will always receive that same address from DHCP, even after reboots, without needing to configure a static IP on the miner itself.

This is the single best practice for any mining operation, regardless of size. Do it for every miner on day one.

Problem 2: IP Address Conflict (Two Devices, Same IP)

Cause: Either you manually set the same static IP on two devices, or your DHCP pool overlaps with a static range you configured.

Symptoms: One or both devices drop on and off the network intermittently. The web interface loads sometimes but not others.

Fix:

1. Run a network scan to identify the conflict — look for two different MAC addresses associated with the same IP.
2. Change one device to a different IP, or better yet, switch both to DHCP reservations.
3. If you use static IPs, keep them outside your router’s DHCP range. For example, if your DHCP pool is 192.168.1.100–192.168.1.200, assign statics in the 192.168.1.2–192.168.1.99 range.

Problem 3: Miner Shows in Router But Web Interface Will Not Load

Cause: The miner has an IP but its web server is not responding. This can be a hung cgminer/bmminer process, a firmware issue, or the miner is still booting.

Fix:

1. Wait 2-3 minutes. ASICs take time to boot fully, especially after a firmware flash. The web interface is one of the last services to start.
2. Try a different browser or clear your browser cache. Some miners serve pages that trip up browser caching.
3. Ping the miner: Open a terminal and run ping [miner-IP]. If it replies, the network is fine and the issue is the web service. If it does not reply, the network layer is broken.
4. Power cycle the miner. Unplug, wait 30 seconds, plug back in. A surprising number of issues resolve with a clean reboot.
5. If the web interface still will not load after a power cycle, the firmware may need reflashing. See our SD Card Firmware Recovery Guide for Antminers, or the AxeOS web flasher for Bitaxe devices.

Problem 4: Ethernet Cable and Port Issues

This is more common than most people think, especially in workshop or garage environments where cables get stepped on, kinked, or exposed to heat.

Diagnostic steps:

• Check the Ethernet port LEDs on the miner. Most ASICs have a green link light and an amber activity light. No lights = no link.
• Swap the Ethernet cable with a known-good one. Cat5e or Cat6 is sufficient for mining — you do not need Cat8.
• Try a different port on your router or switch.
• If you are using a long cable run (over 50 meters), signal degradation becomes a factor. Use a shorter cable for testing or add a network switch as a repeater.

If the Ethernet port on the miner itself is dead (no link light with multiple cables and switch ports), the control board likely has a failed Ethernet transceiver. This is a repairable issue — the component can be reflowed or replaced at the board level.

Problem 5: Firewall or Network Isolation Blocking Access

Cause: Some routers have AP isolation, client isolation, or firewall rules that prevent devices on the same network from talking to each other.

Fix:

• Disable AP isolation or client isolation in your router’s wireless settings (this mainly affects Wi-Fi, but some routers apply it to wired clients too).
• Check your router’s firewall rules for anything blocking traffic on port 80 or 4028 within the LAN.
• If you have VLANs configured, make sure your management device (laptop) and your miners are on the same VLAN or that inter-VLAN routing is enabled.

For a deeper dive into network-level miner troubleshooting, see our dedicated Network Error Fix guide.

Hardening Your Mining Network

Finding and fixing connectivity problems is reactive. Let us talk about how to set up your network so these problems rarely happen in the first place.

Assign DHCP Reservations for Every Miner

We already covered this above, but it bears repeating because it eliminates the single most common category of connectivity issues. Every miner should have a reserved IP address tied to its MAC address in your router’s DHCP settings. Write these down in a spreadsheet or label the miners physically. Documentation is not optional when you are managing hardware.

Use Wired Connections — Always

Wi-Fi has no place in a serious mining operation. Even small open-source miners like the Bitaxe, which connect via Wi-Fi by design, should be on a stable, interference-free network. For ASIC miners with Ethernet ports, there is no excuse for Wi-Fi bridges or powerline adapters. Run proper Ethernet cables.

If your miners are far from your router, add a dedicated network switch. A basic unmanaged gigabit switch costs less than an hour of mining downtime. For larger operations, consider managed switches with VLAN support to segment mining traffic from household traffic.

Separate Your Mining Network

If you are running more than a handful of miners, put them on their own subnet or VLAN. This has three benefits:

1. Reduced broadcast traffic. ASIC miners can be chatty on the network. Isolating them keeps your household devices responsive.
2. Easier IP management. A dedicated 192.168.2.x subnet for miners keeps everything organized.
3. Improved security. If a miner’s firmware is compromised, network segmentation limits the blast radius.

For detailed guidance on choosing the right network switch for your operation, we have a dedicated guide.

Change Default Passwords Immediately

Every Antminer ships with the username root and password root. Every single one. If your miners are accessible on your LAN — and they are — anyone on that network can access the web interface, change your pool settings, redirect your hashrate, or flash malicious firmware.

Change the admin password on every miner as part of your initial setup. This takes 30 seconds per device and is basic operational security.

Keep Firmware Updated

Firmware updates fix bugs, patch security vulnerabilities, and sometimes improve hashrate or efficiency. Running outdated firmware is running known-vulnerable software on a device that handles real economic value.

Check for updates monthly. For Antminers, our Antminer Firmware Update Guide covers stock, Braiins OS+, Vnish, and LuxOS across every model. For Bitaxe, AxeOS updates ship through the web interface or the ESP web flasher.

Critical warning: Never flash firmware from unofficial sources. Malicious firmware can redirect your hashrate to an attacker’s pool or brick the device entirely. Only use manufacturer-provided firmware or well-known, audited third-party options like Braiins OS+, Vnish, or LuxOS.

Monitor Your Miners Proactively

Do not wait for something to break. Set up monitoring that alerts you when a miner goes offline, when temperatures spike, or when hashrate drops below a threshold.

Options range from simple to sophisticated:

• Pool dashboard: Most pools show per-worker status. If a worker goes offline, the pool will often send an email alert.
• Foreman: A purpose-built ASIC monitoring platform with dashboards, alerts, and fleet management.
• Custom scripts: A cron job that pings each miner’s IP and sends an alert if it does not respond. This is the Mining Hacker way — five lines of bash can save hours of downtime.

Resetting Your Miner to Factory Defaults

When all else fails — the web interface is unresponsive, the IP is unknown, firmware is corrupted — a factory reset brings the miner back to a known-good state.

Hardware Reset (Physical Button)

1. Locate the reset button on your miner. On Antminers, it is a small recessed button near the Ethernet port or power connector. You will need a paperclip or SIM ejector tool.
2. With the miner powered on, press and hold the reset button for 5-10 seconds (varies by model — check your manual).
3. The miner will reboot and restore factory settings, including the default IP address and pool configuration.
4. After the reset, reconnect to the miner using its default IP (usually 192.168.1.99 for Antminers) and reconfigure your pool, worker name, and network settings.

SD Card Recovery

If the reset button does not work or the firmware is too corrupted for a soft reset, SD card recovery is the nuclear option. Flash the manufacturer’s recovery image to a micro-SD card, insert it into the miner’s control board, and power on. The miner boots from the card, wipes the internal firmware, and installs a clean image.

This process varies by model and manufacturer. We maintain step-by-step instructions in our SD Card Firmware Recovery Guide.

Special Considerations for Open-Source Miners

The Bitaxe, NerdAxe, NerdQAxe, and other open-source mining devices have their own connectivity quirks that differ from traditional ASICs.

Wi-Fi Configuration on Bitaxe and NerdAxe

Unlike Antminers and Whatsminers that use Ethernet, the Bitaxe and NerdAxe families connect exclusively via Wi-Fi. During initial setup, the device creates its own Wi-Fi access point (AP mode). You connect to this AP from your phone or laptop, enter your home Wi-Fi credentials, and the device switches to station mode and joins your network.

Common issues:

• 5 GHz networks not supported. The ESP32 chip in most open-source miners only supports 2.4 GHz Wi-Fi. If your router uses a combined SSID for both bands, the miner may struggle to connect. Create a dedicated 2.4 GHz SSID or ensure band steering does not push the device to 5 GHz.
• Special characters in SSID or password. Avoid special characters (especially apostrophes, quotes, and backslashes) in your Wi-Fi name and password. The ESP32’s HTTP configuration page does not always escape these correctly.
• Weak signal. The PCB antenna on a Bitaxe has limited range. If the miner is in a garage or basement far from your router, consider adding a Wi-Fi access point closer to the device.
• AP mode not appearing. If you cannot see the Bitaxe’s AP after a fresh flash, hold the boot button while powering on to force AP mode. Consult the Bitaxe Troubleshooting Guide for model-specific instructions.

mDNS and .local Addresses

AxeOS supports mDNS, which means you can typically reach your Bitaxe at http://bitaxe.local without knowing the IP. This works well on macOS and Linux out of the box. On Windows, you may need Apple’s Bonjour service installed (it comes bundled with iTunes) for .local resolution to work.

If mDNS is unreliable on your network, fall back to IP-based access using one of the scanner methods above.

When It Is a Hardware Problem, Not a Network Problem

Sometimes you have done everything right on the network side and the miner still will not connect. At that point, the problem is likely hardware:

• Dead Ethernet port: The RJ45 jack or the Ethernet transceiver IC on the control board has failed. Common on older Antminer S9 and S17 series after years of operation.
• Corrupted NAND/eMMC: The control board’s internal storage is corrupted beyond what a firmware reflash can fix. The storage chip needs replacement.
• Failed control board: The Zynq FPGA, RAM, or voltage regulators on the control board have failed. The board needs component-level diagnosis and repair.
• Power delivery issues: If the control board is not getting stable 12V (or 3.3V for logic), it may partially boot but fail to initialize the network stack.

These are all repairable at the component level. At D-Central, we handle control board repairs daily — from reflowing Ethernet transceivers to replacing NAND chips and reprogramming firmware. If your miner is showing hardware-level network failures, reach out to our repair team before writing off the hardware.

Quick Reference: Default IPs and Discovery Methods by Manufacturer

Frequently Asked Questions