Перевірити підключення майнера та надсилання шарів
Як переконатися, що майнери коректно працюють через ретранслятор.
A miner that connects is not the same as a miner whose shares are accepted. After Protocol Sniffing is on for that pool, the admin site shows submits, accepts, rejects, and stale shares. You do not need to call an API.
Turn sniffing on
- Open Pool Management and edit the pool.
- Turn Protocol Sniffing on. For ordinary BTC the Parser is Stratum V1. Ethash coins such as ETH and ETC use Stratum V1 (Ethash). Choosing the coin fills this in.
- Save. Forwarding still works with sniffing off; you just will not see per-miner share counts.
Confirm the client is online
On the Dashboard, the Client Nodes card shows a recent heartbeat, and Online Workers counts machines that are connected. The same node list is under Client Nodes in the left menu.
Read the shares
- Open Miner Management → Worker Details. Filter by the pool and click Query.
- A connected miner shows Online. The Shares (S/A/R) column is submitted / accepted / rejected. Reject Rate, 5m hashrate, and Last Active are on the same row.
- Click More on that row, then the Share stats tab. There you also see Stale, Current Difficulty, and the 24h share timeline.
- Pool Summary rolls the same counts up by pool: Submitted, Accepted, Rejected, and Reject Rate.
These counters come from the mirrored session. The pool's own site is still what decides the credited balance.
If the numbers look wrong
- The client has a heartbeat, but Worker Details stays empty: the miner is not reaching the client IP and listen port, or the mapping has not been pushed yet.
- The worker is Online and submitted shares stay at zero: Protocol Sniffing is off, or the parser does not match the coin.
- Submitted shares climb and accepted stays at zero: the upstream pool is rejecting them. Check the wallet, the pool URL, and whether the job is stale.
- Reject Rate climbs: check the pool address and the latency column. With alerts enabled, the same event shows under Alert Events.