Releases

MiningOps 2.2.0: Tripp Lite rack PDUs join the power monitors, so each rig on a metered outlet is measured at the wall.

Rack pdus

• Settings > Power has a new Rack PDUs card next to Emporia and Shelly. Add a Tripp Lite PDU by its address and SNMP read community, choose the machine that reads it, and say what the whole bar measures.
• It is read over SNMP every 10 seconds: the whole bar, each of its circuits and, on models that meter them, each outlet. A machine on the PDU's network reads it: this server, or a rig or collector box running agent 1.11.0. So it works when your site is hosted somewhere else too.
• The SNMP community is kept for the machine that reads the PDU and never shown again.
• On the Power page the PDU's outlets sit under their circuit, and its circuits under the bar.
• An outlet's own name on the PDU is used for it, so outlets named after their rigs read that way on the Power page.

Rigs on outlets

• In Settings > Power, under What each channel measures, pick the rig on each outlet. A rig with two power supplies on two outlets adds both.
• That rig's measured watts then replace its cards plus extra watts on the Power page, in Profit and on its page, as with a Shelly plug.
• MiningOps only reads the PDU. Turning outlets on and off isn't part of this release.

Also

• Shelly plugs and rack PDUs share the same settings and checks underneath, so both behave the same way when a device stops answering or is removed.
• A rig page's Each GPU over time charts follow each card when the cards are renumbered, as happens when a card is added, removed or moved to another slot. Each card keeps one line, named by its number now, and every card shows in the legend. A card that was swapped out shows as an earlier card.
• Those charts break their lines where a rig sent nothing, instead of drawing straight across the gap.

Agent 1.11.0

• Reads Tripp Lite PDUs over SNMP v2c, next to ASICs and Shelly meters.
• Fixes a new rig's miner not starting after an install with --install-driver. The driver loads only after the reboot, and a warning about it ended up in the miner's command line. Running the installer again (sudo bash install.sh) repairs a rig set up that way, and it now stops with a clear message rather than writing a miner service that can't start.
• Only a rig or collector box that reads PDUs needs it, apart from the repair above. The site's own collector updates with the site.

In this release

• MiningOps 2.2.0 with agent 1.11.0.
• Install it from Settings > Updates. It makes a database copy first, and the rigs keep mining.

MiningOps 2.1.0: the Power page works without a power monitor, Shelly plugs and meters join Emporia, and a rig can be measured at the wall.

Power page

• The Power page no longer needs a power monitor. From the rigs' own reports it shows what they draw now, a chart over 24 hours, 7 days or 30 days, and each day's energy and cost.
• A new Rigs table lists each rig's power now, its average, energy and cost over the range, and how its power is known: measured by a monitor, or its cards' reported power plus its extra watts.
• With a monitor that measures the whole site, the page adds the whole site and everything else, as before.
• Each connected monitor has a table of its own circuits, plugs and meters. A monitor that needs attention says so at the top of the page.

Power monitors

• Settings > Power has a Power monitors panel with a card for each kind of monitor. Emporia Vue moved there and works as before, and your readings and history carry over.
• Shelly plugs and meters are new. They are read on your own network every 10 seconds, with no account: Shelly plugs, relays that meter power, and the EM and 3EM energy meters, first generation included.
• A machine on the Shelly's network reads it: this server, or a rig or collector box running agent 1.10.0. So it works when your site is hosted somewhere else too.
• Add a Shelly by its address, choose the machine that reads it, and say what it measures: the whole site, one rig, or something else. If the Shelly has a password, it is kept for the machine that reads it and never shown again.
• Removing a Shelly keeps its readings.

A rig's own meter

• A plug or circuit can be assigned to the rig it powers, in Settings > Power under What each channel measures, or when you add a Shelly.
• That rig's measured watts then replace its cards plus extra watts on the Power page, in Profit and on the rig's page, for every minute the monitor has a reading. Minutes without one fall back to the estimate.
• The rig's page shows its power at the wall, and Profit marks the rig as measured.

Also

• In Settings > Power, ASICs no longer show a 150 W estimate of extra power. An ASIC's reported power is the whole machine, which is how Profit already counted it.

Agent 1.10.0

• Reads Shelly plugs and meters for the site, next to ASICs.
• Only a rig or collector box that reads Shellys needs it. The site's own collector updates with the site.

In this release

