Whatsminer Error 2000 – No Pool Configured

Connect a laptop to the same LAN segment as the miner, open a browser, navigate to the miner's IP. WhatsminerTool's web UI loads on `http://<miner-ip>` on stock firmware. Default credentials on a fresh chassis are `admin` / `admin` — change them after first login. If you don't know the IP, scan the LAN with `nmap -sn 192.168.1.0/24` from a sibling machine, or check the router's DHCP lease list.

Navigate to `Configuration → Miner Configuration → Pool Configuration` (path varies slightly between BTMiner generations — on M20S/M21S it's `Network → Pool`; on M30S+ and newer, under the unified Configuration menu). Confirm all three pool slots show empty grey-placeholder text. This visual confirmation is the difference between `2000` (slots empty) and `2010` (slots filled but rejected).

Type a complete `Pool 0` entry: `stratum+tcp://<host>:<port>` URL, worker name in `wallet.workername` format, password (almost always literal `x`). Click `Save & Apply`, watch for the green confirmation banner. The miner does not need a reboot for the pool config to take effect on most BTMiner versions, but a reboot is safer and clears any lingering log spam.

Hard-refresh the Pool Configuration page (Ctrl-F5 or Cmd-Shift-R) and re-verify your URL persisted. A small subset of WhatsminerTool builds have a silent-save bug where the API accepts the form and returns success but doesn't commit to nvram. If the URL is gone after refresh, switch to the desktop WhatsminerTool app, or try a different browser with extensions disabled.

Pull the BTMiner log via `Status → Log` (or via SSH if enabled) and confirm `2000` is gone. A healthy log will show `mining.subscribe`, `mining.authorize`, `mining.notify` lines on a 30-60 second cadence. The `GHSavg` should climb from `0` toward nameplate within 5-15 minutes as the chip diff settles.

Configure all three pool slots with sensible failover. Primary in `Pool 0`, secondary in `Pool 1`, public-pool fallback (e.g. `solo.ckpool.org` or `public-pool.io`) in `Pool 2`. BTMiner iterates: `Pool 0` first, drop to `Pool 1` if handshake fails for ~60s, drop to `Pool 2` after another ~60s. Slots are independently editable — same wallet across all three with different worker labels works.

Use the per-pool credential format strictly. Antpool: `stratum+tcp://stratum.antpool.com:3333` with `<account>.<worker>`, password `x`. F2Pool: `stratum+tcp://btc.f2pool.com:3333` with `<f2pool-username>.<worker>`. ViaBTC: `stratum+tcp://btc.viabtc.com:3333`. Braiins: `stratum+tcp://stratum.braiins.com:3333`. Ocean: `stratum+tcp://mine.ocean.xyz:3334`. solo.ckpool: `stratum+tcp://solo.ckpool.org:3333` with `<bc1q...address>.<worker>`. Public Pool: `stratum+tcp://public-pool.io:21496`. Always verify port and host on the pool's official documentation before pasting.

Rotate the BTC payout address into a fresh receive address on a hardware wallet. Coldcard, BitBox02, Trezor, and Ledger all support derivation of fresh native segwit (`bc1q...`) or taproot (`bc1p...`) receive addresses. Some pools do not yet pay to taproot; check before using `bc1p...`.

Configure NTP time sync from `Configuration → System → Time` so the miner clock stays within 60s of UTC. BTMiner uses signed certificate stratum on a few pools (Braiins, ViaBTC), and a badly-skewed clock fails TLS validation, pushing the connection from `2000`-clean into `2020` handshake-fail territory.

If WhatsminerTool refuses to save pool config and reverts to empty after every save, you've hit the silent-save bug. Workarounds: switch browsers (Chrome → Firefox), disable all extensions and privacy plugins, ensure laptop and miner are on the same VLAN with no router-side proxy, and try the desktop WhatsminerTool app from `https://www.whatsminer.com/`. Last resort: SSH into the miner if enabled and edit pool config via BTMiner CLI.

Factory reset via the recessed button on the control board. Power off, locate the recessed reset button (adjacent to the Ethernet port on most chassis, accessed through a small hole). Hold for ≥5 seconds while powering on. The control board LED blinks fast-red during reset, then settles. Miner boots into first-boot state with a DHCP-assigned IP and empty pool config — re-discover via DHCP table or `nmap`, then re-provision.

Reflash the latest signed BTMiner firmware for your specific chassis model. Pull firmware from MicroBT's official portal (`https://www.whatsminer.com/`) — never from third-party mirrors, which historically have hosted re-signed botware variants. Use WhatsminerTool's built-in `Firmware Upgrade`: upload the `.bin`, watch progress, wait for post-install reboot. Flash regenerates `nvram` from bundled defaults, clearing latent corruption from prior power-loss-during-save events.

Inspect `nvram` via SSH if SSH is enabled. Default access: `ssh root@<miner-ip>`, password is the WhatsminerTool admin password. Once in, `cat /etc/btminer/pools.conf` (path varies by firmware) shows raw pool config. Empty file = `2000`. Truncated/malformed file = silent corruption. Recovery: `rm` the file, factory reset, re-provision. Do not edit nvram files directly without a verified clean backup of the same firmware's pools.conf.

If the miner has been infected with botware (signature: hijacked pool config that re-appears after every factory reset, often pointing at a `1.2.3.4` IP-only stratum host or a domain ending in `.ru`/`.cn`/`.tk`), the recovery is: factory reset, immediately reflash latest signed firmware before reconnecting to the network, change the WhatsminerTool admin password, and place the miner on a network segment that blocks outbound connections to known malware C2 hosts.

Replace the RTC coin cell on the control board if NTP sync repeatedly resets to `1970-01-01` after every reboot. The cell is a `CR2032` on most BTMiner control boards — visually obvious, soldered or socketed. Replace with a fresh cell, re-sync NTP, verify time persists across a cold cycle. Stale RTC isn't itself a `2000` cause but can mask other failures by bouncing TLS-validation states across reboots.

Stop DIY when factory reset AND full firmware reflash both fail to clear `2000` — the pool-config layer is reading from a damaged `nvram` partition the firmware can't repair from userspace. Rare, almost always paired with other latent symptoms (random reboots, IP config also failing to persist, password changes not surviving). Ship the control board (or full chassis) to D-Central with a note describing symptoms and tried fixes.

D-Central bench process for `2000` escalations: control-board diagnosis under load on a test fixture, raw-`nvram` inspection via JTAG / SPI flasher, partition rewrite from a verified clean image for your specific BTMiner firmware version, post-repair 24-hour burn-in at nameplate. If the `nvram` chip itself is dead (extremely rare), it's a chip-replace. Turnaround 5-10 business days, Canada-wide shipping.

Ship safely. Anti-static bag the control board if removed; double-box with ≥5 cm foam on every side; include a written note with: chassis model, firmware version, observed behavior (`2000` persists after factory reset and reflash), what tier of fix you reached before stopping, your contact info. The note saves bench-time, which saves you money.