Skip to content
Small team, full backlog, zero orders dropped. Support replies are slower than we’d like. Read our status update → Zero orders dropped. Status → 📬 Check your spam folder — most of our replies land there. We do answer. Status update → 📬 Check your spam folder. Status →

ASIC Miner Default Passwords & SSH Logins by Control Board

The factory defaults and recovery paths for the ASIC miners D-Central sells and repairs — default network mode, how to find the miner’s IP, the stock web and SSH logins, the reset-button procedure, and the firmware-recovery method — in one machine-readable table, keyed by control-board generation, because that is what actually sets a miner’s defaults, not the model name on the box.

Most “default password for an Antminer” answers online are half-right. The famous root / root is the web-dashboard login on stock Bitmain firmware — but the SSH login on the S9-generation Zynq boards is actually root / admin (set by the SD installer’s passwd.txt), and the newest eMMC-only boards (S19 XP, S21, T21) ship miner / miner with the root account disabled entirely. This reference separates the web login from the SSH login, per board generation, and cites where each fact comes from.

How to use this

  • Find your board generation, not your model. Defaults and recovery are set by the control board’s SoC (Zynq, AM335x, Cvitek…), so a whole family of models shares one row.
  • Recovering your own miner? Start with the reset button, fall back to a microSD recovery, and only reach for UART / U-Boot on the eMMC-only boards where the SD trick no longer works. Each row links D-Central’s full step-by-step guide.
  • Then change the defaults. These are publicly-documented factory credentials, published here so you can recover your own hardware. The single most important thing you can do after recovering a miner is set a strong, unique dashboard password — a second-hand unit still carrying the previous owner’s pool and password is the number-one reason people land on this page.

Scope. This reference covers the six ASIC families D-Central sees most: Bitmain Antminer (by control-board generation, S9 through S21), MicroBT Whatsminer, Goldshell, IceRiver, Canaan Avalon and Volcminer. Every credential and procedure is sourced — to D-Central’s Bitcoin-mining reverse-engineering notes, a vetted on-site repair guide, or the manufacturer’s own documentation — and each row links its full step-by-step guide in our troubleshooting library.

Who closed the shell, and when — Bitmain’s own account

The version of this story that circulates is “Bitmain disabled SSH on everything after April 2019.” Bitmain published its own account of it, and the published account differs in three ways that change what you should actually check on the bench.

  • The gate is the firmware, not the manufacture date. Bitmain’s own wording is that SSH access is disabled after reloading the security firmware. A 2018 unit that was later updated has no shell; a 2019 unit that was never updated may still have one. A build date on a sticker is the wrong field to look at — read the firmware version off the miner’s status page instead.
  • The model list is wrong in both directions. Bitmain names S17, T17, S17 Pro, S15, T15, S9, S9i, S9j, L3+, DR5 and Z11. That adds T15, T17, S9i, S9j and DR5 to the list usually repeated, and it does not name the S17+.
  • The S19 is a different mechanism, not the same one. The S19 did not exist in April 2019 and was never in that article. Its restriction is described separately: Secure Boot switched on and the Root Authority function disabled. Treating it as “SSH was turned off” points you at the wrong recovery path.

Two other firmware vendors document the same window independently, and both say June, not April. Hiveon’s own README tells S9-family owners never to go newer than 10 June 2019 and Series-17 owners never to go newer than 1 December 2019. Awesome Miner’s install article gives June 2019 for S9/L3+/T9+, July 2019 for the L3+, December 2019 for S17/T17, and excludes the S17+ and T17+ outright. Three vendors, three independent documents, one window — and the widely-quoted April date is in none of them.

Two questions this table gets asked constantly

“Braiins Toolbox says my device is password protected.” That is the tool telling you the miner’s web password is not the factory default any more, which on a second-hand unit it usually is not. Braiins documents an override for exactly this: -p, --password <PASSWORD>, described in its own documentation as needed “if the default web password of the miner(s) is changed.” There is also a bos-toolbox unlock path for the S9 that requires the miner’s own web password — it is owner tooling for hardware you can already log into, not a way around a password you do not have. If you do not have the password, the route is the reset procedure in the row for your board generation, and then this table.

