Whatsminer – Cannot Access Web Interface After Reset

Wait 15-20 minutes before touching anything. The miner runs a userland rebuild after any factory reset — regenerating SSH keys, TLS certs, rebuilding miner-service state, enumerating chips. M30-class finishes in 8-12 minutes; M50S takes 12-15; M60S takes 15-20. Interrupting by power-cycling or pressing more buttons can push the board into recovery mode and turn a 15-minute wait into a 45-minute reflash. Verify the miner's kernel is alive by pinging its last-known IP — if ping answers, rebuild is in progress. Walk away and come back with coffee.

Open your router admin (typically `http://192.168.0.1` or `http://192.168.1.1`) and check DHCP leases. Look for a newly-leased device with a MAC prefix matching MicroBT ranges (often `A4:C1:38` or `D0:71:C4`) — or compare against the MAC printed on the miner's chassis sticker. Factory reset wipes any static IP and forces DHCP, so your old bookmark is dead — the new IP is wherever your router just leased. Note it, try `http://<new-ip>` in a browser.

Press and hold the `IPFOUND` button on the miner for 2 seconds. Button is on the control-board end, opposite `RESET`. On most firmware this broadcasts the current IP via a beep sequence (count beeps per digit) or a cascading LED flash; on M50/M60 hydro units with OLED displays it shows the IP directly. Cross-reference the reported IP against your router's lease table to sanity-check.

Clear your browser's HSTS cache for the old miner IP. If the miner previously served HTTPS, Chrome/Firefox may have cached a security policy that now refuses HTTP fallback — factory reset regenerates the TLS cert, breaking HSTS pinning. In Chrome, navigate to `chrome://net-internals/#hsts` → `Delete domain security policies` → enter the old IP. Retry the new IP after clearing. Catches about 5% of 'I can ping but the browser refuses' cases.

Try a different device on the same LAN (phone, tablet, another laptop). If the web UI loads from a second device but not your primary, you have a local DNS or HSTS or proxy problem, not a miner problem. On Windows: `ipconfig /flushdns`. On macOS: `sudo dscacheutil -flushcache`. On Linux: `sudo systemd-resolve --flush-caches`. Retry from the original machine.

Download WhatsminerTool V9.0.1+ from `support.whatsminer.com`. Launch, click `Detect IP` / `Scan`, let it sweep the LAN. The tool queries TCP port `4028` — the Whatsminer API — which stays open even when `nginx` is down. If the miner is alive and on your LAN it shows up within 30 seconds with MAC, IP, firmware version, hashrate. If it appears: use `Remote Ctrl → Restore Miner → DHCP` to force a fresh lease, or set a static IP directly from the tool.

Confirm the reset type from LED pattern. `red-green flicker 3s then steady green` = successful soft reset (IP/pool wiped, firmware kept). `amber slow blink` = stuck in firmware recovery mode (Tier 3). `red-green flicker then no LED` = control board boot failure (Tier 4). If you're in recovery mode and didn't mean to be, you long-pressed RESET — there's no way back to normal boot without flashing firmware via WhatsminerTool.

Test the API directly with `netcat`. From any Linux/macOS/WSL machine on the LAN: `echo '{"cmd":"status"}' | nc <miner-ip> 4028`. Healthy miner returns a JSON blob with hashrate, temps, firmware version. Recovery-mode miner returns JSON with only `recovery` fields. No response = kernel down or network layer dead — jump to Step 11. This one command tells you more than 10 minutes of web-UI-reload attempts.

Assign a static IP via WhatsminerTool. If the miner appears in tool scan but DHCP keeps changing the IP on every reboot, set static from `Remote Ctrl → Config → Network`. Choose an IP outside your router's DHCP pool (e.g. DHCP pool `192.168.1.100-200` → set miner to `192.168.1.50`). Save, wait ~60s for reboot, verify. Static IPs survive every future reset and are the single highest-leverage move any Whatsminer operator can make.

