How to use Awesome Miner for large scale farms? (Centralized control)

Centralized Dashboard Configuration

1. Install Awesome Miner on a dedicated Windows server with static IP and sufficient RAM to handle concurrent connections from hundreds of mining rigs.

2. Launch the software and navigate to Settings > General to enable Remote Management and assign a secure admin password.

3. Configure the Web Server port (default 8080) and ensure firewall rules allow inbound traffic only from trusted internal subnets.

4. Enable SSL by importing a valid certificate under Settings > Web Server > HTTPS to encrypt all dashboard communications.

5. Set up automatic backup of the database every 6 hours via Settings > Backup to prevent configuration loss during hardware failure.

Rig Grouping and Policy Automation

1. Create logical groups in the Groups tab based on hardware type — for example, “RTX-4090-ETH”, “AMD-7900XTX-ERGO”, or “LHR-Unlock-Clamp”.

2. Assign each group a unique profit-switching profile tied to real-time API feeds from WhatToMine and MiningRigRentals.

3. Define custom switching thresholds: trigger ETH switch only if profitability exceeds BTC by 12.7% for 180 seconds continuously.

4. Attach script-based actions to group events — such as executing PowerShell commands to throttle GPU clocks before pool disconnection.

5. Deploy firmware update policies that push new BIOS versions only during off-peak hours, verified via hash checksum before flashing.

Remote Agent Deployment Strategy

1. Package the Awesome Miner Remote Agent as an MSI installer using WiX Toolset to enforce silent installation across domain-joined rigs.

2. Use Group Policy Objects to deploy agents automatically to all machines matching specific WMI filters — e.g., GPU count ≥ 8 and OS build ≥ 22621.

3. Configure agent heartbeat intervals to 15 seconds for critical clusters and 45 seconds for low-priority test farms.

4. Enforce TLS 1.3-only communication between agents and the central server by disabling legacy cipher suites in the agent config file.

5. Isolate agent traffic on a VLAN separate from user-facing networks and apply QoS tagging to prioritize mining telemetry packets.

Real-Time Monitoring and Alerting

1. Build custom dashboards with KPI tiles showing live hashrate deviation, temperature delta per rig, and pool latency percentiles.

2. Integrate with PagerDuty via webhook to escalate thermal alerts above 92°C on three consecutive readings within 90 seconds.

3. Trigger SMS alerts through Twilio when total farm efficiency drops below 84.3% for over five minutes — calculated as (total accepted shares × difficulty) ÷ (total power draw in kW).

4. Log all rejected share events with full stratum headers into Elasticsearch via Logstash, indexed by rig ID and timestamp.

5. Visualize historical power consumption spikes alongside coin difficulty adjustments using Grafana panels linked to the Awesome Miner SQL database.

Frequently Asked Questions

Q: Can Awesome Miner manage rigs running HiveOS or RaveOS?Yes — configure those rigs as “External Miners” using their built-in REST APIs. Enter the device’s IP and authentication token in Awesome Miner’s External Miner dialog. The software polls metrics like temp, fan speed, and hashrate every 20 seconds without requiring local agent installation.

Q: Does Awesome Miner support dual-mining configurations like ETH + TON?It does not natively orchestrate dual-mining logic. However, you can define custom miner executables with preconfigured dual-miner launch parameters and treat them as standard single-algorithm miners within group policies.

Q: How are firmware updates validated before deployment?Each firmware binary must be placed in the designated Updates folder with a corresponding SHA256 hash file named identically but ending in '.sha256'. Awesome Miner compares hashes before initiating flash operations.

Q: Is it possible to restrict certain users to view-only access for specific rig groups?Yes — create user accounts under Settings > Users and assign granular permissions using Group Access Rules. A user may see only “LHR-Clamp” rigs and lack rights to modify profiles or reboot devices.