“Which of these are SSH logins and which are web logins?” They are different credentials on the same machine and conflating them is the single most common error in this category. The table above keeps them in separate columns for that reason. The one that catches people is the S9 generation: root / root is the web dashboard, and the SSH login is root / admin, set by the SD installer’s passwd.txt. Credit where it is due: that SD image is Braiins’, and it is what made the shell reachable on that generation in the first place.

Default passwords, SSH logins & recovery, by control-board generation

Each card is one control-board generation — a whole family of models shares its defaults and recovery path. Reviewed 2026-07-15.

Download CSV Download JSON REST API →

These are publicly-documented factory defaults, published so you can recover hardware you own. Change the dashboard and SSH credentials immediately after any recovery. Procedures vary by firmware and control-board revision; confirm against your unit and the linked guide before relying on them. Not a warranty or a guarantee against bricking.

Control board / generationModelsWeb loginSSH login
Bitmain — Zynq C5 (S9 generation)S9, S9i, S9j, T9+root / root …root / admin …
Bitmain — AM335x BeagleBone (Scrypt L-series)L3+, D3, A3root / root …root / admin …
Bitmain — Zynq (S17 / T17 generation)S17, S17+, S17 Pro, T17, T17+root / rootroot / admin …
Bitmain — S19 series (NAND control board)S19, S19 Pro, S19j, S19a, S19 Pro+ Hydroot / root …root / root · admin / admin …
Bitmain — Cvitek eMMC-only (S19 XP / S21 / T21 generation)S19 XP, S19 XP Hyd, S19k Pro, S19j Pro (Cvitek batches), S21, S21 Pro, T21, L7root / root …miner / miner …
MicroBT — Whatsminer (M2x / M3x / M5x / M6x)M20S, M21S, M30S, M30S+, M31S, M50, M53, M60 (and siblings)admin / admin · super / super …Managed via the web dashboard / btminer API; SSH login varies by firmwar…
Goldshell — Goldshell (BOX-series + KD / LT / CK-series)KD-BOX, Mini-DOGE, HS-BOX, ST-BOX, CK-BOX, KA-BOX, KD5, KD6, LT5, LT6, CK6, KD-MAXadmin / 123456789 …Not the documented field path — recover via the web dashboard or the Zon…
IceRiver — IceRiver KS-seriesKS0, KS0 Pro, KS0 Ultra, KS1, KS2, KS3, KS3L, KS3M, KS5, KS5L, KS5MA model-specific default printed on the chassis sticker / in the user ma…Not the documented field path — recover via the web UI or SD recovery.
Canaan — AvalonMiner (Avalon A-series)AvalonMiner 1066, 1066 Pro, 1166 Pro, 1246, 1366, 1466, 1566, Nano 3 / 3Sroot / rootManaged via the web UI / cgminer API.
Volcminer — Volcminer D1-series (Scrypt / LTC)D1, D1 Lite, D1 Mini, D1 Mini Pre, D1 Hydroroot / ltc@dog …SSH may be locked or use different credentials — use the web dashboard.

Table cells are trimmed to the credential pair. The full caveat for each one — and several of them matter, the S9-generation SSH login most of all — is in that generation's card below.

BitmainZynq C5 (S9 generation)

Models: S9, S9i, S9j, T9+  ·  Xilinx Zynq Z-7010 / Z-7007 (C5-class control board)

Default network
DHCP — no static default IP
Find the IP
Press the IP Report button on the control board (hold ~5 s, not a tap) and the miner broadcasts its IP to Bitmain's IP Reporter tool on the same subnet; or read your router's DHCP lease table / run nmap -sn.
Web dashboard login
root / root (stock web dashboard; HTTP digest realm "antMiner Configuration")
SSH login
root / admin (Bitmain SD-installer passwd.txt default) — NOT root/root; the famous root/root is the web-UI digest, not the SSH password
Reset (config wipe)
Reset button, config-wipe only: hard power-cycle, wait exactly 2 minutes (the button handler is only live 2–10 min after a cold boot), then hold Reset ~5 s. The firmware image stays; /config is cleared.
Firmware recovery
MicroSD (16 GB or smaller, FAT32, MBR, single partition) with Bitmain's SD-recovery bundle → reflashes NAND. The S9 family preserves MAC + config via a UBI "config" volume.
Watch out
The bundle's *.jffs2 files are actually UBI images (UBI# magic), not JFFS2. S9/S9i/S9j share one Zynq artifact set — only the rootfs differs per model.

