The Workers tab shows the miner connections currently associated with your rig. It helps you confirm that your miners are connected, submitting shares, using the expected difficulty, and contributing hashrate correctly.

For rig owners, the Workers tab is one of the most important troubleshooting tools in Mining Rig Rentals. It can help identify disconnected miners, unstable workers, rejected or stale shares, difficulty problems, and hashrate reporting issues before they affect a rental.

Understanding the Workers Tab

A worker is an individual mining connection associated with your rig.

Depending on your setup, a worker may represent:

• one ASIC miner,
• one GPU rig,
• one mining software instance,
• one device group,
• one proxy connection,
• or one of several miners grouped under the same Mining Rig Rentals rig.

If your listed rig is made from multiple miners, each miner may appear as a separate worker. If you use a mining proxy or aggregator, multiple physical devices may appear as one worker.

The Workers tab helps you verify that each connected worker is behaving as expected.

Why the Workers tab matters

The Workers tab can show whether your rig is actually delivering usable mining work.

A miner may appear to be running locally while still having problems such as:

• no accepted shares,
• rejected shares,
• stale shares,
• wrong difficulty,
• unstable hashrate,
• frequent reconnects,
• one worker underperforming,
• one worker offline,
• pool connection problems.

Checking workers is especially important before listing a rig, during a rental, or after changing hardware, mining software, overclock settings, firmware, pool configuration, or algorithm.

Common information shown in the Workers tab

The exact fields may vary by rig type, algorithm, and interface version, but worker information commonly includes connection and mining statistics such as:

These values should be reviewed together. One field by itself rarely tells the full story.

Worker status

Each worker entry tells you whether the miner is connected and active.

A healthy worker should normally show as connected or active while the rig is mining.

Possible issues include:

If a worker is supposed to be part of the rig, it should stay connected during normal operation.

Hashrate

Worker hashrate is an estimate of how much work that worker is contributing.

Hashrate can be calculated differently by the miner, pool, and Mining Rig Rentals. Because of this, the value may not exactly match the number shown in your miner console.

Short-term hashrate may move up and down naturally. This is especially true when share difficulty is high or shares are submitted infrequently.

When reviewing worker hashrate, look for the stable average over time, not a brief spike.

A worker may have a problem if:

• hashrate is much lower than expected,
• hashrate frequently drops to zero,
• hashrate swings heavily for long periods,
• one worker is much lower than similar workers,
• total worker hashrate does not match the rig’s advertised hashrate.

If the miner shows high local hashrate but worker hashrate remains low, check accepted shares, rejected shares, stale shares, difficulty, and pool-side reporting.

Accepted shares

Accepted shares are one of the most important signs that the worker is mining successfully.

An accepted share means the worker submitted proof of work that was accepted by the mining connection.

A healthy worker should show accepted shares increasing over time.

If accepted shares are not increasing, possible causes include:

• the miner is not actually mining,
• the pool connection is incorrect,
• the algorithm is wrong,
• share difficulty is too high,
• the miner is disconnected,
• the worker is pointed to the wrong endpoint,
• the renter’s pool is not accepting work,
• there is a miner or hardware problem.

Local hashrate without accepted shares is not enough. Renters need accepted mining work.

Rejected shares

Rejected shares are shares submitted by the worker but not accepted.

A small number of rejects may happen occasionally, but repeated or increasing rejected shares should be investigated.

Common causes include:

• unstable overclocking,
• hardware errors,
• wrong algorithm,
• incorrect miner settings,
• pool difficulty mismatch,
• miner software bugs,
• unsupported coin or algorithm variant,
• bad pool connection parameters.

If one worker has more rejects than the others, inspect that worker first. It may have unstable hardware, bad clocks, bad firmware, or a configuration problem.

Stale shares

Stale shares are shares that arrived too late to be useful for the current mining job.

A low stale rate may occur occasionally, especially when mining to distant pools. Frequent stale shares usually indicate a latency or connection problem.

Common causes include:

• high latency to the pool,
• packet loss,
• unstable internet connection,
• overloaded router,
• pool server instability,
• VPN or proxy delay,
• frequent job changes from the pool,
• miner reconnects.

If stale shares only happen with one pool or region, the pool location or routing may be the cause. If stale shares happen across multiple pools, check your local network and miner stability.

Difficulty

The difficulty shown for a worker is usually share difficulty, not coin network difficulty.

Share difficulty controls how difficult each submitted share must be. It affects how often the worker submits shares and how smooth hashrate reporting appears.

If difficulty is too low, the worker may submit too many shares.

If difficulty is too high, the worker may submit shares less often, causing hashrate estimates to appear unstable over short time periods.

