Prepare the location before applying power
An ASIC drawing several kilowatts should not run through a random extension cord or an unverified outlet. Prepare protection, grounding, the correct cable, Ethernet and a hot-air path before opening the web panel.
Place the miner so air moves through the chassis in one direction and the switch and cables remain accessible. After power-on, let the controller boot and do not press reset without knowing which settings it will clear.
- check circuit and breaker capacity
- use Ethernet for first setup
- prepare ventilation before startup
- do not use a household multi-plug
Find the IP address and open the local panel
Most ASICs receive an IP through DHCP. Find it in the router, DHCP leases or the manufacturer's tool. Open the address only from the local network and change the default password before leaving the miner online.
If the device does not load, check Ethernet link lights, the cable, VLAN, gateway and DNS. A static address can help a farm, but configure it carefully to avoid an IP conflict.
- record IP and MAC address
- change the admin password
- do not publish the panel on the internet
- check DHCP, gateway and DNS
Enter the pool URL, worker name and password
Miner Configuration usually provides three pool rows with priorities. Put the primary endpoint in Pool 1 and backup addresses in Pool 2 and Pool 3. The worker format depends on the service, but it is often account.workername.
A worker password is a technical field on many pools and is not the account password, but follow the pool's rules. The payout address belongs in the pool account rather than in the worker-password field.
- copy URL and port without spaces
- give every ASIC a unique worker name
- never paste a seed phrase into the password field
- save backup endpoints
Verify operation after Save
After saving, check that pool status becomes Alive or Connected. The first accepted share should appear after a few minutes, and local hashrate should settle. Do not estimate income from the first minutes because pool statistics have variance.
Compare local and pool-side hashrate, temperature, fan speed, hashboard count and accepted/rejected/stale shares. If the ASIC is online but no shares are accepted, the most common causes are URL, worker, DNS, port or compatibility.
- check pool status
- wait for the first accepted share
- compare local and pool-side hashrate
- check the log after first start
Failover and common errors
Three pool URLs do not automatically make mining more profitable. They give the ASIC somewhere to go when the primary server is unavailable. Test whether it really switches when the first endpoint is unreachable, and avoid endpoints that share the same DNS or route problem.
A high stale rate points to latency or job updates, rejected shares point to wrong data or compatibility, and no shares at all point to configuration or network. Change one parameter at a time so you know what fixed the issue.
- Pool 1 is primary; Pool 2 and 3 are backups
- test failover separately
- do not change URL, worker and DNS at once
- record the error and time
| Field | Example role | Check |
|---|---|---|
| Pool URL | Server address and port | Correct protocol and region |
| Worker | account.asic-01 | Unique name without spaces |
| Worker password | Technical value | Pool-specific rules |
| Pool 2/3 | Failover endpoints | Lower priority and reachability |
| Payout address | Address in pool account | Configured in the service account |
Real photos and source material
These photographs and diagrams are sourced from public archives. Open the source link to check the author and license.
_0389.jpg)
Want to check the numbers for your ASIC right away?
Open calculator →