Full step-by-step recovery guide →

BitmainAM335x BeagleBone (Scrypt L-series)

Models: L3+, D3, A3  ·  TI AM335x (BeagleBone-class control board)

Default network
DHCP — no static default IP
Find the IP
Router DHCP lease table, or Bitmain's IP Reporter tool. (Not all L-series units carry a dedicated IP-report button.)
Web dashboard login
root / root (HTTP digest realm "antMiner Configuration")
SSH login
root / admin (SD-installer passwd.txt default)
Reset (config wipe)
Reset button (same cold-boot window as the S9 family) — config wipe.
Firmware recovery
MicroSD SD-recovery bundle → reflashes NAND (the AM335x ROM probes four NAND offsets, so MLO is written to four partitions).
Watch out
⚠ On the L3+, recovery WIPES all user config (/config is cleared with rm -rf) — back up your pool settings first. Runs cgminer-ltc (Scrypt), not bmminer. A partial SD flash (missing an MLO copy) bricks the loader.

Full step-by-step recovery guide →

BitmainZynq (S17 / T17 generation)

Models: S17, S17+, S17 Pro, T17, T17+  ·  Xilinx Zynq (Zynq-7000 class control board)

Default network
DHCP — no static default IP
Find the IP
IP Report button (hold ~5 s) → IP Reporter tool; or router DHCP lease.
Web dashboard login
root / root (stock)
SSH login
root / admin on the sibling S9-family Zynq boards; the widely-cited root / root is the web-dashboard digest, not the SSH password. Confirm per unit — custom firmware (VNish/Braiins/LuxOS) sets its own.
Reset (config wipe)
Reset button — cold-boot, wait 2 min, hold ~5 s (valid 2–10 min window). Config wipe.
Firmware recovery
MicroSD (≤16 GB, FAT32/MBR) with the image for your EXACT control-board silkscreen revision → reflashes NAND. The S17/T17 family shares boot artifacts (one Zynq kernel across all four).
Watch out
Use the image for your exact silkscreen revision — a wrong-revision image bricks the board.

Full step-by-step recovery guide →

BitmainS19 series (NAND control board)

Models: S19, S19 Pro, S19j, S19a, S19 Pro+ Hyd  ·  NAND control board (silkscreen e.g. BHB42xxx / BHB56xxx / BHB68xxx)

Default network
DHCP — no static default IP
Find the IP
IP Report button (hold ~5 s) → IP Reporter tool; router DHCP lease. DCENT_OS additionally advertises the miner over mDNS.
Web dashboard login
root / root (stock) — newer boards ship a per-unit sticker password instead
SSH login
root / root (legacy) or admin / admin (newer firmware), or the per-unit sticker password
Reset (config wipe)
Reset button — hard power-cycle, wait 2 min, hold Reset ~5 s (valid 2–10 min window after a cold boot). Config wipe.
Firmware recovery
MicroSD (≤16 GB, FAT32, MBR) with the EXACT-revision Bitmain image → reflashes the control board. Wrong-revision flashing is the number-one operator-error brick at the bench.
Watch out
Match the firmware to the silkscreen revision (e.g. BHB68001 vs BHB68601) — an image from a different revision of the SAME model bricks the board.

Full step-by-step recovery guide →

BitmainCvitek eMMC-only (S19 XP / S21 / T21 generation)

Models: S19 XP, S19 XP Hyd, S19k Pro, S19j Pro (Cvitek batches), S21, S21 Pro, T21, L7  ·  Cvitek CV1835-class SoC with eMMC storage

