Setup Guide

Start an IceRiver miner the right way.

Use this end-to-end checklist to position the miner safely, find it on the network, log in to the web interface, configure your mining pool, and confirm healthy operation.

On this page

Step-by-step setup checklist
Default credentials
Sample pool URLs
Tips for stable operation
Recommended tools

Step-by-step setup checklist

Position the miner in a clean, ventilated area between 0 and 35 degC ambient. Keep at least 30 cm of clearance around intake and exhaust.
Connect a quality Ethernet cable to the miner before plugging in power. Use a switch on the same subnet as your management computer.
Connect the appropriate power supply: compact 100 W class models use external adapters, Lite models commonly use 500-1000 W, and full-size KS3/KS5/KS7/AL3/AE3 miners require high-voltage circuits sized for 3200-3400 W continuous load.
Discover the miner: run IceRiver Monitor or IceRiver MinerTool, click Scan, and locate the device. Alternatively press the IP button on the front of the unit for 1-2 seconds.
Open the miner IP in a browser (for example http://192.168.1.101) and log in using the default credentials shown below.
Open Mining Settings and enter pool URL, worker name (your Kaspa or Aleo wallet address), and password (usually x). Add a backup pool when possible.
Save changes and reboot the miner so the new pool configuration is active.
Watch the dashboard for 30-60 minutes: confirm steady hashrate, healthy chip temperatures, accepted shares, and no error codes.

Default credentials

All IceRiver miners ship with the same default web interface credentials. Change the password as soon as the device is online and reachable.

Username:admin · Password:12345678

Sample mining pool URLs

These are common Kaspa kHeavyHash mining pools. Replace 'your_address' with your Kaspa wallet address and 'worker' with a label of your choice.

Pool URL	Worker / wallet	Password
`stratum+tcp://kas.2miners.com:2020`	kaspa:your_address.worker	x
`stratum+tcp://kas.f2pool.com:5400`	kaspa:your_address.worker	x
`stratum+tcp://stratum.kaspa.herominers.com:1200`	kaspa:your_address.worker	x
`stratum+tcp://kas.kryptex.network:7011`	kaspa:your_address.worker	x
`stratum+tcp://stratum.kaspa-pool.org:4444`	kaspa:your_address.worker	x
`stratum+tcp://pool.woolypooly.com:3112`	kaspa:your_address.worker	x

Use Pool1, Pool2, and Pool3 for failover

All current IceRiver firmware exposes three pool slots. Configure all three with the same wallet so the miner automatically switches if Pool1 becomes unreachable. Many operators use one pool family across two regions plus a backup pool from a different operator.

LED indicator quick reference

After power-on, the indicator lights tell you whether the miner has booted, joined the network, and started mining.

L1 / power LED solid: power supply is healthy and the control board is energised.
L2 / status LED blinks during boot then becomes steady - this confirms a successful startup.
Network LED solid or blinking on the RJ-45 port: Ethernet link is up. If it is dark, swap the cable or switch port.
D3 and D4 flashing simultaneously after a long press of the reset button means a hard reset is in progress; wait until they go steady before powering off.

Power cord specification per model

IceRiver miners ship without a region-specific power cord (except KS0 PRO bundles). Use the correct IEC inlet for your hardware.

KS0, KS0 Pro, KS0 Ultra, AL0, RX0, AE0: bundled adapter or compatible external PSU according to the product page.
KS1, KS2, KS2 Lite, KS7 Lite, AL2 Lite, AE1 Lite: use a cord and circuit rated for the model's continuous draw.
KS3, KS3L, KS3M, KS5L, KS5M, KS7, AL3, AE3: use a high-current cord and breaker sized for 200-250 V AC operation where specified.
Always confirm the breaker, outlet, and cord can sustain the model's rated power draw under continuous mining load.

Tips for stable operation

Maintain ambient temperature between 0 and 35 degC. Above 35 degC the miner will throttle or trigger overheat protection.
Use input voltage between 170 V and 300 V AC. Power dips and spikes are the most common cause of unexpected reboots.
Set the fan curve to auto. Manually lowering fan speed to reduce noise will overheat the hashboard and shorten chip life.
Keep the miner connected by Ethernet. Wi-Fi bridges add latency that increases share rejection.

Recommended tools

Video tutorials

IceRiver video walkthroughs

Watch hands-on video guides covering setup, miner discovery, firmware updates, and full reviews of IceRiver ASIC miners.

IceRiver KS3M full review and setup walkthrough

End-to-end review of the IceRiver KS3M Kaspa miner: unboxing, hashrate verification, web interface and pool configuration.

IceRiver KS series setup overview

Quick visual guide to the IceRiver setup workflow: discover the miner IP, log in, set the pool, and verify mining.

IceRiver MinerTool batch utility demo

Walkthrough of IceRiver MinerTool for scanning, configuring, and managing fleets of KS series ASIC miners.

IceRiver firmware update best practices

Step-by-step demonstration of safely applying IceRiver firmware to KS series miners with stability checks.

Match the instruction to the exact device

Record	Why it matters
Full model label, serial label and power-supply requirements	Similar family names do not make firmware, power or cooling requirements interchangeable.
Installed firmware version and the operation you intend	An instruction for monitoring is not a firmware installation procedure.
Error code, time, temperature context and affected boards	A support request should describe the observed fault, not only a low hashrate.
Original settings and vendor recovery instructions	Repeated flashing or resets can remove useful diagnostic evidence.

Use manuals for the model-specific procedure, firmware notes for the exact image, and troubleshooting for an existing fault. Specifications shown in comparison tables are reference values, not independent wall-power measurements or a profitability forecast.

Documentation reviewed September 28, 2026. This is an independent operator guide; compatibility must be checked against the installed version. Source: project documentation.