Offline miner
Start with power, switch port, VLAN, DHCP, and the IP range being scanned.
Troubleshoot miner discovery, credentials, pool changes and device-specific behavior with a reversible BTC Tools workflow.
Workflow
Troubleshooting works best when symptoms are separated by network, configuration, pool, firmware, hardware, and cooling causes.
Start with power, switch port, VLAN, DHCP, and the IP range being scanned.
Review pool URL, worker name, backup pools, and the device group that received the change.
Compare local status with pool-side activity and inspect heat or hardware symptoms.
Check pool endpoint, latency, worker format, and firmware-specific settings.
Checklist
Record the subnet, device response, credentials, firmware and last attempted action before repeating a change.
Operations
The table separates network, authentication, configuration and device-specific symptoms so unrelated fixes are not mixed together.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Network unreachable | Wrong subnet, firewall, VLAN, DHCP, switch, or cable. | Confirm IP plan and physical network. |
| Wrong credentials | Password changed or inconsistent device group. | Confirm access for the selected miners. |
| Low hashrate | Overheating, pool issue, firmware, or hardware condition. | Check temperature, pool data, and miner logs. |
| Fan errors | Fan failure, cabling, dust, or sensor issue. | Inspect device cooling and maintenance records. |
| Firmware mismatch | Different model or firmware behavior. | Test actions on a small compatible group. |
| Wrong pool | Pool URL or worker value was applied to the wrong group. | Compare current values with the intended batch plan. |
| Duplicate IP | Static IP conflict or stale DHCP reservation. | Reconcile MAC address and IP records. |
| Rejected shares | Pool endpoint, worker format, latency, or firmware setting. | Compare pool dashboard data with miner-side settings. |
| Thermal throttling | Airflow, fan, room heat, or dust buildup. | Fix cooling conditions before expanding changes. |
| Intermittent reachability | Switch, cable, PSU, firmware, or overloaded network segment. | Check physical path and isolate the affected segment. |
Setup
Change one variable at a time and keep the first reproducible failure for comparison.