Default network
DHCP — no static default IP
Find the IP
IP Report button / IP Reporter tool; router DHCP lease.
Web dashboard login
root / root, or the per-unit sticker password
SSH login
miner / miner, with the root account DISABLED (root shell = /bin/false)
Reset (config wipe)
Reset button (cold-boot window). ⚠ A wrong reset on an eMMC-only board can turn a bent config into a bricked control board.
Firmware recovery
SD-card recovery is often UNAVAILABLE on these eMMC-only boards → recover over UART / U-Boot TFTP with the exact-revision image. Highest brick risk of any generation; if U-Boot won't respond, it needs bench work.
Watch out
eMMC-only means there is no simple SD-reflash safety net. S19j Pro shipped on more than one control board across batches — if miner/miner fails, try the S19-series NAND row's root/root.

Full step-by-step recovery guide →

MicroBTWhatsminer (M2x / M3x / M5x / M6x)

Models: M20S, M21S, M30S, M30S+, M31S, M50, M53, M60 (and siblings)  ·  MicroBT control board (Xilinx Zynq-class), H3/H6 generation

Default network
DHCP — the assigned IPv4 is shown on the front LED/LCD (0.0.0.0 or 169.254.x.x on the display means DHCP did not answer)
Find the IP
Hold the IPFOUND button ~2 s and the miner announces its IP; or run MicroBT's IPReporter / IPFOUND tool; or check the router's DHCP leases for a fresh MAC prefix A4:C1:38, D0:71:C4 or 7C:21:0D.
Web dashboard login
admin / admin (limited web admin) and super / super (full admin) — change the super password immediately
SSH login
Managed via the web dashboard / btminer API; SSH login varies by firmware — use the dashboard.
Reset (config wipe)
Hold RESET for 5–10 s for a full factory reset (returns to admin/admin + super/super, DHCP).
Firmware recovery
MicroSD rescue image; UART serial recovery on control-board corruption (e.g. M30S). For a direct link, static-assign your laptop to 192.168.1.99/24 and connect straight to the miner.
Watch out
After a factory reset the super password is back to its default — reset it before the miner is reachable on an untrusted network.

Full step-by-step recovery guide →

GoldshellGoldshell (BOX-series + KD / LT / CK-series)

Models: KD-BOX, Mini-DOGE, HS-BOX, ST-BOX, CK-BOX, KA-BOX, KD5, KD6, LT5, LT6, CK6, KD-MAX  ·  Goldshell control board — BOX models have a user microSD slot; KD/LT/CK/KD-MAX use eMMC

Default network
DHCP — no static default IP
Find the IP
Open find.goldshell.com on a wired laptop on the same LAN (WiFi off, incognito, no extensions); or the router's DHCP client list — Goldshell MAC prefix 18:2A:7B (current), 5C:CF:7F or 24:C9:A1 (early BOX OEM).
Web dashboard login
Legacy firmware (most BOX-series and stock-era KD5/KD6/LT5/LT6/CK6): admin / 123456789. Modern firmware (BOX-II, Mini-DOGE III+, late KD6/LT6 after ~mid-2023): the Goldshell Zone account email + password (cloud-bound via zone.goldshell.com; an unbound unit shows a QR-binding screen instead of a password prompt).
SSH login
Not the documented field path — recover via the web dashboard or the Zone binding, not SSH.
Reset (config wipe)
Hold the RST button 5–10 s (wait 90 s after AC power before starting). Or in the web UI: Configuration -> System -> Factory Reset (legacy) / Device Management -> Unbind & Reset (Zone firmware).
Firmware recovery
SD-card reflash is BOX-series ONLY (those have a user microSD slot) — balenaEtcher + the burn-*.img recovery image (request from hello@goldshell.com). KD5/KD6/LT5/LT6/CK6/KD-MAX are eMMC and are RST-button-only in the field. Firmware upgrades must run over Ethernet, never WiFi.
Watch out
Change the published 123456789 default immediately. A used, Zone-bound BOX still tied to the prior owner's account is cleared by an SD-image reflash. Non-BOX (eMMC) models have no SD safety net.

Full step-by-step recovery guide →

IceRiverIceRiver KS-series

Models: KS0, KS0 Pro, KS0 Ultra, KS1, KS2, KS3, KS3L, KS3M, KS5, KS5L, KS5M  ·  IceRiver control board (eMMC); front-panel LEDs D1–D4

