Nothing scans
Check workstation interface, target range, routing, VLAN, firewall, and whether any expected miner web UI is reachable.
Diagnose BTC Tools discovery, credential, pool, worker and batch-change problems with an ordered set of network and device checks.
Workflow
Start with the narrowest failing layer. A failed scan is not automatically a broken miner, and a visible miner is not automatically ready for configuration.
Check workstation interface, target range, routing, VLAN, firewall, and whether any expected miner web UI is reachable.
Check power, cable, switch port, address changes, duplicate IP, and device-specific response behavior.
Confirm credentials, ownership, firmware support, and whether discovery and management use different interfaces.
Compare applied pool and worker values with local status and pool-side timestamps.
Checklist
Change one variable at a time and record the result so repeated attempts do not hide the original cause.
Operations
Use the symptom to choose the next observation, not the next random change.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Zero miners found | Wrong interface, range, VLAN, firewall, or routing | Test reachability to one known miner. |
| Some miners missing | Address change, shared network fault, power, or unsupported response | Compare by rack, switch, and model. |
| Authentication failure | Wrong credential or firmware behavior | Test one confirmed device directly. |
| Batch timeout | Too many devices, network loss, mixed firmware, or action support | Reduce the batch and isolate exceptions. |
| Wrong pool or worker | Incorrect prepared value or wrong selected group | Restore recorded values on a test set. |
| Low hashrate or heat | Pool, cooling, firmware, PSU, or hardware condition | Compare miner logs, local readings, and pool data. |
Setup
Save the scan result, affected IPs, model and firmware group, action, timestamp, and pool-side state before rebooting or repeating a batch.
