VminerHelp center / Fleet Control: manage every rig remotely
Fleet Control: manage every rig remotely
Stats & Fleet#
We recommend registering and signing in to Fleet: while you are not signed in, the top-right button is a gold "Register / sign in to Fleet".
Register an account (username + password + email); signing in claims this machine under it. Sign in to the web console with the same account to see every machine you own.
- See: online state, hashrate, shares, temperature, power, GPU model.
- Control: start/stop mining, restart the miner, switch coin / pool / miner / wallet, change power, fan and clocks, rename, reboot, shut down.
- A machine belongs to one account only; commands are queued and run when the machine is online.
- The web console also shows earnings; the bell at the top right gets a red dot when there's a new notice.
- Shutdown works remotely, power-on does not - someone has to press the button.
Email is the only way to recover a password, so register with one you can read.
Change configuration in one step: from a rig’s action list, or after selecting a batch, click “Change configuration…”. Set the worker name, coin, pool, miner and version, connection method, direct node and payout wallet or username together. Single-rig fields show saved settings; batch fields default to “Keep unchanged”, and unchanged fields are omitted. Editing the name sets the complete fixed worker name and disables the previous prefix or random suffix. Leaving it unchanged preserves the existing naming rules.
Direct offers nodes; automatic selection uses a valid default for the final pool. CF hides node selection and leaves your local explicit proxy settings intact. “Auto (system recommended)” does not mean newest; other available versions can be selected manually. Node and version choices follow the final pool and miner. An explicitly incompatible choice rejects the whole configuration. With automatic miner selection, the displayed effective miner is informational. Leaving the miner unchanged preserves automatic selection instead of fixing it to the displayed executable.
The old wallet is not displayed. Leave it blank to keep it; entering a value explicitly replaces it and requires checking the payout destination. When switching to or from F2Pool, enter the destination pool’s username or wallet rather than assuming the previous identity applies. The client validates the final combination before saving. An idle rig only saves, without starting mining; a running rig switches at most once.
Only clients explicitly supporting unified configuration show the new single-rig button. Legacy clients retain separate actions. Mixed batches send the unified command only to supported clients; use “Legacy client settings…” for the others. Cancel sends nothing. Queued is not executed: check execution receipts and subsequent reported state.
LAN downloads and staged updates: LAN coordination, peer discovery and validation of received files run automatically, but LAN file distribution does not itself trigger an upgrade. Installation still follows the update setting or a manual command. Fleet “Staged update” schedules predownloads, then offers “Install together once all are downloaded” or “Install each as soon as it’s downloaded”; task progress and stopping further installations are available. Netbar clients do not update automatically: update the master image manually, then distribute it through the diskless system.
In Netbar Mode, remote hardware tuning is available only on newer clients that explicitly report support for combined Netbar and overclocking. Legacy clients or clients without this capability remain restricted and need an update. Ordinary mode retains its existing rules. Online/fresh status, the OC master switch, GPU support and hardware safety conditions still apply. An older batch warning about Netbar/manual-power incompatibility refers to skipped legacy clients, not a prohibition on supported newer clients.