Many pools use variable difficulty, also called VarDiff, which automatically adjusts the share difficulty after the worker connects. In that case, the difficulty may change during the first few minutes of mining before stabilizing.

The stable difficulty shown in the Workers tab can help you choose a reasonable Suggested Difficulty value for the rig.

Do not confuse this with blockchain network difficulty. Network difficulty is controlled by the coin network and should not be used as your rig’s Suggested Difficulty.

Multiple workers under one rig

Some rigs are made from multiple workers. The total rig performance depends on all workers combined.

When reviewing a multi-worker rig, check each worker individually.

Look for:

• one worker offline,
• one worker producing rejects,
• one worker submitting stale shares,
• one worker with lower hashrate than expected,
• one worker using different difficulty,
• one worker reconnecting repeatedly.

Do not assume the rig is healthy just because the total hashrate looks close to normal. One unstable worker may still cause rental problems, especially if it disconnects during a renter’s rental.

If a worker is unreliable, remove it from the rig or fix it before listing the rig.

Using the Workers tab before listing a rig

Before making a rig available for rent, use the Workers tab to confirm:

If any of these checks fail, troubleshoot the rig before listing it.

Using the Workers tab during a rental

During an active rental, the Workers tab can help determine whether the rig is delivering expected performance.

Check:

• whether all workers are still connected,
• whether accepted shares are increasing,
• whether rejected or stale shares increased,
• whether hashrate dropped,
• whether difficulty changed unexpectedly,
• whether a worker stopped submitting shares.

If the renter reports poor pool-side hashrate, compare the Workers tab with miner logs and the renter’s pool data where available.

The Workers tab can help separate rig-side problems from pool-side or network-side issues.

Common worker problems and what they mean

Worker is offline

Possible causes:

• miner stopped,
• rig lost power,
• network outage,
• incorrect Mining Rig Rentals connection settings,
• firewall or DNS problem,
• mining software crash,
• watchdog failed to restart the miner.

Recommended action:

Restart the miner, verify network connectivity, check mining software logs, and confirm the Mining Rig Rentals connection details.

Worker is connected but has no accepted shares

Possible causes:

• wrong algorithm,
• wrong pool port,
• wrong wallet or username format,
• pool authorization problem,
• difficulty too high,
• miner is not receiving valid work,
• pool is not accepting shares.

Recommended action:

Check miner logs, verify pool settings, test with a known-good pool, and confirm that the rig is listed under the correct algorithm.

Worker has many rejected shares

Possible causes:

• unstable overclock,
• bad hardware,
• wrong miner settings,
• wrong algorithm variant,
• miner software bug,
• pool difficulty mismatch.

Recommended action:

Reduce clocks, check hardware errors, test another miner version, and verify the algorithm and pool configuration.

Worker has many stale shares

Possible causes:

• high latency,
• packet loss,
• unstable internet,
• distant pool server,
• overloaded router,
• VPN or proxy delay,
• pool server instability.

Recommended action:

Check network quality, test another pool region, avoid unstable VPN routing, and confirm the miner is not reconnecting.

Worker has unstable hashrate

Possible causes:

• high share difficulty,
• low share count,
• unstable hardware,
• thermal throttling,
• miner restarts,
• pool-side reporting delay,
• aggressive overclocking,
• rejected or stale shares.

Recommended action:

Review difficulty, accepted share timing, miner logs, temperatures, clocks, and worker stability over a longer period.

Miner console vs Workers tab

The miner console and the Workers tab may not always show the same hashrate.

This is normal because they may calculate hashrate differently.

The miner console often reports local estimated speed based on device activity. Mining Rig Rentals and pools may estimate hashrate from accepted shares over time.

If these values differ, check:

• share difficulty,
• rejected shares,
• worker uptime,
• pool-side hashrate,
• miner-side hashrate.

A miner console showing high hashrate does not guarantee that the renter is receiving accepted mining work.

When to contact support

Contact Mining Rig Rentals support if the Workers tab shows behavior that does not match your miner or pool data and you cannot identify the cause.

Include:

• rig name or ID,
• rental ID if applicable,
• algorithm,
• miner software and version,
• worker names,
• pool URL and port,
• approximate time of the issue,
• screenshots of the Workers tab,
• miner logs showing accepted, rejected, or stale shares,
• whether the issue happens on more than one pool.

Exact times and logs help support determine whether the issue is rig-side, renter-side, pool-side, network-side, or platform-side.

Summary

The Workers tab shows how each connected miner is performing through Mining Rig Rentals.

Use it to verify:

• workers are connected,
• rejected and stale shares are low,
• worker hashrate is stable,
• share difficulty is reasonable,
• all workers are contributing as expected.

For rig owners, the Workers tab should be checked before listing a rig, after configuration changes, and whenever a rental performance issue is reported.