Backend Operations
Commands and operations accessible only via backend infrastructure, not available through the MiningOS web UI.
This section documents commands and operations that are only accessible via the backend infrastructure and are NOT available through the MiningOS web UI. These operations require direct access to worker services via RPC commands or system administration privileges.
For an overview of the system architecture and worker communication, see the Architecture Guide. For RPC command setup and worker registration, see the Installation Guide.
System Operations
Backend-only system commands include:
| Operation | Description | Related Documentation |
|---|---|---|
| System dump (CSV) | Export complete system state to CSV format | — |
| Reporting per period (CSV) | Generate periodic reports in CSV format | — |
| Firmware updates | Deploy firmware to mining devices | See Firmware Update Procedures below |
Site operators should ensure there are no "pending actions in the Actions Chart" or "submitted actions pending approval" during firmware deployments while server restart is in progress. See Requests & Approvals for action workflow details.
Container Operations
Backend-only container configuration commands:
| Operation | Description | Related Documentation |
|---|---|---|
| Configure cooling | Adjust cooling system parameters | Container Example: Bitdeer, Container Example: Antspace |
| Configure alarms | Set alarm thresholds and notification rules | Alerts Manual, Visual Alerts per Container Type |
For container-specific alarm thresholds and visual indicators, refer to the Alerts Manual. For container specifications, see Supported Devices — Containers.
Miner Operations
Backend-only miner configuration commands:
| Operation | Description | Related Documentation |
|---|---|---|
| Performance tuning | Adjust hashrate and power consumption parameters | Power Mode Support Table |
| Configure pools | Set mining pool endpoints and failover configuration | Pool Manager Module, Pool Endpoints |
| Configure networking | Manage IP addresses and network settings | Manual Set of IPs |
| Create/replace devices | Register new miners or replace existing units | O&M: Adding & Updating Miners |
Whatsminers require a password change to enable API command access. See the Introduction for initial setup notes and Supported Devices — MicroBT Whatsminer for model specifications.
For UI-based miner management operations, see:
- Explorer — Search and filter miners
- O&M: Adding & Updating Miners — Register, move, and maintain miners
- Pool Manager Module — Configure mining pools via UI
Remarks on Firmware Updates
CRITICAL: Before any firmware update on any device at the sites, the development team must test the firmware separately on a single device to verify there are no breaking API changes. Failure to do this risks losing control of devices, which could be dangerous for operations.
Bitmain S19XP Special Firmware: The Bitmain S19XP miners in some deployments are modified by Bitmain to operate without fans. This is achieved through custom firmware (not fan coolers). Therefore:
- DO NOT update S19XP firmware by downloading versions from Bitmain's public website
- ALWAYS use firmware updates provided directly by Bitmain specifically modified for fanless operation
- Contact Bitmain support for custom firmware versions
See Supported Devices — Bitmain Antminer for S19XP specifications.
Firmware Update Checklist
Before performing firmware updates:
- Test on isolated device — Verify API compatibility on a single unit
- Clear pending actions — Ensure no actions are pending in the Actions Chart
- Notify operators — Coordinate with site operators via Comments if needed
- Verify device compatibility — Check Supported Devices for model-specific requirements
- Schedule maintenance window — Avoid peak operational periods
- Backup configuration — Export current settings before update
Supported Firmware Sources
| Manufacturer | Official Source | Support Portal |
|---|---|---|
| Bitmain | Contact support directly for custom firmware | Bitmain Support |
| MicroBT | MicroBT Official | WhatsMiner Shop |
| Canaan | Canaan Official | Canaan Shop |
For detailed specifications of each manufacturer's devices, see Supported Devices.
RPC Command Reference
Backend operations are executed via RPC commands to the appropriate workers. For detailed RPC method documentation and the worker architecture, see the Architecture Guide.
Example: Register a New Miner via RPC
hp-rpc-cli -s <MINER_WORKER_RPC_KEY> -m registerThing -d '{
"id": "miner-am-s19xp-001",
"opts": {
"address": "192.168.1.100",
"port": 4028
},
"info": {
"serialNum": "BITMAIN-S19XP-001"
}
}'For complete installation and RPC setup instructions, see the Installation Guide.
User Permissions
Backend operations require elevated privileges. User role requirements:
| Operation Type | Minimum Role Required |
|---|---|
| System dump/reporting | Admin |
| Firmware updates | Admin |
| Container configuration | Admin or Site Manager |
| Miner configuration | Admin or Site Manager |
| Device registration | Admin or Site Manager |
For user role definitions and management, see Settings > User Management.
Related Documentation
Operator Manual
- Header — Actions Chart and status indicators
- Requests & Approvals — Action authorization workflow
- Alerts Manual — Alarm configuration and thresholds
- Pool Manager Module — Mining pool configuration
- O&M: Adding & Updating Miners — Device management procedures
- Settings — User roles and system configuration
- Operational Best Practices — Recommended procedures
Architecture & Technical Reference
- Architecture Guide — System design, RPC communication, and worker hierarchy
- Supported Devices — Hardware compatibility and firmware sources
- Installation Guide — Worker setup and RPC registration