Default network
DHCP; factory fallback 192.168.1.1 when DHCP does not answer (static-assign your laptop to 192.168.1.0/24). Default hostname ICERIVER-* or KS3M-*.
Find the IP
IceRiver's Detect IP tool from iceriver.io; or the router DHCP lease table.
Web dashboard login
A model-specific default printed on the chassis sticker / in the user manual — current defaults are listed at iceriver.io/faq/. IceRiver uses per-model defaults, not one universal password.
SSH login
Not the documented field path — recover via the web UI or SD recovery.
Reset (config wipe)
Hold the reset button a FULL 20 seconds until the red status LED flashes, then wait 5 minutes untouched (the bootloader copies the factory partition over the active one — interrupting bricks the eMMC). Some KS5L/KS5M revisions require holding reset WHILE powering on.
Firmware recovery
SD-card recovery — balenaEtcher + the .img from iceriver.io/firmware-download/; insert the SD, power on holding reset ~5 s (up to 30 s on some revisions), wait 8 minutes untouched. UART + eMMC reflash for deeper bricks.
Watch out
The 20-second hold with red-LED confirmation and the 5-minute do-not-touch rule are mandatory — an interrupted reset bricks the unit. Third-party firmware (xyys / tswift / iceriver-oc) changes reset behaviour.

Full step-by-step recovery guide →

CanaanAvalonMiner (Avalon A-series)

Models: AvalonMiner 1066, 1066 Pro, 1166 Pro, 1246, 1366, 1466, 1566, Nano 3 / 3S  ·  AvalonMiner control board (cgminer-based)

Default network
DHCP; configuration-mode static fallback 192.168.168.168 (subnet 255.255.255.0) — browse http://192.168.168.168/
Find the IP
The AvalonMiner control panel / Avalon app; the router DHCP lease; or configuration mode at 192.168.168.168.
Web dashboard login
root / root
SSH login
Managed via the web UI / cgminer API.
Reset (config wipe)
Press and hold the FUNC key 5–10 s (before the indicator light turns red) while powered on — clears network, pool and password configuration.
Firmware recovery
Firmware upgrade via the web UI; SD-card recovery on models whose control board has an SD slot (per the Canaan model manual).
Watch out
root/root is widely published — change it immediately. Confirm the exact model manual: defaults and the reset key vary slightly across AvalonMiner generations.

Full step-by-step recovery guide →

VolcminerVolcminer D1-series (Scrypt / LTC)

Models: D1, D1 Lite, D1 Mini, D1 Mini Pre, D1 Hydro  ·  Volcminer D1 controller (Antminer-class architecture)

Default network
DHCP — no static default IP
Find the IP
Router DHCP / connected-devices list; or VolcMiner's IP Reporter tool (volcminer.com/techsupport) — run it, then hold the IP Report button on the controller until the red LED lights.
Web dashboard login
root / ltc@dog (the @ is a literal @ character)
SSH login
SSH may be locked or use different credentials — use the web dashboard.
Reset (config wipe)
Web UI: Configuration -> System -> Factory Reset (returns to ltc@dog); or a firmware upgrade with Keep Settings UNCHECKED.
Firmware recovery
SD-card reflash — FAT / FAT32 only (32 GB or smaller; exFAT is NOT supported), extract the official recovery image to the SD root, insert into the controller daughter-board, power on: both LEDs on -> both off after ~10 s (refresh begins) -> wait 60–180 s -> both LEDs on = done. UART (3.3 V) is the last resort.
Watch out
exFAT is not supported (FAT32 only). Wrong-variant firmware (D1 vs Lite vs Mini vs Hydro) bricks the controller. Discharge the 3900 W PSU for 5 minutes before opening the chassis.

Full step-by-step recovery guide →

Pairs with the ASIC repair-by-model index and the troubleshooting cheat sheet. Every credential and procedure is sourced (D-Central mining RE + vetted on-site repair guides). Reviewed 2026-07-15; next review 2026-10-15. These are publicly-documented factory defaults, published so you can recover hardware you own. Change the dashboard and SSH credentials immediately after any recovery. Procedures vary by firmware and control-board revision; confirm against your unit and the linked guide before relying on them. Not a warranty or a guarantee against bricking.