Force a full `Restore Miner → Factory` via WhatsminerTool if the web UI still won't come up but the API responds. This path is cleaner than the physical RESET button because it goes through the miner-service daemon (not the bootloader) and waits for clean userland teardown before rebuilding. Takes 10-15 minutes. After completion, web UI should respond at the DHCP-assigned IP. Default credentials: `admin`/`admin` on most firmware; `root`/`root` on M60S post-`20240801`.

Flash firmware via WhatsminerTool's recovery mode. If `nmap` showed only port `4028` open, or the API returned a `recovery` JSON: download official firmware from `support.whatsminer.com` matching your exact sub-model (wrong firmware bricks the control board). In WhatsminerTool → `Firmware Upgrade` → browse to the `.bin` file → `Start Upgrade`. Push takes 20-30 minutes over TCP `4028`. Watch the progress indicator — if it stalls more than 5 minutes at one step, do not interrupt; aborted flashes leave the board in a worse state.

SSH as a last-resort diagnostic, if you set a password pre-reset. `ssh root@<miner-ip>` — default on M30-era was `root/root`, on M50+ typically `super/super`, but most modern builds have SSH disabled by default. If SSH is up: `cat /etc/config/network` for current IP config, `ps | grep nginx` to see if the web daemon started, `tail -f /var/log/syslog` to watch userland boot. Bench-tech territory — skip to Tier 4 if OpenWrt-style config is unfamiliar.

Manually force DHCP renewal via SSH or API if the miner is sitting on an old static-IP remnant. Over SSH: `killall udhcpc && udhcpc -i eth0 -n`. Over the API: send `{"cmd":"net_config","ip":"dhcp"}` via TCP `4028`. Forces a fresh DHCP lease. Wait 60 seconds, rescan. Useful when factory reset only partially wiped config — happens rarely when RESET was pressed during a firmware update cycle.

Rebuild from recovery partition via RESET long-press. Power off the miner. Hold RESET while powering on, keep holding ~30 seconds until LED pattern changes to steady amber. Triggers full reinstall from the recovery partition — different from factory reset which uses the main partition. Rebuild takes 20-25 minutes. Miner comes back on DHCP with default credentials. Use this when factory reset left the main partition corrupt (symptoms: web UI comes up briefly then dies, services crash-loop, dmesg full of rootfs errors). Wipes all pool config and any custom firmware.

Verify full recovery with a 30-minute burn-in. Log in, reconfigure pool URLs, worker name, password; set a static IP; verify hashrate climbs to nameplate within 15 minutes (M30S ~88 TH/s, M50S ~126 TH/s, M60S ~172 TH/s — check your exact sub-model); confirm temps within spec; confirm no hashboard errors under MinerTool's diagnostic tab. If anything looks off post-reset, that issue was already hiding pre-reset — the reset just exposed it.

Stop DIY if the control board won't answer ARP after a full recovery-mode flash, or if LEDs are stuck steady red with no network activity. That's test-fixture and chip-level territory — the SoC, eMMC, or power regulation on the control board has failed. Pack the control board alone (not the whole miner if you can avoid it) and book a D-Central Whatsminer repair slot at `https://d-central.tech/services/asic-repair/`. Include your symptom log, firmware version history, and reset sequences tried — saves us diagnostic time, saves you money.

What D-Central does at the bench: control-board diagnosis on a MicroBT reference jig, UART serial console to read bootloader output, eMMC re-flash via J-TAG when the normal firmware path fails, component-level repair on ARM SoC power rails, and if the board is truly dead, a swap from our salvaged-grade Whatsminer control-board inventory. Canadian shipping, 3-7 business day turnaround typical on control-board-only jobs. For rare full-miner cases, 7-12 business days.

Ship safely. Pack the control board in anti-static bag, double-boxed with ≥5 cm of foam on every side. If shipping the full miner is necessary, pack the hashboards similarly and use the original foam packaging if you still have it. Include a note with observed symptoms, firmware version, reset combinations tried, and your contact info. Good shipping paperwork + a clean symptom description shaves hours off diagnostic time and directly reduces your final invoice.