• MiningOps 2.1.0 with agent 1.10.0.
• Install it from Settings > Updates. It makes a database copy first, and the rigs keep mining.
• The first start copies your Emporia readings to the new power tables. The old tables stay, in case you go back to 2.0.3.

MiningOps 2.0.3: tune or disable single GPUs from the rig's page, an alert for a stopped GPU fan, and card readings while the miner is stopped.

Single GPUs

• Each GPU on a rig's page now has Tune and Disable buttons, for administrators.
• Tune gives one card values of its own: power limit, fan speed, core and memory offsets, and clock locks. Fields you leave empty follow the rig's tuning, and Use the rig's settings puts the card back on them.
• A card can change only values the rig's tuning sets, so going back always has the rig's values to use. Clock locks are the exception, as 0 already means no lock.
• Cards keep their own values when you apply a profile or manual tuning to the whole rig. Manual tuning in the Control dialog has a box to reset them as well.
• The GPU table has a Tuning column with each card's settings. A card's own values are marked, and hovering one shows what the rig uses.
• The Current tuning panel shows the tuning the rig holds now, as its agent reports it, and which cards have their own values.
• Disable takes a card out of mining, and Enable puts it back. The miner restarts on the chosen cards, so mining pauses for about 30 seconds. The rest of the miner settings stay as they are, the pool password included.
• A disabled card keeps reporting its temperature, fan and power, and its row is dimmed.
• Both need agent 1.9.1 on the rig. AMD cards on Windows take one setting for every card, so they can be disabled but not tuned one by one.

Alerts

• A new alert names each GPU whose fan reads 0% while the card is at 70 °C or more. Its fan has stopped or come unplugged, and tuning can't start it again, so the alert says to disable the card and check the fan.
• It shows on the Overview and goes to your notification channels as an urgent alert, so it comes through during quiet hours too. You can turn it off in Settings > Notifications.
• Cards that rest their fans while idle are not flagged, and neither are cards that report no fan speed.

Agent 1.9.1

• Tunes single cards and changes which cards mine, for the buttons above.
• GPU readings keep coming while the miner is stopped. Without persistence mode the driver starts every card for each reading when no miner has them open, and on a rig with eight cards that took longer than the agent waited. The dashboard then lost every card's temperature, fan and power until the miner started again, including the card you stopped it for.

In this release

• MiningOps 2.0.3 with agent 1.9.1. Update each rig's agent from its page to use the GPU buttons and get the readings fix.
• Install it from Settings > Updates. It makes a database copy first, and the rigs keep mining.

MiningOps 2.0.2: Settings in tabs, days in your own time zone, and a tidier fleet.

Settings

• Settings is split into tabs: Mining, ASICs, Power, Notifications and Accounts, plus Updates on a licensed site.
• Each tab has its own address, so links from other pages open the right one. The Overview's update notice opens Updates, and the Power page's Emporia link opens Power.
• The Updates tab shows a dot when a new release is waiting.

Your time zone

• Everything grouped by day now uses the days of the browser you are looking from, instead of UTC days: the Analytics daily summary, day by day on the Profit and Power pages, and the pay forecast.
• Today so far on the Power page counts from your local midnight.
• Days when the clocks change are 23 or 25 hours long, as they are on the wall.

ASICs

• When the server's own ASIC collector is switched off in Settings, or has no addresses to poll, this-server no longer shows in the fleet, on the Rigs page or on the Overview, and it raises no offline alerts.
• ASICs it found before keep their history and stay listed.

In this release

• MiningOps 2.0.2 with agent 1.9.0, unchanged, so your rigs need no agent update.
• Install it from Settings > Updates. It makes a database copy first, and the rigs keep mining.

MiningOps 2.0.1: clearer numbers on the Profit page.

Profit

• Coin prices of a dollar or more show cents: $31.20 instead of $31.200, and $98,603.61 for Bitcoin.
• Small coin amounts keep their significant digits, so a rig earning 0.000226 BTC a day shows that instead of 0.000 BTC.
• Break-even prices follow the same rules.

Also new in the installer

These come with the installer at miningops.io/install.sh, whichever release it installs:

• --tunnel PORT, for a Cloudflare Tunnel (cloudflared) on the same server. The site listens on 127.0.0.1 only, and nothing is opened in the firewall.
• Running the installer again on a site that already has data first makes a copy of its databases, the same kind Settings lists.
• The site's folder, /opt/miningops, can now be read by the site's own user only.

In this release

• MiningOps 2.0.1 with agent 1.9.0, unchanged, so your rigs need no agent update.
• Install it from Settings > Updates. It makes a database copy first, and the rigs keep mining.

