Setting a Static IP Address on ANTMINER: What You Need to Know

Setting a static IP address on an Antminer locks the miner to one fixed address on your LAN so it never wanders when the router reboots or its DHCP lease expires. That matters because your monitoring, your pool watchdog, and your SSH/API scripts all depend on the miner living at a predictable address. This guide covers every stock-firmware Antminer generation — the web UI layout is nearly identical across all of them.

Two ways to pin an address — pick one, not both

There are two clean approaches. Do not combine them or you will create an address conflict:

• DHCP reservation (recommended): Leave the miner on DHCP and bind its MAC address to a fixed IP in your router. Central, survives a factory reset, and impossible to fat-finger a subnet mask.
• Static IP on the miner itself: Configure the address in the miner’s own network page, described below. Use this when you don’t control the router (shared/hosted networks) or want the miner to hold its address regardless of DHCP server state.

Tools you’ll need

• The miner powered on and cabled to the same switch/LAN as your computer.
• A way to find the miner’s current IP: Bitmain’s built-in IP Reporter (press the IP-Report button on the control board and it broadcasts its IP + MAC to the IP Reporter utility), or a subnet scanner such as BTC Tools / Advanced IP Scanner.
• Default stock login credentials — Antminer ships as root / root. If those fail, the unit has been re-secured and you’ll need the owner’s password.
• Three addresses written down before you start: the static IP, the gateway, and the subnet mask (see planning step).

Plan the address first (this is where most people break their network)

1. Find your subnet. Check any working device on the LAN. A home network is almost always 192.168.0.x or 192.168.1.x with a subnet mask of 255.255.255.0 (a /24).
2. Identify the gateway. This is your router’s LAN address — typically 192.168.1.1 or 192.168.0.1. On Windows run ipconfig and read “Default Gateway”; on macOS/Linux run ip route or netstat -rn.
3. Choose an IP outside the DHCP pool. Routers hand out a range (e.g. .100–.200). Pick a static address outside that range — 192.168.1.50 is safer than 192.168.1.150 — so the router never leases the same address to another device. Assigning a static IP that lives inside the DHCP pool is the #1 cause of “the miner drops off the network every few days.”
4. Set DNS. Point it at your gateway (the router will forward), or a public resolver like 1.1.1.1 / 8.8.8.8. DNS only matters for outbound lookups (firmware update servers, pool hostnames); a bad DNS entry won’t stop hashing to an IP-based pool but will break hostname-based pools.

Set the static IP in the miner web UI

1. Open the dashboard. Browse to http://<current-miner-IP> and log in with your credentials.
2. Go to Network settings. Open the Network tab (on some builds it’s System → Network or Configuration → Network).
3. Change Protocol to Static. In the Protocol drop-down, switch from DHCP to Static. The address fields become editable.
4. Enter your details. Type the static IP address, Netmask (255.255.255.0 for a /24), Gateway, and DNS exactly as planned. Double-check every octet — a transposed digit here is the difference between a reachable miner and a service call.
5. Save & Apply. Click Save & Apply. The network interface restarts and the miner will drop off its old address immediately.

Important: the moment you apply, the miner is only reachable at the NEW address. If you made a mistake in the gateway or mask, the web UI at the old IP will appear “dead.” Don’t panic and don’t power-cycle repeatedly — go straight to the recovery step.

Confirm it worked

1. Browse to the new address: http://192.168.1.50 (your chosen IP). The dashboard should load.
2. From a terminal, ping 192.168.1.50 — you want steady replies with no timeouts.
3. Reboot the miner (Save & Apply usually does this) and confirm it comes back up at the same address. A real static assignment survives a reboot; a stale DHCP lease does not.
4. Check the hashboards reconnected to the pool from the Miner Status / Pools page — a network change should never affect hashrate, so a sudden drop means something else needs attention.

When it goes wrong — recovery

• Miner unreachable after applying: Press the IP-Report button on the control board and read the address back with the IP Reporter tool, or re-scan the subnet. The miner will tell you where it actually is.
• Wrong subnet entirely / no response: Hold the reset button on the control board for ~5 seconds. This restores factory network defaults (back to DHCP), letting you rediscover the miner and try again. Firmware and pool settings are retained.
• Two devices, same address: If another machine grabs the same IP you’ll see intermittent connectivity. Move the static IP outside the DHCP pool, or reserve it by MAC in the router instead.

Do you even need this?

Running one or two miners at home, DHCP is usually fine — the router keeps handing back the same address most of the time. Static addressing earns its keep once you’re managing several units, monitoring via API, or running remote scripts that must find each machine by a known address. If you go static, keep a simple map of IP → machine → MAC so future-you (or the next tech) isn’t guessing.

Related: Working through a full deployment or a fault? See the per-model Antminer repair manuals, look up any fault on the ASIC fault finder, brush up terms in the mining glossary, or if a board won’t come back online, start a repair with us.