MiningOps 2.0.0, the first self-hosted release.

MiningOps is a dashboard for GPU rigs and ASIC miners that runs on your own server. A small agent on each rig reports to it and carries out what you choose in the dashboard. Your rigs, wallets and pool settings stay with you.

Install

• One command on a fresh Ubuntu 24.04 server installs the site with your license key. It sets up Node.js, the MiningOps service and an HTTPS certificate from Let's Encrypt (--email), or plain HTTP for your own reverse proxy or Cloudflare Tunnel (--proxy PORT).
• The installer checks the release's signature against the MiningOps release key before any of its code runs.
• It prints a setup key for your first admin account.
• Running it again repairs the install and keeps your data. On a new server, the same key and domain move the site there.

Rigs

• The agent runs on Linux rigs (Ubuntu) and on Windows 10 and 11. On Windows it brings its own Python and runs from Task Scheduler.
• Add a rig from the dashboard: it gives you the install command for Linux or Windows, with the rig's own token.
• NVIDIA and AMD cards. AMD support is new in this release and has had less testing than NVIDIA.
• For every card: hashrate, accepted and rejected shares, core and memory temperature, power, fan speed, clocks and load.
• Set how many cards each rig should have, so a card that drops out is noticed.

Miners and pools

• Nine GPU miners: ForgeMiner, KRig, WildRig Multi, SRBMiner-Multi, BzMiner, OneZeroMiner, PeakMiner, Rigel and lolMiner. The agent downloads them from their official GitHub releases and checks each download's SHA-256.
• Choose the miner, coin, algorithm, pools and worker name for each rig from the dashboard. If new settings don't start, the rig goes back to the ones it had.
• Upgrade a rig's miner to a newer release from the dashboard.
• Miner defaults for new rigs, so a rig starts mining as soon as its agent is installed.

Tuning

• Power limit, core and memory clock offsets, clock locks and fan speed for each rig, within limits you set per rig.
• Tuning profiles apply the same settings to many rigs at once.
• Tuning is applied again after every miner restart and reboot.
• On Windows, settings the driver refuses are shown as unavailable instead of failing.

ASICs

• A collector polls the ASIC miners on your network and shows them beside your GPU rigs: hashrate, temperatures, hashboards, fans and pools. The collector is either the site itself or the agent installed with --collector on a box at the miners' site.
• It reads ASICs that answer the cgminer API (stock Antminer, LuxOS, Braiins OS and others) and Whatsminer's API.
• ASIC monitoring is read-only: MiningOps never changes an ASIC's settings.

Profit, payouts and power

• Profit per coin from live prices and network difficulty, against your power cost.
• Payout tracking shows what your pools actually paid. Sources: pool APIs (cryptonote-nodejs-pool, MiningCore and open-ethereum-pool pools), a wallet on a supported block explorer, or payouts you import.
• Optional Emporia Vue energy monitor: everything the site draws, circuit by circuit, beside what the rigs use.

History

• Charts of hashrate, power and temperatures over time, for each rig and card, with comparisons between rigs.
• An activity log of every command, who sent it and how it went.

Alerts

• A rig goes offline or an ASIC stops answering.
• Fewer cards or hashboards report than the rig should have.
• A card or ASIC chip gets too hot.
• A rig has many rejected shares.
• A command fails on a rig.
• Alerts go to Telegram, Discord, email or a webhook. Quiet hours hold back alerts overnight and can still let urgent ones through.

Accounts and safety

• Admin and view-only accounts. Sign-ins lock for a while after repeated failures.
• A database copy every night (the last 7 are kept) and before every update.
• Rig agents update themselves from your site. Your site signs the agent with its own key, made at install, and every rig checks that signature before it installs an update.

Updates

• Settings > Updates checks for new releases once a day. Installing one makes a database copy, checks the release's signature, installs it and restarts the site. The rigs keep mining throughout.
• Your license includes a year of updates. After that your site keeps running on its version; renewing gives you another year under the same key.

In this release

• MiningOps 2.0.0 with agent 1.9.0.
• Server: Ubuntu 24.04 with Node.js 24.22.1 or newer. The installer installs or upgrades Node.js, which also brings the fix for the Brotli flaw in older Node.js releases (CVE-2026-111497).

Known limits

• HiveOS rigs are not supported yet.
• The site needs a public domain name. Installs reachable only on a local network come later.
• Docker is not supported.